Yeraze/meshmonitor v3.5.0

MeshMonitor v3.5.0 - Experimental MeshCore Support

on GitHub

What's New

MeshMonitor v3.5.0 is a milestone release introducing experimental MeshCore protocol support, along with AutoTraceroute scheduling improvements, Remote Admin UI enhancements, and several bug fixes.

Experimental MeshCore Protocol Support

MeshMonitor can now connect to MeshCore repeaters and clients via serial port, enabling monitoring and messaging with MeshCore-based mesh networks alongside standard Meshtastic nodes.

• Serial port connectivity to MeshCore repeaters and clients
• Node discovery and tracking for MeshCore devices on the map
• Two-way messaging between MeshMonitor and MeshCore nodes
• Contact management with automatic discovery

MeshCore support is experimental and requires a compatible MeshCore device connected via serial port. For more information, visit meshcore.co.

(#1777, #1880)

Features

• AutoTraceroute & Remote Admin time window scheduling — Restrict scans to specific hours (e.g., off-peak 22:00–06:00) with overnight wrapping support (#1871, #1872)
• Remote Admin icon and filter on map node list — Quickly identify and filter nodes with remote admin access (#1868)
• Show successful nodes first in Remote Admin Scanner log — Improved scan log readability (#1870)
• Expand system tokens in Auto Responder HTTP URLs — Use tokens like {NODE_ID}, {SNR}, etc. in HTTP action URLs (#1867, #1865)
• LLM Bridge user script — New community script for connecting LLMs to your mesh (#1878, #1876)
• Highlight selected node during traceroute — Pulsing glow on the selected node on the map (#1847)
• Compact packet charts on Info tab — Combined charts into compact sections (#1846, #1833)
• Gist support for User Scripts Gallery — Plus Earthquake Alerts script (#1845, #1804)
• Combined BLE & WiFi paxcounter graph — Dual-line graph (#1843)
• Compact node list cards and tighter popups (#1842, #1834)
• Document relayNode in V1 API and serve OpenAPI spec publicly (#1855)
• Local node hint banner on Remote Admin page (#1854)

Bug Fixes

• Tapback DM routing fix — Tapback emoji reactions now correctly stay on the original channel instead of being sent as DMs (#1885)
• Outgoing message timestamp fix — Timestamps update to node time on ACK receipt (#1884, #1877)
• Default auto-traceroute interval changed from 3 to 15 minutes (#1883, #1875)
• Persist Auto Acknowledge pattern testing text (#1881, #1879)
• Remove duplicate emoji from Sky and Sea Alert script name (#1882)
• AutoTraceroute schedule settings race condition (#1872)
• MFA verification broken on SQLite — Missing columns in SELECT queries (#1831, #1828)
• Double-issuer in MFA otpauth URI (#1831)
• Snapshot node positions at traceroute time — Fix moving node rendering on traceroute maps (#1864, #1862)
• Broadcast outgoing text messages to virtual node clients (#1863, #1859)
• Always verify auto_traceroute_nodes enabled column on startup (#1861, #1860)
• Improve map node popup grid layout for consistent positioning (#1851, #1841)
• Include network and telemetry configs in Load All button (#1854, #1852)
• Always show local node in Auto Time Sync node list (#1848)

Documentation

• Add MeshCore feature documentation (#1880)
• Add Auto Time Sync section to automation documentation (#1874)
• Update API docs and schema for traceroute position snapshots (#1866)

Translations

• Russian translation updates via Weblate (#1856, #1869)

Full Changelog: v3.4.9...v3.5.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)

Installation

Docker (recommended):

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

Helm:

helm repo add meshmonitor https://yeraze.github.io/meshmonitor
helm install meshmonitor meshmonitor/meshmonitor --version 3.5.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.5.0

📦 Installation

Docker (recommended):

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