I’ve been playing with creating my own wake word following the openWakeWord instructions here, but I’m confused by the lack of a “download to the device step” in the instructions. The instructions state that I copy my .tflite file to Home Assistant, select that file as the wake-up word for my voice assistant then, in ESP Home, select that voice assistant and, I guess, magic should happen.
However, the M5 Atom still wants to respond to “OK Nabu”. In fact, whatever pre-existing wake-word I select (e.g. “Hey mycroft”, as configured in the pictures below), the M5 Atom still responds to “OK Nabu”, and “OK Nabu” alone.
Is this expected, i.e. does the M5 Atom always respond to all wake-words anyway, and “OK Nabu” is the only one that works? Or can the M5 Atom only have that wake-word and it will ignore all other settings (hence it being greyed out in the configuration)? I tried selecting having the processing in Home Assistant rather than in the device but that resulted in no wake-up words being recognised at all.
Confused…
Did you reconfigure the end device to not use microWakeword?
I believe you need to use the continuous wake word detection example.
1 Like
Huh, thanks for that. I followed the flow in 13 dollar voice assistant for Home Assistant, which installs this m5stack-atom-echo.yaml, slightly different from the one you pointed at, though whether the differences are significant I can’t tell.
But, re-reading the explanation on the “about wake word” page, I realise that I have been confused between microWakeWord and openWakeWord; I now understand that openWakeWord is always run on the Home Assistant server, and the bullet point below says:
follow the guide to the $13 voice assistant. This tutorial is using the tiny ATOM Echo, detecting wake words with openWakeWord.
What causes confusion is that there is a setting under the ATOM Echo device for where the wake-word detection engine is run:
…which I can’t find a mention of in the documentation. I guess that when I have that set to “on device” (ATOM Echo light is white) the ATOM Echo device is performing local wake-word detection with a hard-coded “OK Nabu” of its own and that, for any of the openWakeWord stuff to operate, it needs to be set to “Home Assistant” (ATOM Echo light is magenta). Since all of the documentation suggests you use “OK Nabu” you’d never know the difference between the two cases.
As mentioned above, with the wake-word detection engine set to “Home Assistant” nothing worked for me but I’ve now tried again with debug switched on and it is reacting to “Hey Mycroft” and not “OK Nabu” now.
And, pointing the voice assistant to it instead of “Hey Mycroft”, my own-trained wake-up phrase does work! So all is good in the end.
Thanks again.
