I just got my audio kit and I managed to install this and get it working. I do have a few questions thought:
What does each button do? I did not manage to find an explanation for that yet
Is there a way to disable led D1, D2 and D3, or reduce the brightness? I use the device in the same room I sleep and it is waaay to bright
I there a (at least somewhat) easy way to record audio with this to train my hotword model on? Right now it is a bit hit and miss. I know this has not much to do with this project for ESP32 but I thought others might have ran into this issue before.
I am new to this forum but extremely enthusiastic about this project. I have three Matrixvoice devices and used Snips in the past. As Snips is no longer available to the public, I wanted to test Rhasspy. I cloned romkabouterâs repo and were able to setup Rhasspy (as docker container) and uploaded the project to two of the (Matrixvoice) satellites (aim is to use them without a raspberry). I have two questions:
I want to use little speakers and print a case for every satellite. Is it possible to output audio from the satellites by using the speaker output? I have seen there is a variable in âESP32-Rhasspy-Satellite/tree/master/PlatformIO/src/device.hâ file and I published the setting via MQTT to the satellite: {âamp_outputâ:â0â}. Unfortunaltely, I only hear strange noise when hotword is detected (either by amp or jack). What could I do to have a nice sound output?
Did anyone use Matrixvoice satellites with speakers and has a case (3D) printed?
I have found this setting and I hear an output. Unfortunately it is âonlyâ noise. Where do I find the samplerate? I do not output any own messages, just the âhotword detectionâ is recognized. I have Rhasspy as docker container and Matrix Voice satellites (without raspberries). What do I have to choose as âText to speechâ? Is there any other setting to be made?
You can find the files under âSoundsâ, but the project should resample to the format the Matrix Voice supports.
You can set any text to speech, but Audio Playing should be HermesMQTT
Also, each satId (different per device) should be set on all the âSatellite siteIdsâ boxes.
Server should be a different siteID (base/server/whatever)
But when you hear the hotword detection you probably already have set that correctly
Because the ESP32 runs wireless networking on Core0 it usually wise to have little code running there as if networking + custom code is too much you garner the above errors.
Would seem like you have too much on core0 at a certain point.
I donât think this is the issue. The asyncMQTT is running on core1 so only the stream task is extra on core0. It has a priority of 3, this should not cause this issue.
The core dump error is a general core dump, is absolutely says nothing about the cause.
Actually, the LoadProhibited is a message saying a memory address error
You can get those kinds of errors when you assign a small stack size to a task for instance, or just a wrong/null pointer
Also, this same code is running fine for a large amount of time on my M5 and I would probably have bumped across it when running the I2STask on core 0.
And the previous versions were all running on core0 without any issues.
So yes, in theory too much work on one core can cause an issue but I do not think this is the issue in this case.