#Voice assistant stops recognizing wake word

1 messages · Page 1 of 1 (latest)

steel cedar
#

Same issue as here https://community.home-assistant.io/t/voice-pe-stops-recognizing-wake-word-and-requires-reboot/818140/4
I have 3 satellites that are connected to my main server with HA. The wake word randomly just stops recognizing. Everything is running and satellites are confirmed to be streaming audio to HA, but no resposne.
Only reboot helps.
This does not happen however if I run wakeword locally on each of the satellites. The reason I want a centralized wakeword is to prevent several satellites being triggered at once.
Any ideas?

Home Assistant Community
Voice PE stops recognizing wake word and requires reboot

I have now configured a static IP for the Voice Assistant PE to see if that helps. My issue was happening when using Nabu Casa or Open AI. Other than that (and using Jarvis instead of Nabu), everything else is on default settings, running via the Pi 4. The static IP approach solved a similar issue I had with my Google Nest Hub thingy a while b...

#

also, noticed this in whisper logs at the exact moment it hanged on me. So maybe the problem is with Whisper?

ERROR:asyncio:Task exception was never retrieved future: <Task finished name='wyoming event handler' coro=<AsyncEventHandler.run() done, defined at /usr/local/lib/python3.11/dist-packages/wyoming/server.py:31> exception=ConnectionResetError('Connection lost')> Traceback (most recent call last): File "/usr/local/lib/python3.11/dist-packages/wyoming/server.py", line 41, in run if not (await self.handle_event(event)): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/wyoming_faster_whisper/handler.py", line 79, in handle_event await self.write_event(Transcript(text=text).event()) File "/usr/local/lib/python3.11/dist-packages/wyoming/server.py", line 29, in write_event await async_write_event(event, self.writer) File "/usr/local/lib/python3.11/dist-packages/wyoming/event.py", line 131, in async_write_event await writer.drain() File "/usr/lib/python3.11/asyncio/streams.py", line 378, in drain await self._protocol._drain_helper() File "/usr/lib/python3.11/asyncio/streams.py", line 167, in _drain_helper raise ConnectionResetError('Connection lost') ConnectionResetError: Connection lost

wild robin
steel cedar
#

@wild robin it’s true only if you run a single wakeword on HA and not on satellites. Otherwise they all wake up when they hear it

#

That is why I moved WW from satellites to HA and now experiencing this other issue…

wild robin
steel cedar
#

Interesting. Could you share your satellite command? Maybe there is something I’ve misconfigured because for me they all wake up if they hear me. Also, I am running openwakeword

wild robin
#

what do you mean by satellite command?
what sattelites are you actually using?

steel cedar
#

I have 3 raspberry pi zero 2w that run Wyoming-satellite in docker containers

#

When you run the Wyoming satellite you provide certain flags as input parameters

wild robin
#

oh right, wyoming satelite is a bit behind in functionality

steel cedar
#

what are you running?

wild robin
#

esphome based sattelites

#

plus some custom

steel cedar
#

ah, well. That’s probably why.
Do you run microwakeword in HA? Or does each of those satellites run their own instance of wakeword?

wild robin
#

it means it doesnt have to constantly stream

steel cedar
#

gotcha.
With Wyoming-satellite + VAD you can make it stream only when it hears the voice, but it bugs out randomly as described above…

wild robin
#

yeah i see what you mean now. in the future i recommend moving over to esphome based stuff as that is where most of the development is going. stuff will likely filter down to wyoming in the end but it may take time.

i also get that this doesnt help your current situation though

#

can you run the WW's local which gives you the problem of dupe activations then use an automation that when 1 triggers (whichever one gets there first) home assistant stops listening on the others until the device asist entity goes back to idle then switches them all back on?

steel cedar
#

I can run it locally, yes. Will need to figure out the automation part

wild robin
#

yeah, i am not entirily sure how the stuff works in wyoming and how to approach the automation but do you see what i am driving at in concept?