-
Notifications
You must be signed in to change notification settings - Fork 123
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
Atom echo boot loop problem. #257
Comments
I'm having the same issue on a brand-new device. My settings are identical to https://github.com/esphome/firmware/blob/main/voice-assistant/m5stack-atom-echo.yaml (except for api and wifi settings ofc) logs:
|
yeah i bought it too few days ago, At first it flashed somewhat ok, but when i unplug it, it reverts back to the default state (no lights, does nothing). Then i had to flash it several times to get it to work with voice assist, but still when i unplug it reverts back to default state.. and in the ESP home i always have multiple configurations showing up and the "adopt" button for the atom device with default ESP32 configuration/yaml. The adopt thing never go away even if i press it. The ESP32 box 3 didnt had so many problems, flashed voice assistant on second try. The first one was blank white screen and voice assist didnt work. The screen turn on/off worked but whenever it is triggered the speaker would pop. This popping is still present even with correct voice assist on the box3 (with that smiley face, not the blank white screen). Anyways.. is there a way to maybe not use these low powered devices but use android phone instead? I got many layin - e-wasting. It would be nice to put them to a good use. My main gripe is that i want hands free experience with the assist cuz of disabilities. |
I flashed an Atom Echo yesterday through https://esphome.io/projects/ and it resulted in a boot loop problem - at least I guess so from the lights. |
I dont know exactly what i did but i got it working somehow.. Steps i took involved: Install fw for first time use, |
Same happens for me. It occured, after the update which could not be installed ota, because of the new partition size. Then updated with "Plug into the computer running ESPHome Dashboard"
|
Turns out, it is already fixed in #227. Use the m5stack-atom-echo.adopted.yaml config |
how can it be fixed if this happened to me last week? |
Just use the new config and write it via usb. |
I was able to get my m5stack working again by using the yaml file included in this repository (normal, not adopdted) and esphome docker container. In contrast to what is written on https://esphome.io/projects/?type=voice I got the impression that the following firmware is used https://github.com/esphome/wake-word-voice-assistants/blob/main/m5stack-atom-echo/m5stack-atom-echo.yaml , not the one from this repository. Because in this repository, there is no on-device wake-word engine on the latest main branch, but a set up device from https://esphome.io/projects/?type=voice contains the wake word engine -> This seems like a bug to me, even though having a local wake word on the device is desireable. |
After install its looping..
Logs:
Yaml that i tried to flash using usb on web.esphome.io
The text was updated successfully, but these errors were encountered: