M5 Echo Issue - Wake word works once after boot, then stops listening or misunderstands commands

Configuration Voice Assistant
1

Hi everyone,
I’m encountering a frustrating issue with my M5 Echo, which is configured with HAOS. I have wake word detection enabled using OpenWakeWord (“Hey Jarvis”).
Here’s the problem:

  • After the M5 Echo boots up, it successfully detects the wake word (“Hey Jarvis”) the first time, as expected.
  • However, after this initial successful detection, it seems to stop listening and no longer responds to the wake word.
  • On the rare occasions it does react to the wake word again after that first time, it fails to understand or process any subsequent voice commands. It acts as if it “doesn’t understand” them, even though the language settings are correctly configured, and the rest of the setup seems to be in order.

I’m using the following Home Assistant add-ons for voice processing:

  • Whisper (for Speech-to-Text)
  • Piper (for Text-to-Speech)
  • OpenWakeWord (for the “Hey Jarvis” wake word)

Has anyone experienced a similar issue where the wake word detection works initially but then fails? Or where commands are not understood despite a seemingly correct setup? Any pointers on what to check or how to troubleshoot this would be greatly appreciated.

Thanks in advance!

2

My M5 would only listen to the first command and then stop responding unless I pressed its button.
What I ended up doing is creating an automation. The trigger is when the M5 goes back to “idle” mode. The action is setting the wake word location to where it already is. In my case I am using Home Assistant to process my wake word and I have a custom one set up. This is the first option in the drop down. so the action is set wake word location to first option.

image
image963×612 25.2 KB