You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In certain environments this works quite well and the HA connection is immediately available after WiFi is connected. However, this can also cause connectivity issues after the device wakes up and take longer to detect a no longer working WebSocket connection.
With the upcoming, renewed connection logic in the core (unfoldedcircle/feature-and-bug-tracker#320) the integration should disconnect from HA when entering standby, and immediatly reconnect when receiving the exit_standby event.
This might also help with the following HA server log entries: Client unable to keep up with pending messages (unfoldedcircle/feature-and-bug-tracker#301). Assumption: remote is in standby and HA tries to send entity change events over the still open WebSocket connection.
The text was updated successfully, but these errors were encountered:
New option to disconnect from HA server when the device enters standby
and immediately reconnects when leaving standby (enabled by default).
This is controlled by the `enter_standby` and `exit_standby` events from
Remote Two.
Closes#50
New option to disconnect from HA server when the device enters standby
and immediately reconnects when leaving standby (enabled by default).
This is controlled by the `enter_standby` and `exit_standby` events from
Remote Two.
Closes#50
When running on the Remote Two device, the WebSocket connection to the HA server is currently kept open when the device enters suspend mode.
The Remote Two sends the
enter_standby
andexit_standby
events, but they aren't being used yet in the integration besides setting a flag:integration-home-assistant/src/controller/handler/r2_event.rs
Lines 36 to 42 in 6cbc80e
In certain environments this works quite well and the HA connection is immediately available after WiFi is connected. However, this can also cause connectivity issues after the device wakes up and take longer to detect a no longer working WebSocket connection.
With the upcoming, renewed connection logic in the core (unfoldedcircle/feature-and-bug-tracker#320) the integration should disconnect from HA when entering standby, and immediatly reconnect when receiving the
exit_standby
event.This might also help with the following HA server log entries:
Client unable to keep up with pending messages
(unfoldedcircle/feature-and-bug-tracker#301). Assumption: remote is in standby and HA tries to send entity change events over the still open WebSocket connection.The text was updated successfully, but these errors were encountered: