Files
misadeksandCopilot App d9b79ad17d MS UI link: fast reconnect (1s) to the control/telemetry WebSocket
The control and telemetry workers already try to connect immediately when they
start, but they only retried every 15s when the UI was unavailable — so if the
operator UI started after (or restarted independently of) the radio, it took up
to 15s to (re)connect. Cut RECONNECT_DELAY 15s -> 1s in both workers so the
radio reconnects within ~1s of the UI appearing.

To keep the journal clean under the faster cadence, log the connection failure
once per down-period at WARN, then quietly at DEBUG until it reconnects (added a
`down_logged` flag reset on a successful connect). The first attempt is still
immediate on worker start.

- net_control/worker.rs, net_telemetry/worker.rs: RECONNECT_DELAY 15s->1s;
  warn-once-then-debug reconnect logging.
- docs/MS_CONFIG.md: document the immediate-connect + ~1s retry behaviour.

Logging/timing of the UI link only; no protocol/stack behavior changed.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
2026-08-09 01:36:26 +02:00
..