-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP32 S3 Box and Box 3 eventually Freeze with on device wake work detection #194
Comments
Same Box 3 hardware and I am experiencing wake word issues similar to your own however, mine seems to lock up after only 1 or 2 responses. When it does respond, the screen stays on showing the text response and does not revert to the 'grey house'. If the mic is muted and unmuted the screen does return so the ESP is not 'locked up', it's still online and responding to esphome config changes. Pretty much useless at this point. |
Did you ever get this worked out I am having the exact same thing. |
Not really, I have sort of set this project/experiment aside as it was too frustrating and moved on to other things. I have however got it on the bench in the kitchen and I have been updating it on ESPhome as the usual updates roll through. I occasionally challenge it and it does seem a bit better but not fully useful at this stage (not mature enough tech software wise possibly)? |
Thanks for the reply. Yeah I hear you about frustrating immaturity |
The hardware is also a bit interesting - I have the green power light that flickers at times. Also how bright is that green LED - I might have to dig in and change to a much bigger resistor!! |
Hello,
I'm having an issue with both the ESP32 S3 Box and Box 3 firmware. After a few hours they will eventually freeze and stop responding to wake words. This issue occurs only when using local wake word detection on the esp32 box, so I assume its an issue with the box firmare. It seems to be resolved by toggling the box mute in home assistant, but then will inevitable break again in a few hours. I've managed to capture the error in the log below, which I've attached. Has anyone encountered this before?
logs_esp32-s3-box-3_no_wake.txt
The text was updated successfully, but these errors were encountered: