Skip to content

Yeraze/meshmonitor

v3.4.8 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

auth

Summary

AI summary

TOTP-based two-factor authentication (MFA) added to user accounts.

Full changelog

What's New in v3.4.8

Two-Factor Authentication (MFA)

TOTP-based two-factor authentication for user accounts. Set up with any authenticator app (Google Authenticator, Authy, etc.), with 10 single-use backup codes for recovery. Admins can disable MFA for other users if needed.

Auto-Acknowledge Enhancements

  • Per-channel control — enable/disable auto-ack on individual channels and direct messages
  • Tapback & text reply modes — independent toggles for emoji reactions and text responses, each with separate direct/multi-hop settings
  • Always use DM — send responses as direct messages even when triggered by channel messages
  • Sample message preview — live preview of templates with example token values

Position History Line Style

Choose between linear (straight) and spline (curved) line styles for position history tracks on the map.

News Popup UX Improvements

Bulk dismiss, version-gated news items, and improved popup layout.

Bug Fixes

  • Fixed traceroute history always showing empty on PostgreSQL/MySQL deployments

Pull Requests

  • #1815 feat: separate Direct and Multi-hop settings for Auto Acknowledge
  • #1817 fix: traceroute history always empty on PostgreSQL/MySQL
  • #1818 feat: add TOTP-based two-factor authentication (MFA)
  • #1822 feat: add position history line style setting
  • #1824 feat: improve news popup UX with bulk dismiss and version gating
  • #1825 docs: add auto-ack features, MFA section, and security sidebar link
  • #1826 chore: bump version to v3.4.8 with news update

Issues Resolved

  • #1814 [FEAT] Allow more granular fine-tuning of tapback/auto-acknowledge
  • #1816 [FEAT] 2 Factor Auth for admin user (TOTP)
  • #1820 [FEAT] semicircles in position history must die!
  • #1823 [BUG] Auto Acknowledge - Tapback and Reply too fast and getting rate limited

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

📦 Installation

Docker (recommended):

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

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