Skip to content

MeshMonitor v4.9.0 β€” Low-battery alerts, airtime cutoff & richer automations

MeshMonitor v4.9.0 focuses on keeping your mesh healthy and your automations polite. Here's what's new.

Low-battery alerts ​

Pick the nodes you care about and get notified when their battery drops below a threshold you set β€” delivered through the same fan-out as your other alerts (Apprise, Web Push, Desktop). It reuses your existing monitored-nodes list, so a remote solar node going dark no longer has to be a surprise. (#3305)

Airtime utilization cutoff ​

A new Cutoff Airtime Utilization Threshold (default 30%) on the Automation page pauses all transmitting automations β€” auto-traceroute, auto-announce, auto-ack, timers, geofence triggers, and more β€” whenever the connected node's Channel Utilization climbs above the threshold. When real people are filling the channel, your bots back off automatically and resume once things quiet down. A live banner shows the current utilization and whether automations are paused; manual actions are never blocked. (#3311)

{LAST_HOP} automation variable ​

Autoresponder and auto-ack templates can now include {LAST_HOP}, which resolves the node that last relayed an incoming message β€” short name when known, a hex byte when it isn't, or unknown when there's no relay info β€” matching the Packet Monitor's display. Great for acknowledging the path a message took. (#3318)

Telemetry time-range selector ​

The Device Info telemetry graphs gained a time-range selector (15 minutes to 7 days), remembered per browser. Long windows now downsample the full history across all database backends instead of silently truncating to the most recent rows on chatty nodes. (#3312)

Fixes worth calling out ​

  • MQTT environment telemetry is visible again. Temperature, pressure, and humidity arriving over MQTT were stored under different keys than serial data and never showed up in the graphs. Ingestion is fixed and a migration repairs existing history. (#3314)
  • Ignored nodes stay ignored. When a radio's node database fills up and drops an ignore, MeshMonitor now re-applies it (and re-pushes it to the device) so the node keeps getting blackholed. (#2601)
  • Plus MeshCore date separators and packet-log fixes, an API rate-limiter exemption for local/reverse-proxy traffic, and a handful of UI and notification correctness fixes.

See the full changelog for the complete list.

Last updated: