Preserve telemetry preferences and routes across storage failures

This commit is contained in:
mikecarper committed 2026-10-03 18:34:12 -07:00
1 parent 645c8a1119
commit 0cf1fcead9
9 files changed
+892 -52

No files matched your search

+8
View File
@@ -47,6 +47,14 @@ history is entirely zero are treated as disconnected and are not sent. The
command requires at least one collected base sample and works even when the
automatic schedule is off.
Schedule changes are saved transactionally; a failed write does not truncate
the previous preferences. A legacy route must be successfully migrated into
`data.tx` before its schedule can run. Corrupt, unreadable, or ambiguously
committed preferences stop automatic and pending sends. `get telemetry.tx`
shows `fault=prefs`, and manual sends return an error instead of acknowledging
work that cannot run. Such a storage fault must be repaired before settings
can be changed; the firmware does not overwrite an unmigrated legacy file.
## Decode a packet
<div class="telemetry-tool" data-telemetry-decoder>