Right now, if you are NOT running VAD with your satellite, it can get stuck in WakeStreamingSatellite event_from_mic.
I'm running multiple satellites in Docker containers with mic / playback / satellite containers on them, no VAD. ( In fact, there is no VAD in the Docker container build, but that's a problem for tomorrow. )
What:
Added in a timeout to WakeStreamingSatellite event_from_mic based on the timeout in VadStreamingSatellite event_from_mic. I figured we should be doing about the same thing there.
The one caveat being this is based on the setting self.settings.vad.wake_word_timeout. I didn't feel like adding in a new setting. Let me know if you want that setting genericized or something.
Testing:
I've had a variant of this container running stably for about a week now. No getting stuck. 🙌
Why:
Right now, if you are NOT running VAD with your satellite, it can get stuck in WakeStreamingSatellite event_from_mic.
I'm running multiple satellites in Docker containers with mic / playback / satellite containers on them, no VAD. ( In fact, there is no VAD in the Docker container build, but that's a problem for tomorrow. )
What:
Added in a timeout to WakeStreamingSatellite event_from_mic based on the timeout in VadStreamingSatellite event_from_mic. I figured we should be doing about the same thing there.
The one caveat being this is based on the setting self.settings.vad.wake_word_timeout. I didn't feel like adding in a new setting. Let me know if you want that setting genericized or something.
Testing:
I've had a variant of this container running stably for about a week now. No getting stuck. 🙌