Issue:
When I set the “Wake word engine location” to “On device”, I can use “OK Nabu”, the LED turns blue, I can say a command and it gets executed. After that, the LED goes back to white and I can say “OK Nabu” again.
When I set the “Wake word engine location” to “In Home Assistant”, I can use “OK Nabu”, the LED turns blue, I can say a command and it gets executed. After that, the LED goes to a light blue/cyan and it stops responding to “OK Nabu”… No matter how long I wait, it never responds again.
If I power cycle it, it still lights up in cyan. I wait for it to be back available (~1min) and it responds to “OK Nabu” again, but again only one time; after that it’s again unresponsive…
I have the exact same experience. if you push the button on the m5, it will listen for another word again. I tried to see about setting up an automation that would push the button once the m5 went back to idle, but couldn’t figure out how to actually “push the button” there didn’t seem to be an option for it.
Anyone have any ideas about the automation I’m trying to set up or this issue in general?
Same here: m5stack Atom Echo, “On device” works, wake word in “Home Assistant” works once. Works again (once) after I press the button on the atom echo.
I have found a work around for this exact issue.
Set up an automation.
The trigger is when the “device” (the Atom M5) goes to “idle”.
The action is to set the wake word location to where it already is. In my case it was “In Home Assistant”. In my case this was the top or first option.
So trigger is when m5 goes idle and action is to set wake word location to “first”.
