REALTIME WEBSOCKET
Heartbeat and reconnect
The production WebSocket lifecycle keeps desired commands, applied state and telemetry explicit.
Recover without storms
- Use bounded reconnect intervals/backoff.
- Enable heartbeat and keep the socket loop non-blocking.
- After re-authentication, publish presence and current applied state.
- Do not create parallel reconnect loops.