Landed 2026-09-07 (feat/dashboard-v2, uncommitted; Pass S4). Settings > System > Time: brain clock + zone (Australia/Sydney), NTP status via timedatectl (unknown on hosts without it), hub clock + drift with a tone chip (<5 s ok, <60 s warn, else failed state), hub uptime, and the note that photoperiods run on the hub's own sntp clock. Brain: GET /system/time (system_info.py). Firmware: new text sensor 'Hub Clock' (epoch seconds or 'unsynced', 30 s) mapped to hub_clock_epoch. Until the hub is flashed with it the row says 'this firmware does not publish its clock'. Needs: Pi hotpatch + hub flash, then check drift on the live kit.
Journey event · 7 Sep 2026
No timezone / NTP / hub-vs-brain clock drift surface although photoperiods depend on hub local time
Landed 2026-09-07 (feat/dashboard-v2, uncommitted; Pass S4). Settings > System > Time: brain clock + zone (Australia/Sydney), NTP status via timedatectl (unknown on hosts without i
● state copied from the tracker, never improved
● event date 2026-09-07
| Event date | 2026-09-07 |
| Version found | |
| Version fixed | |
| Expected kit firmware | |
| Release file | |
| SHA-256 | |
| Served count | |
| Source | https://app.notion.com/3d42b4cda3708165809ac099f671d620 |
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.