AWTRIX NG (next generation firmware)

Blueprints Exchange
22

I don’t know why it is spamming the activity log. What is the activity? Uptime I understand, but that only needs to update with a time stamp when it boots?

If I use the uptime entity to trigger something, it will trigger all the time, not just when the awtrix display starts, right?

I might misunderstand the concept.

23

OK
0.1.5

Uptime now rounds to the minute instead of recomputing from utcnow()
on every 5s poll, which was writing a near-identical new state every
poll and flooding the logbook. Added a separate “Last boot” timestamp
sensor that only updates when the computed boot time actually jumps
(reboot), so it can be used as a reboot trigger.

24

Thanks a lot!

This looks much better. No activity log spamming with useless state changes.

Screenshot 2026-08-13 at 11.10.40
Screenshot 2026-08-13 at 11.10.402800×196 12.8 KB

What is now the difference between the Uptime and the Last boot timestamp?

Screenshot 2026-08-13 at 11.09.57
Screenshot 2026-08-13 at 11.09.57790×176 9.7 KB

25

Both currently show the same value because the device hasn’t rebooted since either was last updated - but they update very differently:

  • Uptime recomputes every poll and rounds to the minute. It keeps ticking/refreshing on its own even without a reboot (as time passes, it stays “how long ago the device booted” - it’s a live “time since boot” readout, so its displayed value can shift by a minute here and there).
  • Last boot is a fixed timestamp that only changes when the device actually reboots (detected as a >30s jump in computed boot time). Between reboots it never fires a state change - so it’s safe to use as a reboot trigger. Uptime is not, because it updates on its own schedule too.
26

OK … I don’t see Uptime updating, but I personally don’t mind, since I don’t need the uptime to be calculated since the time stamp is in the state of both Uptime and Last boot. Maybe there is something I don’t understand, but I am still curious why we see different things for the Uptime entity.

27

image
image1258×668 69.3 KB

and btw fixed.