M5 Atom stuck after successful recognition

Hi there,

I’m using the template for the M5 Atom Echo from here: wake-word-voice-assistants/m5stack-atom-echo/m5stack-atom-echo.yaml at 5a50822602d6981ff3e61b07a5bf96c8e53d9a36 · esphome/wake-word-voice-assistants · GitHub
The voice recognition works quite well but once a command gets recognized the device stays blue and does not recognize any command anymore. A reset via button or power cycle solves the issue.

I did a test setup just with an esp and a microphone which did not show that behaviour.

Any idea on how I can more deep dive to search for the issue?

Meinereiner

Ok I think it’s not the LED.
The problem seems to be the speaker: I don’t hear anything. After successful recognition it tries to put out shy and then get stuck. But why?!

What do logs show in esphome device builder?

I think my problem is that somehow he cannot get the files to play:

[09:45:51.075][D][speaker_media_player:410]: State changed to ANNOUNCING
[09:45:56.043][D][esp-idf:000][ann_read]: E (70580) esp-tls: [sock=57] select() timeout
[09:45:56.051][D][esp-idf:000][ann_read]: E (70582) transport_base: Failed to open a new connection: 32774
[09:45:56.063][D][esp-idf:000][ann_read]: E (70582) HTTP_CLIENT: Connection failed, sock < 0
[09:45:56.067][E][audio_reader:120][ann_read]: Failed to open URL
[09:45:56.079][E][speaker_media_player.pipeline:112]: Media reader encountered an error: ESP_ERR_HTTP_CONNECT
[09:45:56.087][E][speaker_media_player:330]: The announcement pipeline's file reader encountered an error.
[09:46:01.099][E][speaker_media_player.pipeline:112]: Media reader encountered an error: ESP_ERR_HTTP_CONNECT
[09:46:01.107][E][speaker_media_player:330]: The announcement pipeline's file reader encountered an error.

Is this an issue with home assistant that cannot get reached or piper directly?

Not sure yet, but probably that is the issue: Error mediaplayer no audio response after upgrading esp32-s3-box-3 with esphome 2025.2 · Issue #72 · esphome/wake-word-voice-assistants · GitHub