Closed jiriappl closed 9 months ago
Hey there @balloob, @synesthesiam, mind taking a look at this issue as it has been labeled with an integration (wyoming
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
wyoming documentation wyoming source (message by IssueLinks)
I wonder if we should implement a ping command to detect disconnects.
I have this issue as well, once the satellite is rebooted i have to restart HA or the integration to get a connection working
Im having what I think is this issue? Although, its happening even without reboots. Every couple commands I have to restart the integration and that fixes it for me.
I have the same issue. Any resolution to this?
For the next version of HA (2024.2) and Wyoming satellite version 1.1, this will be be fixed. Pinging between HA and the satellite has been implemented so that the connection can be dropped quickly once either side disconnects.
The problem
I have been using https://github.com/synesthesiam/homeassistant-satellite post Year of Voice Chapter 4 and did not encounter this issue. Post Chapter 5, I have reimaged the satellite (rpi3) with the new Wyoming satellite bits https://github.com/rhasspy/wyoming-satellite, and all works initially. In both cases, I have been using wake word detection on the satellite, using wyoming-openwakeword.
However, if I power cycle the rpi satellite, I can see that wake word is detected and audio streaming starts (based on the events that wyoming satellite emits), but on the HA core, the Assist in progress property of the satellite remains off.
Debugging this a bit further, it seems to be that HA/wyoming protocol integration holds an open connection back to the satellite (iirc port 10700), and that connection does not get dropped even after the satellite gets restarted.
If I reboot HA core, or disable and reenable Wyoming integration, my satellite becomes operational as well (though perhaps that needs to happen also post powercycle of the RPi, as trying more iterations of the repro now, I did not get consistent results). So I think the issue is on the Wyoming integration in HA Core, not on the satellite itself.
As for the specific repro steps, my satellite is deployed using the RPI+ReSpeaker instructions from the wyoming-satellite repo and this reproes if I power cycle the RPI satellite. To note, my powercycle period is about 8 hours, not just a short off/on cycle (power off during night).
Re difference between home assistant satellite (chapter 4) and wyoming satellite (chapter 5), I used the token auth post chapter 4 and for chapter 5 I registered the satellite using the wyoming integration. So possibly the connection was established differently between the two.
Would be happy to debug further if you cannot repro or want more details. I spotted the connection from HA Core/Wyoming integration using netstat, executed from an SSH session exposed using the Advanced SSH addons, without protections and tcpdump/netstat from the rpi satellite.
What version of Home Assistant Core has the issue?
core-2024.1.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Wyoming Protocol
Link to integration documentation on our website
https://www.home-assistant.io/integrations/wyoming/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?