Wake word detection stops working.

[KamilKeski]

Describe the bug

After an indeterminate amount of time it stops responding to wake words.

Steps to reproduce

No reliable repro steps atm. After varying periods of inactivity wake words stop being recognized. The device is still online and reporting to HA. You can toggle led's, change different states, change wake words. However it will not start responding to wake words until rebooted.

Expected behavior

Continues to respond to wake words.

Environment

• OS: HAOS
• None as this part is onboard.

Additional context

Add any other context about the problem here.

Short log included below showing it going into idle, then never responding to a wake word. But responding do other actions, including changing the wake word.

Satellite1 4e8898 Wake word changed to Hey Jarvis triggered by action Select: Select
8:08:12 AM - 10 minutes ago - Kamil
Satellite1 4e8898 Wake word changed to Okay Nabu triggered by action Select: Select
8:08:02 AM - 10 minutes ago - Kamil
Satellite1 4e8898 LED Ring turned off triggered by action Light: Turn off
8:07:57 AM - 10 minutes ago - Kamil
Satellite1 4e8898 LED Ring turned on triggered by action Light: Turn on
8:07:55 AM - 10 minutes ago - Kamil
Satellite1 4e8898 Wake sound turned on triggered by action Switch: Turn on
8:07:42 AM - 10 minutes ago - Kamil
Satellite1 4e8898 Wake sound turned off triggered by action Switch: Turn off
8:07:38 AM - 10 minutes ago - Kamil
February 6, 2025
Satellite1 4e8898 Assist satellite changed to Idle
1:17:27 PM - 19 hours ago

[Zealand67]

Same behavior on my system. Usually after 24 hours after reboot stop responding to wake word. Reboot is only solution seems to help

[that1guy]

This is a known issue we're trying to track down.

Please share any logs you can get your hands on that are relevant to this issue.

[ddaudio1985]

I have a Sat1 sitting at my desk, I also had the same issue of the wake word stops responding. It would stop responding regardless of if it were a speaker or 3.5mm. When the speaker was connected It seemed to have gone longer without any issues but still did after a few days. With the external speaker (3.5mm) connected it seems that it would only last maybe a day or two then stop responding, but I noticed if I do not have a speaker nor a 3.5mm connected it stays up and recognizes the wake word with no issue's. It has been up for about a week without it failing in that configuration. I hope this helps narrow down where the bug is.

Another observation is, when the Sat1 is used on a regular basis (multiple times a day) I didn't have the issue of the wake word not responding, only when I had to go into the office and left it sitting idle for a couple of days.

[gnumpi]

Usually after 24 hours after reboot stop responding to wake word

When the speaker was connected It seemed to have gone longer without any issues but still did after a few days. With the external speaker (3.5mm) connected it seems that it would only last maybe a day or two then stop responding, but I noticed if I do not have a speaker nor a 3.5mm connected it stays up and recognizes the wake word with no issue's. It has been up for about a week without it failing in that configuration. I hope this helps narrow down where the bug is.

Another observation is, when the Sat1 is used on a regular basis (multiple times a day) I didn't have the issue of the wake word not responding, only when I had to go into the office and left it sitting idle for a couple of days.

These are very helpful observations, thanks for sharing.

[that1guy]

Quick update here: We are waiting on future variant of the Sat1 HAT from the manufacturer that enables us to more closely debug the XMOS with a JTAG connector. Thank you for everyone's patience as we get the correct hardware on our desks to find the root cause.

[tsx-5]

Thought I would add my own, not very scientific, observation. I have two of these great devices - recently I placed one in the living room and one in my basement. The living room one is driving a small speaker, the basement one is using the 3.5 mm audio out. The most notable difference between the two locations is background noise - where the basement has a lot more computer fan noise. What I have observed is that the one in the basement has shown this issue within a day, while the one in the living room has not shown it at all.

[that1guy]

We are testing a firmware internally to try and isolate this issue. Updates are coming. Please drop any information here that can help with the troubleshooting.