Avoid Companion request tag collisions after login

This commit is contained in:
mikecarper committed 2026-10-05 01:47:05 -07:00
1 parent cc4bcb9cad
commit 982f96ca96
11 files changed
+106 -19

No files matched your search

+4
View File
@@ -22,6 +22,10 @@ layout before installing an image.
- Access Control replies fit the encrypted LoRa route budget and the
Companion frame envelope. Large ACL listings use bounded pages. ESP32 ACL
persistence avoids repeated metadata opens while retaining recovery checks.
- Companion requests skip recently used reply tags. A login reply whose
server timestamp matches the next client timestamp no longer causes an
immediate status or ACL request to fail locally. Stale replies remain
blocked, and tag selection does not change the radio's wall clock.
- nRF52 keeps its 8 KiB loop stack. Crypto, contact CRC and background storage
work reduce peak stack use and long pauses. OTA metadata is cached after
verification instead of repeatedly reopening storage for status displays.