What's Fixed in v1.8.1
Critical Bug Fix: Mesh Traffic Blocking
Fixed a critical bug that was preventing the system from receiving live mesh traffic, causing only historical data to be displayed.
Problem: The system was calling sendWantConfigId() every 60 seconds during normal operation, which triggered the Meshtastic node to restart its full configuration dump sequence. This blocked the receipt of actual mesh packets (messages, telemetry, etc.).
Solution: Removed periodic configuration requests from the polling loop. Configuration is now only requested once during initial connection, allowing the system to properly receive live mesh data.
Impact
- ✅ Live mesh data now displays correctly
- ✅ No more repeated configuration dump loops
- ✅ Messages and telemetry updates appear in real-time
- ✅ Continuous nodeInfo updates received properly
Technical Details
- Removed periodic
sendWantConfigId()calls that were blocking traffic - System now polls for mesh packets every 2 seconds without interruption
- Node naturally sends updates as they occur on the mesh network
Full Changelog: v1.8.0...v1.8.1
🚀 MeshMonitor v1.8.1
📦 Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:v1.8.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.