MeshMonitor v4.17.2-rc1

MeshCore Companion sources gain Auto Ping: a contact who DMs ping N gets a run of pings back and a summary. The limits match Meshtastic's Auto Ping, and it is off by default. MeshCore Node Details gets a Show on Map button that opens the map on the node with its popup. On the Unified Telemetry dashboard, a reading the node takes itself, such as battery or temperature, now draws one line merged from every source. A Split by source toggle brings back the per-source lines. In Link Profile, you can drag the endpoints, and panning the map no longer drops a point. The Nodes list can filter nodes that are hidden from the map. The ducting overlay now centres on your own nodes. Reticulum attach mode now works in Docker, and the bridge recovers from a failed RNS start without a restart.

Features

• MeshCore: Auto Ping (ping N DM command) for Companion sources (#5962)
• MeshCore: Show on Map from Node Details (#5965)
• Unified Telemetry: merge objective telemetry across sources into one line, with a per-chart Split by source toggle (#5966)
• Link Profile: draggable endpoints; panning never picks a point; hold Space to pan freely (#5963)
• Nodes: Hidden from map filter in the Nodes list (#5958)

Bug Fixes

• Ducting: centre the default area on the busiest cluster and your local nodes (#5960)
• Reticulum: recover from a failed RNS start without a manual restart (#5957)
• Reticulum: attach mode puts MeshMonitor on host networking (#5956)

Documentation

• 4.17.1 documentation pass and release post (#5961)

CI/DevOps

• Version bump to 4.17.2-rc1 (#5967)

Issues Resolved

#5931, #5951, #5952, #5953, #5954, #5955, #5959, #5964

Upgrade notes

• Reticulum attach mode (Docker): the overlay now runs MeshMonitor with network_mode: host, and the bridge runs as ${RNS_UID:-1000}:${RNS_GID:-1000} with a read-write ~/.reticulum mount. If you use docker-compose.reticulum.yml, pull the new file, and set RNS_UID/RNS_GID if your Reticulum config is not owned by UID 1000. Set ALLOWED_ORIGINS if you open MeshMonitor anywhere other than http://localhost:3001. The overlay needs Docker Compose 2.24.4 or later (ports: !reset). Helm adds reticulum.securityContext.
• MeshCore Auto Ping is off by default (Automation → Auto Ping on a Companion source).

Full Changelog: v4.17.1...v4.17.2-rc1

🚀 MeshMonitor v4.17.2-rc1

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:4.17.2-rc1

🧪 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.