Journey event  ·  14 Sep 2026

Hub uptime in /fleet freezes at the first post-boot sample (sensor rarely publishes inside the 5 s subscribe window)

SEEN 2026-09-07: after the hub OTA reboot /fleet showed uptime 3.27 s for 10+ minutes while temperatures kept updating and last_seen advanced — the uptime sensor's state only arriv

  state copied from the tracker, never improved

  event date 2026-09-14

Event date 2026-09-14
Version found
Version fixed
Expected kit firmware
Release file
SHA-256
Served count
Source https://app.notion.com/3d32b4cda37081c0b59be0e32dd59f0b

SEEN 2026-09-07: after the hub OTA reboot /fleet showed uptime 3.27 s for 10+ minutes while temperatures kept updating and last_seen advanced — the uptime sensor’s state only arrives if it publishes during the short per-poll subscribe window, so the cached first value sticks. Cosmetic, but it defeats ‘did it reboot?’ checks (I initially read it as a stuck ingest). Option: take uptime from device_info / a dedicated longer subscribe, or drop the field from the fleet payload.

All events  ·  DSC  ·  CannaLib  ·  Site  ·  Firmware releases

Empty rows are honest

A blank cell means the tracker has no value for it. Nothing on this page is filled in to look complete.