Skip to content

Yeraze/meshmonitor

v3.4.7 Feature

This release adds 2 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

Summary

AI summary

Auto Time Sync adds automatic server‑to‑node time synchronization.

Full changelog

What's Changed

New Features

  • Auto Time Sync — Automatically sync server time to nodes without NTP/GPS capability. Supports configurable intervals, expiration hours, and node filtering. Available in the Automation tab. (#1807)

  • Persistent Ignored Nodes — Ignored nodes are now stored in a dedicated database table and survive database pruning. Fixes #1796. (#1801)

Bug Fixes

  • Fix traceroute scheduler timer leaks — Prevent timer leaks when auto-traceroute scheduler is restarted, and enforce 30-second minimum interval between traceroute sends to respect Meshtastic firmware rate limits. Fixes #1805. (#1806)

  • Fix verifyResponse checkbox — The "Verify Response" checkbox for geofence triggers and auto-responders was being ignored. DMs now correctly use 1 attempt when disabled or 3 attempts when enabled. (#1808)

  • Fix map popup positioning — Improved map popup positioning and traceroute behavior. Fixes #1798. (#1803)

  • Rename "Most Active Node" to "Most Recently Heard" — The dashboard label now accurately reflects what the metric shows. Fixes #1800. (#1802)

Translations

  • Translation updates from Hosted Weblate (#1799)

Issues Resolved

  • #1805 - [BUG] Auto-Traceroute sends traceroute requests too frequently
  • #1800 - [BUG] node diagrams and most active node mismatch
  • #1798 - [BUG] position of node popup on map not fully fixed
  • #1796 - [BUG] Logic Deadlock: Ignored nodes are permanently lost after Database Pruning

Pull Requests

  • #1801 - feat: persistent ignored nodes list
  • #1802 - fix: rename 'Most Active Node' to 'Most Recently Heard'
  • #1803 - fix: improve map popup positioning and traceroute behavior
  • #1806 - Fix traceroute scheduler timer leaks and enforce minimum send interval
  • #1807 - feat: add Auto Time Sync feature for nodes without NTP/GPS
  • #1808 - fix: respect verifyResponse setting for geofence and auto-responder
  • #1799 - Translations update from Hosted Weblate

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.4.6...v3.4.7


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

📦 Installation

Docker (recommended):

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

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