Yeraze/meshmonitor v3.1.0

on GitHub

What's New in 3.1.0

New Features

Channel Database for Server-Side Packet Decryption

Store unlimited channel configurations beyond your device's 8 slots and decrypt packets server-side. This allows monitoring encrypted traffic from channels you're not actively participating in.

• Store channel name and PSK combinations in MeshMonitor's database
• Automatic server-side decryption of incoming encrypted packets
• Retroactive processing of historical encrypted packets when adding new channels
• Read-only access (view decrypted content without transmit capability)
• Permission-based access control for non-admin users

See the Channel Database documentation for details.

Enhanced Traceroute Visualization

• Focused view mode for traceroute paths
• Distinct path colors for better visualization

Python Requests Library

User scripts can now use import requests for HTTP calls without manual installation.

Bug Fixes

• PostgreSQL/MySQL schema fixes - Fixed upgrade_history table schema mismatch and boolean type handling for auto_traceroute_log
• Direct neighbors API - Fixed hardcoded URL that caused 404 errors when BASE_URL differs from default
• Bind mount conflicts - Internal scripts now deploy to /data/.meshmonitor-internal/ to avoid conflicts with user script directories during upgrades

Changes Since v3.0.3

• #1547 - feat: add Python requests library to Docker image
• #1544 - fix: move internal scripts to separate directory to avoid bind mount conflicts
• #1543 - fix: use ApiService for direct-neighbors endpoint instead of hardcoded URL
• #1542 - fix: PostgreSQL/MySQL schema bugs for upgrade_history and traceroute
• #1541 - Translations update from Hosted Weblate
• #1540 - feat: add Channel Database for server-side packet decryption
• #1536 - feat: enhance traceroute visualization with focused view and distinct path colors

Issues Resolved

• #1545 - Add py3-requests to Docker image
• #1539 - PostgreSQL upgrade_history column does not exist
• #1538 - Request Neighbor Info button not working
• #1537 - PostgreSQL auto_traceroute_log boolean type error
• #1518 - Scripts disappearing during upgrade with bind mounts
• #1495 - Channel Database feature request

Full Changelog: v3.0.3...v3.1.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.1.0

📦 Installation

Docker (recommended):

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