M5 assist satellite stopped voice responses after core update 2025.2.5

tescophil · February 23, 2025, 9:42pm

I have an M5 assist satellite setup with local voice pipeline processing (OpenWakeWord, Wisper and Piper)

After the latest core install the speaker still responds to the wake word, executes the requested command, but I get no voice response for any commands I try, and the “Responding” state of the speaker stays on for 30 seconds (far too long) after each command, preventing any other interactions.

Looks like it resets/reboots after each voice command:


M5Stack Atom Echo a02548 Firmware turned off
22:04:32 - 32 seconds ago
M5Stack Atom Echo a02548 changed to Idle
22:04:32 - 32 seconds ago
M5Stack Atom Echo a02548 Wake word engine location changed to In Home Assistant
22:04:32 - 32 seconds ago
M5Stack Atom Echo a02548 Use listen light turned on
22:04:32 - 32 seconds ago
M5Stack Atom Echo a02548 Button turned off
22:04:32 - 32 seconds ago
Assist Satellite changed to Idle
22:04:32 - 32 seconds ago
M5Stack Atom Echo a02548 Factory reset became unknown
22:04:32 - 32 seconds ago
Assist Satellite became unavailable
22:04:32 - 33 seconds ago
M5Stack Atom Echo a02548 Wake word engine location became unavailable
22:04:32 - 33 seconds ago
M5Stack Atom Echo a02548 became unavailable
22:04:32 - 33 seconds ago
M5Stack Atom Echo a02548 Firmware became unavailable
22:04:32 - 33 seconds ago
M5Stack Atom Echo a02548 Factory reset became unavailable
22:04:32 - 33 seconds ago
M5Stack Atom Echo a02548 Button became unavailable
22:04:32 - 33 seconds ago
M5Stack Atom Echo a02548 Use listen light became unavailable
22:04:32 - 33 seconds ago
M5Stack Atom Echo a02548 changed to Playing
22:04:03 - 1 minute ago
Assist Satellite changed to Responding triggered by state of Assist Satellite changed to Listening
22:04:03 - 1 minute ago
Assist Satellite changed to Processing triggered by state of Assist Satellite changed to Listening
22:04:03 - 1 minute ago
Assist Satellite changed to Listening
22:03:58 - 1 minute ago

Any ideas ?

mchk · February 24, 2025, 4:34am

Use the latest firmware version if you are satisfied with the microwakeword feature.

github.com/esphome/wake-word-voice-assistants

m5stack-atom-echo/m5stack-atom-echo.yaml

5a2aff4b9

substitutions:
  name: m5stack-atom-echo
  friendly_name: M5Stack Atom Echo
  micro_wake_word_model: okay_nabu  # alexa, hey_jarvis, hey_mycroft are also supported

esphome:
  name: ${name}
  name_add_mac_suffix: true
  friendly_name: ${friendly_name}
  min_version: 2025.2.0

esp32:
  board: m5stack-atom
  framework:
    type: esp-idf
    version: 4.4.8
    platform_version: 5.4.0

logger:
api:

This file has been truncated. show original

tescophil · February 24, 2025, 10:01pm

It’s already on 2025.2.1, beside that I have no idea what to do with the link your provided ?

tescophil · February 24, 2025, 10:05pm

Found the issue reported here

github.com/esphome/wake-word-voice-assistants

M5 Atom Echo - crash on Announce

opened 05:20AM - 21 Feb 25 UTC

brettmiller

After https://github.com/esphome/wake-word-voice-assistants/pull/60 the Atom Ech…oes crash when Announcing. ``` [D][media_player:086]: Announcement: yes [D][voice_assistant:506]: State changed from IDLE to STREAMING_RESPONSE [D][voice_assistant:512]: Desired state set to STREAMING_RESPONSE [D][light:036]: 'M5Stack Atom Echo 80472c' Setting: [D][light:051]: Brightness: 100% [D][light:059]: Red: 0%, Green: 0%, Blue: 100% [D][speaker_media_player:420]: State changed to ANNOUNCING [23:01:14]***ERROR*** A stack overflow in task ann_read has been detected. [23:01:14] [23:01:14] [23:01:14]Backtrace: 0x400833ed:0x3ffe4a70 0x4008ce89:0x3ffe4a90 0x4009022d:0x3ffe4ab0 0x4008ebb5:0x3ffe4b30 0x4008cf84:0x3ffe4b60 0x4008cf36:0x3ffb4210 0x733ffffc:0x00000000 |<-CORRUPTED [23:01:14] [23:01:14] [23:01:14] [23:01:14] [23:01:15]ELF file SHA256: 05d7e199ca7540d4 [23:01:15] [23:01:15]Rebooting... ``` I've test two Echoes, one setup with `esphome` locally with a yaml that includes w/ a remote_package and another setup via the ready made project on the esphome.io website. Both have the issue. Per comments on the PR it seems others are have this issue as well.

HarlemSquirrel · February 25, 2025, 12:38am

Yeah this sucks and it looks like trying to build pointing at old tags doesn’t work on latest ESPHome Builder