Skip to content

Yeraze/meshmonitor

v4.11.6 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

Published 1mo Monitoring & Metrics
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

meshcore meshtastic mqtt

Summary

AI summary

Updates MeshCore, Fix, and Meshtastic / general across a mixed release.

Full changelog

MeshMonitor 4.11.6

Maintenance release on the 4.11.x line. Includes all fixes and features merged since 4.11.5 except the Automation Engine (#3653), which ships in 4.12.

MeshCore

  • Region/scope support — phase 1: per-channel scope (#3667)
  • Scope all originated flood traffic — phase 2 (#3667)
  • Region discovery from nearby repeaters — phase 3 (#3667)
  • Per-message scope/region override (#3701)
  • Channel "heard repeaters" via self-echo correlation (#3700)
  • Show unread message indicator on the Channels view (#3703)
  • Manual telemetry poll buttons (#3674)
  • 2/3-byte path hash support in the Define Path editor (#3670)
  • Last Heard shows the date when a node was heard before today (#3656)
  • Fix: honor Temperature Unit on the DM telemetry graph (#3659)
  • Fix: reduce set_out_path timeout and improve the error message (#3664)
  • Fix: low-battery and inactive-node notifications never fired (#3672)
  • Fix: clarify LPP telemetry WARN and stop pubkey/nodeNum log spam (#3680)
  • Fix: honor the packet-monitor Max-count setting in the live list (#3690)
  • Fix: Discover Regions always timed out due to a missing Sent payload (#3682)
  • Fix: stop the virtual node server during transport teardown (#3705)
  • Fix: correlate LogRxData path by hop count so {ROUTE} resolves on routed messages (#3710)

MQTT

  • Fix: consolidate channels by name instead of splitting by slot/hash (#3708)
  • Fix: identify channels by name and key, and enumerate them on the Channels tab (#3712 follow-up)

Map

  • Fix: make spiderfy work and stop auto-collapse on Map Analysis & Unified maps (#3685)
  • Rich multi-source node popups matching the Unified map (#3692)

Meshtastic / general

  • Fix: always send traceroutes on channel 0 (Primary) (#3696)
  • Fix: resolve position-packet channel from decryption context, not the raw hash (#3682)
  • Fix: persist & surface local node isUnmessagable/isLicensed (#3684)
  • Fix: scope manual device backup to the selected source (#3711)
  • Fix: scope channel queries, mark-read & message migration by sourceId (#3712)

Notes

  • Database migrations 098–102 on this line correspond to the 100–104 migrations on the 4.12 (main) line; upgrading 4.11.6 → 4.12 re-runs them idempotently and applies the Automation Engine migrations fresh — no data loss or manual steps.

🚀 MeshMonitor v4.11.6

📦 Installation

Docker (recommended):

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

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

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Yeraze/meshmonitor

Get notified when new releases ship.

Sign up free

About Yeraze/meshmonitor

All releases →

Related context

Earlier breaking changes

  • v4.13.0 Source‑scoped API endpoints now require an explicit `sourceId` parameter.
  • v4.13.0 Auto-Upgrade is retired; remove upgrade sidecar and related config.
  • v4.7.2 Route `destination` field now rejects non‑8‑hex nodeId or 64‑hex publicKey, returning HTTP 400.

Beta — feedback welcome: [email protected]