Skip to content

Yeraze/meshmonitor

v3.6.0 Feature

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

Published 3mo 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

Affected surfaces

deps

Summary

AI summary

Auto-Ping automation adds DM‑command driven connectivity testing with latency summary.

Full changelog

What's Changed

New Features

  • Auto-Ping automation — A new DM-command driven ping feature lets mesh users test connectivity and measure latency. Users DM ping N to start pings with ACK/NAK/timeout tracking and receive a summary with min/avg/max latency. Admins configure interval, max pings, and timeout in the Automation tab. (#1917, closes #1894)
  • Telemetry packet ID tracking — Telemetry records now include packetId from the originating mesh packet, enabling API consumers to de-duplicate data received via multiple mesh paths. (#1921)

Improvements

  • Virtual Node firmware branding — VN connections now report firmware as 2.6.6-MM3.6.0, identifying the connection as a Virtual Node running on MeshMonitor. (#1920)
  • Virtual Node channel stability — Fixed configComplete broadcasts during physical radio reconnection causing VN clients to lose their channel list. Disabled channel slots (role=0) are now sent to match real device behavior. (#1920)
  • Poll/unread optimization — Batch queries for /api/poll and /api/unread-counts reduce database load with MySQL support. (#1909)
  • Automation documentation — Added missing docs for Auto-Ping, Auto Key Management, and Ignored Nodes. (#1918)

Bug Fixes

  • Packet distribution portnum total — Portnum filter now correctly applies to total count in the packet distribution API. (#1919)
  • Mobile infinite scroll — Fixed infinite scroll and always-visible virtual channels on mobile. (#1907, closes #1908)
  • Hide accuracy region for overridden positions — Position accuracy indicators no longer show for manually overridden node positions. (#1910)

Dependencies

  • Bump serialport from 12.0.0 to 13.0.0 (#1915)
  • Bump @serialport/parser-readline from 12.0.0 to 13.0.0 (#1913)
  • Bump production dependencies (jose, jiti, sass, sharp) (#1911)
  • Bump @typescript-eslint/eslint-plugin (#1916)
  • Bump @typescript-eslint/parser from 8.54.0 to 8.55.0 (#1912)
  • Bump jsdom from 28.0.0 to 28.1.0 (#1914)

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.5.1...v3.6.0


Proxmox LXC Template

This release includes a Proxmox-compatible LXC container template for MeshMonitor.

Installation

  1. Download the .tar.gz template file
  2. Verify the SHA256 checksum (optional but recommended)
  3. Upload to your Proxmox server: scp meshmonitor-*.tar.gz root@proxmox:/var/lib/vz/template/cache/
  4. Create a new LXC container from the template via Proxmox web UI
  5. Configure /etc/meshmonitor/meshmonitor.env with your Meshtastic node IP
  6. Start the container and access the web UI on port 8080

Documentation

See the Proxmox LXC Deployment Guide for detailed instructions.

Limitations

  • Auto-upgrade feature is not supported in LXC deployments
  • Manual updates required (download new template for each version)
  • Community-supported (Docker remains the primary deployment method)

🚀 MeshMonitor v3.6.0

📦 Installation

Docker (recommended):

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

🧪 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.7.2 Route `destination` field now rejects non‑8‑hex nodeId or 64‑hex publicKey, returning HTTP 400.

Beta — feedback welcome: [email protected]