Atom Echo M5 Troubleshooting

ESPHome
1

Recently purchased and setup the Atom Echo M5 dev kit through Esphome Project’s website. Everything was added to my HA instance no problem, but then I noticed it didn’t respond to the wake word at all, and then I noticed that the version of Esphome installed seems rather outdated

image
image676×605 25.1 KB

Strangely, the firmware reports as up to date:
image
image879×364 20.2 KB

I then tried to install it via Esphome by taking control and started encountering build errors when trying to install via my laptop (I tried altering the yaml to include the new ota syntax, changing the firmware url…). When I do take control and try to update it via the firmware entity, I get errors that seem to be related to old problems where the firmware image was too large…

Is there a better way of setting it up / updating it?

2

Have a look here, I have no idea if it still works or not. but it did some time ago. I have not played with one for a while. But at least it gives you the whole yaml.

I assume you have tried this from the official site??

3

I assume you have tried this from the official site??

Yea, when I try to install it after taking control in Esphome, I get the following error:

...
Compiling .pioenvs/m5stack-atom-echo-bb503c/src/esphome/components/script/script.cpp.o
Compiling .pioenvs/m5stack-atom-echo-bb503c/src/esphome/components/select/select.cpp.o
Compiling .pioenvs/m5stack-atom-echo-bb503c/src/esphome/components/select/select_call.cpp.o
xtensa-esp-elf-g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
*** [.pioenvs/m5stack-atom-echo-bb503c/src/esphome/components/micro_wake_word/streaming_model.cpp.o] Error 1
========================= [FAILED] Took 128.54 seconds =========================

Similar error when using the full .yaml from your first link :frowning:

Compiling .pioenvs/m5stack-atom-echo-bb503c/src/esphome/components/wifi/wifi_component.cpp.o
Compiling .pioenvs/m5stack-atom-echo-bb503c/src/esphome/components/wifi/wifi_component_esp_idf.cpp.o
Compiling .pioenvs/m5stack-atom-echo-bb503c/src/esphome/core/application.cpp.o
xtensa-esp-elf-g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
*** [.pioenvs/m5stack-atom-echo-bb503c/src/esphome/components/micro_wake_word/streaming_model.cpp.o] Error 1
========================= [FAILED] Took 100.03 seconds =========================
4

On what hardware are you running the esphome addon?

You may need to try from another computer

5

Ah… that seems like the case.

and of course, I’m experiencing a different error there, lol

...
 - toolchain-esp32ulp @ 2.35.0-20220830
 - toolchain-xtensa-esp-elf @ 13.2.0+20240530
Reading CMake configuration...

CMake Error: Could not find CMAKE_ROOT !!!
CMake has most likely not been installed correctly.
Modules directory not found in
C:/Users/Midni/.platformio/packages/tool-cmake/share/cmake-3.30
CMake Error: Error executing cmake::LoadCache(). Aborting.
6

Are you trying to build on a Raspberry Pi?

For info, “Official” YAML from the compiled firmware is here: firmware/voice-assistant/m5stack-atom-echo.yaml at cf3d2e439e63a82dce48cdc6ffd12537c5c969a9 · esphome/firmware · GitHub

7

I was trying to do it from my Home Assistant Blue - but I guess its got too much going on.
It now shows up after reinstalling again that its due for an update but the upgrade fails and reboots HA.

Trying to copy the yaml and build from my Windows laptop results in the below error:

......
Reading CMake configuration...

CMake Error: Could not find CMAKE_ROOT !!!
CMake has most likely not been installed correctly.
Modules directory not found in
C:/Users/Midni/.platformio/packages/tool-cmake/share/cmake-3.30
CMake Error: Error executing cmake::LoadCache(). Aborting.
8

Looks like it’s a bug with esp-idf on windows - telling it to use a previous version seems to have worked.

image
image705×534 22 KB

Though I still can’t seem to get it to respond to the wake word… progress I suppose

9

Ah, looks like I figured out my assistant problem - I accidentally purchased an Atom Lite, not the Atom Echo. Also submitted an issue for the compiling problem