Closed zehnm closed 10 months ago
A fresh setup on the remote (e.g. after a factory reset) leaves the integration in DISCONNECTED state. At least from the remote's view. However, the integration is not showing any connection issue and is communicating with HA. Sending connect events (either through web-configurator, or manually with the Core-API) has no effect, since the internal state is already CONNECTED. There's also no device_state event sent back: https://github.com/unfoldedcircle/integration-home-assistant/blob/bbd3f6e329d9b70ae566e566d5ed284d3e2fa52f/src/controller/handler/r2_event.rs#L26-L30
DISCONNECTED
connect
CONNECTED
device_state
After sleep & wakeup, the state is synchronized and the integration is working. Same happens after a reboot.
Discovered while testing unfoldedcircle/feature-and-bug-tracker/issues/237 after user reports of having to reboot the remote.
Required fixes:
A fresh setup on the remote (e.g. after a factory reset) leaves the integration in
DISCONNECTEDstate. At least from the remote's view. However, the integration is not showing any connection issue and is communicating with HA. Sendingconnectevents (either through web-configurator, or manually with the Core-API) has no effect, since the internal state is alreadyCONNECTED. There's also nodevice_stateevent sent back: https://github.com/unfoldedcircle/integration-home-assistant/blob/bbd3f6e329d9b70ae566e566d5ed284d3e2fa52f/src/controller/handler/r2_event.rs#L26-L30After sleep & wakeup, the state is synchronized and the integration is working. Same happens after a reboot.
Discovered while testing unfoldedcircle/feature-and-bug-tracker/issues/237 after user reports of having to reboot the remote.
Required fixes:
device_stateevent back after receiving theconnectevent.