-
-
Notifications
You must be signed in to change notification settings - Fork 60
Flashing M5 Atom echo includes many warnings #86
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
Comments
The IDF version is set to 4 as I believe the microphone does not work on 5 yet. There is a PR in progress. The other warnings come from the tflite lib which we cannot do anything about. |
Is this one (espressif/esp-idf#13900) the issue with the microphone? |
besides all this technical considerations, why was the move made in the first place for this device? we never had these loggings before. The m5 Echo seems not powerful enough to be a serious voice assist agent anyways, so why burden it with all these more complex options. (I've had to add a Disabled on the wake word selector in the firmware manual because it just isnt up to the task) the output now is worse than in the older firmware, so progress here is making us discard the device completely, where before, it was a nice tool to play around with. Honestly, imho, bring down the options for this device... the Echo is not a full fledged wake word voice assistant, and we shouldnt treat it like that either. |
In my humble opinion, the problem is not the firmware, the speaker was not working before and is not working now, because the speaker has awful quality. That is why I use it as a full fledge wake word voice assistant but have disabled the speaker and use an external speaker, and it works perfectly now. In this post, there is an explanation on how to set it up this way: https://community.home-assistant.io/t/esphome-voice-assistant-speech-output-to-home-assistant-media-player/588337/37 |
I can see why/how that could work for you. I won’t be using the Echo with an external speaker. However what remains is that the current software for this device throws these errors while the former didn’t. I can’t see what benefit would be had from it, given the device specs are as they are. |
I guess there could be the option to have two different versions of the firmware, a full version and a slim version, that would be the best solution. But yes, the warning and errors should be fixed in any case. Isn't it possible to switch back to using an older version of the firmware? |
As there has been no activity on this issue for 30 days, I am marking it as stale. If you think this is a mistake, please comment below and I will remove the stale label. |
first of all the version gets a trigger about
but, after installing https://github.com/esphome/wake-word-voice-assistants/blob/main/m5stack-atom-echo/m5stack-atom-echo.yaml continues, these are logged
logs_m5stack-atom-echo-a82d10_run.txt
The text was updated successfully, but these errors were encountered: