Files
ZephCore/zephcore
rlwilliamson-dev 58dbba7f3b room-server: drive push engine on a timer + cut delivery latency
Two hardware-found fixes after on-air testing on the GAT562 kit:

- Add a 500ms push timer in main_room_server.cpp so the post-sync
  engine advances at its intended cadence. ZephCore is event-driven
  (no Arduino superloop), so without this the engine only ran on the
  5s housekeeping tick — posts dripped out every ~5s and transmits
  bunched up, causing timeouts/resends.

- Lower the post-sync hold from upstream's conservative defaults
  (POST_SYNC_DELAY 6s -> 2s, PUSH_NOTIFY 2000ms -> 1000ms). These are
  server-side timing only (no wire-format change), and take measured
  delivery from ~6-7s down to ~2s.

Verified on hardware (910.525/62.5/SF7/CR8, two clients): normal-pace
messages deliver in ~2s with clean ACKs. Rapid-fire bursts can still
drop out-of-order messages via the per-client timestamp replay check
(unchanged from upstream) — left as-is to stay upstream-compatible.
2026-06-02 14:12:08 -05:00
..
2026-06-02 14:50:31 +02:00
2026-06-02 13:02:57 -05:00
2026-06-02 14:50:18 +02:00
2026-06-02 16:08:51 +02:00
2026-03-19 10:44:33 +01:00
2026-06-02 13:02:57 -05:00
2026-06-02 13:02:57 -05:00
2026-06-02 16:08:51 +02:00
2026-06-02 14:50:18 +02:00
2026-02-22 13:09:18 +01:00
2026-05-31 20:51:59 +02:00