Skip to content

Yeraze/meshmonitor

v3.4.1 Feature

This release adds 1 notable feature for engineering teams evaluating rollout.

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

Added a Proxmox LXC container template for MeshMonitor deployment.

Full changelog

What's Changed

New Features

  • Spam Detection: Added detection for nodes with excessive packet rates in the Security tab (#1696, closes #1690)
  • Script Arguments: Added script arguments support for AutoResponder, Timer, and Geofence triggers with token expansion (#1691, closes #1685)
  • Geofence Enhancements:
    • Added "None" channel option and {IP} token for geofence triggers (#1686)
    • Added "Verify Response" option for geofence triggers (#1693)
  • Accuracy Regions: Changed accuracy circles to rectangles for better GPS precision visualization (#1694, closes #1688)
  • Long Message Support: Added automatic message breakup for long API messages (#1695, closes #1689)

Bug Fixes

  • Phantom Telemetry: Filter out phantom telemetry packets from packet log - these were internal device state updates incorrectly logged as TX packets (#1697)
  • Position History: Fixed position history not working on PostgreSQL/MySQL backends (#1692)

Other

  • Translation updates from Weblate (#1674)

Pull Requests

  • #1698 - chore: bump version to 3.4.1
  • #1697 - fix: filter phantom telemetry packets from packet log
  • #1696 - feat: add spam detection for nodes with excessive packets
  • #1695 - feat: add multi-message breakup for long API messages
  • #1694 - feat: change accuracy circles to accuracy regions (rectangles)
  • #1693 - feat: add Verify Response option to Geofence Triggers
  • #1692 - fix: position history not working on PostgreSQL/MySQL backends
  • #1691 - feat: add script arguments for AutoResponder, Timer, and Geofence triggers
  • #1686 - feat: add "None" channel option and {IP} token for geofence triggers
  • #1674 - Translations update from Hosted Weblate

Issues Closed

  • #1690 - [FEAT] AutoBan for Spam
  • #1689 - [BUG] Long messages sent via the API get stuck pending
  • #1688 - [FEAT] Show Accuracy as Rectangle on Map
  • #1685 - [FEAT] Geofence / Script / Remote Admin

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.4.0...v3.4.1


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

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:3.4.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.

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]