fix: reconnect reliably after radio restarts (TCP + serial) - #38
Merged
Conversation
…ackoff, and liveness watchdog
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
_on_disconnected(non-manual) now triggers the!adm restartteardown/rebuild path — every recovery is a full startup resync.amain(): signals (shutdown_event) now override internal restarts; unreachable radio retries with capped exponential backoff (5s→60s, forever) instead of exiting.watchdog_intervalregistry setting (default 180s, 0=off): periodic device-query probe; 2 misses → restart. Catches half-open TCP sockets after silent power-cycles (no keepalive, idle bot may never send). Auto-appears in web UI/API/!adm setting.CONNECTED{reconnected}(lib recovered a short blip): refresh self_info + force contact re-sync.tests/test_reconnect.py(11 tests); suite now 96 passing.Breaking changes
None. Serial unaffected except recovery now works; by-id device paths already recommended.
🤖 Generated with Claude Code