dandri/pyxis
1
0
Fork 0
mirror of https://github.com/torlando-tech/pyxis.git synced 2026-08-27 21:19:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Reduce BLE desync reboot tolerance from 5min to 90s with connections

Browse Source 
A desynced NimBLE host can't actually communicate over existing
connections, so they're effectively zombies. Waiting 5 minutes left
the device unresponsive. 90s gives enough time for self-recovery
while avoiding prolonged dead states.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
torlando-tech
2026-02-23 16:39:43 -05:00
co-authored by Claude Opus 4.6
parent 4e1f379d94
commit 5949cd97ff
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
lib/ble_interface/platforms/NimBLEPlatform.cpp
+4 -3
View File
@@ -685,11 +685,12 @@ bool NimBLEPlatform::startScan(uint16_t duration_ms) {
std::to_string(SCAN_FAIL_RECOVERY_THRESHOLD) + ")");
// Only reboot after prolonged desync — brief desyncs self-recover.
// With active connections, data still flows over BLE mesh — we just
// can't discover new peers. Extend tolerance to 5 minutes.
// With active connections, give a bit more time (90s vs 60s) but
// don't wait too long — a desynced host can't actually communicate
// over those connections, so they're effectively zombie connections.
unsigned long reboot_threshold = HOST_DESYNC_REBOOT_MS; // 60s base
if (getConnectionCount() > 0) {
reboot_threshold = 300000; // 5 min with active connections
reboot_threshold = 90000; // 90s with connections (they're likely dead anyway)
}
if (desync_duration >= reboot_threshold) {
ERROR("NimBLEPlatform: Host desynced for " +