plugged an m5stack atom echo into the windows pc and wanted it as a home assistant voice satellite. the catch: the agent lives on the server, so it reached the device through a serial bridge over the network. a com port on the windows box forwarded over tcp, and the server flashed through that pipe. the stock firmware crash looped the moment anything tried to provision it over serial, so it got rebuilt from the current esphome config and flashed through the bridge.
then two silent killers. the tts setting was configured for mp3 while the local stack returns wav, so announcements were dying in the decoder and it just sounded like nothing. and home assistant's internal url wasn't set, so the device couldn't pull the audio file at all. fixed both, plus a firewall rule for the local network, and the satellite spoke its own welcome message through its speaker. the full loop worked: announce received, audio fetched, decoded, played, back to listening.
the button on top does almost nothing visible, it just restarts the wake listener. holding it ten seconds factory resets the whole device, so that one's off limits. the side button is a hardware reset that reboots it. then the dashboard refused over the air installs even though the device was clearly online and adopted, which ate some time before the wake word work. it now listens for hey glados, push to talk works, and the whole thing was verified by actually talking to it instead of assuming.