MeshMonitor v4.9.1
A small follow-up to v4.9.0 that adds voltage-based low-battery alerts for MeshCore companions and a neighbour-averaged source for the airtime cutoff, and fixes two regressions: MQTT broker sources showing no nodes on the dashboard/map, and the Auto Traceroute match-list preview ignoring its "Last Heard Within" and "Hop Range" filters.
Features
- MeshCore low-battery alerts (voltage-based) (#3332) — Low-battery notifications now work for MeshCore sources. MeshCore devices report battery as a voltage (mV) rather than a 0–100 percentage, so a new per-user voltage threshold (default 3300 mV) is compared against each monitored node's
batteryMv. The Notifications settings expose both thresholds — percentage for Meshtastic, mV for MeshCore — and the monitored-node picker now lists all MeshCore nodes (not just those with a GPS fix). Resolves #3331. - Airtime cutoff — neighbour-averaged source (#3328) — The airtime-utilization cutoff (Automation page) can now measure Channel Utilization from nearby infrastructure instead of the local node. In "Nearby infrastructure" mode it averages the Channel Utilization of the 3 strongest-RSSI directly-heard (0-hop) router/repeater nodes — useful when a well-placed node under-reports the wider mesh. The live banner shows which source is in use and how many neighbours were sampled.
Bug Fixes
- MQTT broker source dashboard/map showed no nodes (#3333) —
MqttBrokerManagerwas missing thegetAllNodesAsync/getConnectionStatus/getDeviceConfigmethods that the consolidated/api/pollendpoint calls, so those endpoints returned HTTP 500 formqtt_brokersources and the dashboard/map received no node data despite positions being ingested and stored correctly. The broker manager now implements the same DB-backed read methods asMqttBridgeManager. - Auto Traceroute match-list preview ignored filters (#3330) — The Auto Traceroute match-list preview now honours the "Last Heard Within" and "Hop Range" filters instead of showing every node. Resolves #3329.
Issues Resolved
- #3331 — low-battery alerts for MeshCore
- #3329 — Auto Traceroute "Last Heard Within" and "Hop Range" filters not affecting the match list
Full changelog: v4.9.0...v4.9.1
🚀 MeshMonitor v4.9.1
📦 Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:4.9.1🧪 Testing
✅ All tests passed
✅ TypeScript checks passed
✅ Docker images built for linux/amd64, linux/arm64, linux/arm/v7
📋 Changes
See commit history for detailed changes.