Local Voice Assistant - Atom Echo not playing the media URL's after execution

Hi,

I went through the different installations - adding to ESP home modifying the code and uploading and chromium installation. Both methods do not let the device to respond by playing the media URL.

I have the wake word processing on the device and not home assistant. Once I say the wake word the light changes to slow pulsing blue and then changes into fast flashing blue. The command executes but does not play the response URL.

My Home assistant config is

  • Core - 2025.3.4
  • Supervisor - 2025.03.3
  • Operating System - 15.0
  • Frontend - 20250306.0

The M5stack version is 25.2.1

After I issue a command the device shows playing but nothing happens, see below:

[D][micro_wake_word:195]: State changed from STARTING_MICROPHONE to DETECTING_WAKE_WORD
[I][safe_mode:041]: Boot seems successful; resetting boot loop counter
[D][esp32.preferences:114]: Saving 1 preferences to flash…
[D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[D][switch:016]: ‘Use listen light’ Turning OFF.
[D][switch:055]: ‘Use listen light’: Sending state OFF
[D][light:036]: ‘M5Stack Atom Echo a13ffc’ Setting:
[D][light:047]: State: OFF
[D][switch:012]: ‘Use listen light’ Turning ON.
[D][switch:055]: ‘Use listen light’: Sending state ON
[D][light:036]: ‘M5Stack Atom Echo a13ffc’ Setting:
[D][light:047]: State: ON
[D][light:051]: Brightness: 60%
[D][light:059]: Red: 100%, Green: 89%, Blue: 71%
[D][micro_wake_word:162]: The ‘Okay Nabu’ model sliding average probability is 0.976 and most recent probability is 1.000
[D][micro_wake_word:123]: Wake Word ‘Okay Nabu’ Detected
[D][micro_wake_word:195]: State changed from DETECTING_WAKE_WORD to STOP_MICROPHONE
[D][micro_wake_word:129]: Stopping Microphone
[D][micro_wake_word:195]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE
[D][esp-idf:000]: I (90158) I2S: DMA queue destroyed

[D][micro_wake_word:195]: State changed from STOPPING_MICROPHONE to IDLE
[D][voice_assistant:506]: State changed from IDLE to START_MICROPHONE
[D][voice_assistant:512]: Desired state set to START_PIPELINE
[D][voice_assistant:223]: Starting Microphone
[D][ring_buffer:034]: Created ring buffer with size 16384
[D][voice_assistant:506]: State changed from START_MICROPHONE to STARTING_MICROPHONE
[D][esp-idf:000]: I (90210) I2S: DMA Malloc info, datalen=blocksize=1024, dma_buf_count=4

[D][voice_assistant:506]: State changed from STARTING_MICROPHONE to START_PIPELINE
[D][voice_assistant:277]: Requesting start…
[D][voice_assistant:506]: State changed from START_PIPELINE to STARTING_PIPELINE
[D][voice_assistant:527]: Client started, streaming microphone
[D][voice_assistant:506]: State changed from STARTING_PIPELINE to STREAMING_MICROPHONE
[D][voice_assistant:512]: Desired state set to STREAMING_MICROPHONE
[D][voice_assistant:642]: Event Type: 1
[D][voice_assistant:645]: Assist Pipeline running
[D][voice_assistant:642]: Event Type: 3
[D][voice_assistant:656]: STT started
[D][light:036]: ‘M5Stack Atom Echo a13ffc’ Setting:
[D][light:059]: Red: 0%, Green: 0%, Blue: 100%
[D][light:109]: Effect: ‘Slow Pulse’
[D][voice_assistant:642]: Event Type: 11
[D][voice_assistant:805]: Starting STT by VAD
[D][voice_assistant:642]: Event Type: 12
[D][voice_assistant:809]: STT by VAD end
[D][voice_assistant:506]: State changed from STREAMING_MICROPHONE to STOP_MICROPHONE
[D][voice_assistant:512]: Desired state set to AWAITING_RESPONSE
[D][voice_assistant:506]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE
[D][light:036]: ‘M5Stack Atom Echo a13ffc’ Setting:
[D][light:059]: Red: 0%, Green: 0%, Blue: 100%
[D][light:109]: Effect: ‘Fast Pulse’
[D][esp-idf:000]: I (94633) I2S: DMA queue destroyed

[D][voice_assistant:506]: State changed from STOPPING_MICROPHONE to AWAITING_RESPONSE
[D][esp32.preferences:114]: Saving 1 preferences to flash…
[D][esp32.preferences:143]: Saving 1 preferences to flash: 1 cached, 0 written, 0 failed
[D][voice_assistant:642]: Event Type: 4
[D][voice_assistant:670]: Speech recognised as: " Turn off basement lights"
[D][voice_assistant:642]: Event Type: 5
[D][voice_assistant:675]: Intent started
[D][voice_assistant:642]: Event Type: 6
[D][voice_assistant:642]: Event Type: 7
[D][voice_assistant:698]: Response: “Turned off the light”
[D][light:036]: ‘M5Stack Atom Echo a13ffc’ Setting:
[D][light:051]: Brightness: 100%
[D][light:059]: Red: 0%, Green: 0%, Blue: 100%
[D][light:109]: Effect: ‘None’
[D][voice_assistant:642]: Event Type: 8
[D][voice_assistant:720]: Response URL: “https://mana-illu.duckdns.org/api/tts_proxy/lxB5LH-wqB87AiKAm-b2_Q.wav
[D][voice_assistant:506]: State changed from AWAITING_RESPONSE to STREAMING_RESPONSE
[D][voice_assistant:512]: Desired state set to STREAMING_RESPONSE
[D][media_player:073]: ‘M5Stack Atom Echo a13ffc’ - Setting
[D][media_player:080]: Media URL: https://mana-illu.duckdns.org/api/tts_proxy/lxB5LH-wqB87AiKAm-b2_Q.wav
[D][media_player:086]: Announcement: yes
[D][light:036]: ‘M5Stack Atom Echo a13ffc’ Setting:
[D][light:051]: Brightness: 100%
[D][light:059]: Red: 0%, Green: 0%, Blue: 100%
[D][speaker_media_player:420]: State changed to ANNOUNCING
[D][voice_assistant:642]: Event Type: 2
[D][voice_assistant:736]: Assist Pipeline ended

I am experiencing the same issue exactly as described. I also tried different installation methods. I also checked the Assistant debugging page and could see, that everything seems to work properly but I am also not getting any playback from the echo itself. This leads me to belief that the firmware might be faulty / not accessing the speaker correctly.
Have you figured out anything?

Nothing seems to be working.

I have the same problem, it comes from the SSL certificate, when you disable https everything works normally, you get the audio feedback. But when you turn it back on, the atom is desperately silent. If anyone has the solution (keeping https) I would be very grateful…

That is so crazy that the atom will not work if HTTPS is turned. It was my understanding that security is one of the main requirements for all home-assistant builds. SMH. I hope they can fix this soon. I a, getting tired of home assistant constantly loosing connectivity between Google Home API integration and HA.