New problem with wake word on M5Stack Atom Echo rev. 2025.2.2. The wake word only works once!!! you have to reset it every time afterwards or it won’t work. Do not update to this revision. It has a nice features such as voice volume control that appears (for the limited time that I have been able to use it) to be clearer and louder when set to full. I hope there is a new update soon to fix the problem.
1 Like
same problem ((
rev. 2025.2.2
Do not update to this revision !!!
Perhaps that issue was fixed. Because I just added one of these, updated it, and changed it’s wake word. I have been playing with it for hours, and my wife is NOT amused at all the lights going on and off! LOL
1 Like
what version do you have on you Echo?
I have 25.2.1 it is shown as up to date.
I have to press the button each time after using the on device wakeword to recognise it again.
It works fine for me on 25.2.2 and 25.3.0. the former had a bit of an issue getting flashed, but 25.3.0 went right on, and works great.
I’m not aware of a version 25.3.0, just the 25.2.2 and 25.2.3. Neither work properly for me on an M5Stack Atom Echo. The 25.2.2 will work on a M5StackS3 so what device are you burning in?
I just noticed an update through Home Assistant for a ver. 25.3.1 and 25.3.2. 25.3.2 also doesn’t work properly on a M5Stack Atom Echo
there is a fix in the git, one can easily apply it
Hi. Thanks for the info but I am having trouble finding the fix. Would you mind showing me a link?
Is this thing installing the latest version incl wake word etc? Or should I follow this thread including the fixes etc.?
No logs|no yaml = no issue.
That’s how the current firmware is burnt onto the M5Stack Atom Echo (25.2.1). The same firmware version developed for the M5Stack S3 works
Idk what version they use there, but it prompts to a github page of a deprecated version…
But links to a file that is current, in fact updated 6 hours ago.
Yes, I found this, probably the one you refer to. So if I use the installer it will actually pickup this latest config?
Why not just use esphome builder?
Same difference, it doesn’t work anyway, I get errors when compiling.
Compiling .pioenvs/m5stack-atom-echo-<redacted>/components/esp-tflite-micro/tensorflow/lite/micro/micro_allocator.o
xtensa-esp32-elf-g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
*** [.pioenvs/m5stack-atom-echo-<redacted>/src/main.o] Error 1
Could you point me to the Github of the latest version? I can only find the github for the deprecated version and also the 13$ xxxx guide on HA page points to one that the latest release is from Feb 20.
EDIT: I flashed with the 13$ xxxx tutorial and then went ahead and tried the Ready-Made Projects and they are both the same version
EDIT2: I see what you mean, if you go via ESPHome Device Builder you get a more up-to-date version 2025.4.0.
I also get this error when trying to update the version via ESPHome Device Builder…
Compiling .pioenvs/m5stack-atom-echo/src/esphome/components/select/select.o
src/esphome/components/psram/psram.cpp:5:10: fatal error: esp_psram.h: No such file or directory
*******************************************************************
* Looking for esp_psram.h dependency? Check our library registry!
*
* CLI > platformio lib search "header:esp_psram.h"
* Web > https://registry.platformio.org/search?q=header:esp_psram.h
*
*******************************************************************
#include <esp_psram.h>
^~~~~~~~~~~~~
compilation terminated.
*** [.pioenvs/m5stack-atom-echo/src/esphome/components/psram/psram.o] Error 1
========================= [FAILED] Took 19.39 seconds =========================
EDIT: They are currently fixing it esphome/esphome#8584
I would advise not to update the devices (at least Atom Echos) for the time being, i’ve managed to do some workarrounds, compiles but with alot of warning and haven’t tested it yet.