Skip to content

Yeraze/meshmonitor

v3.2.4 Feature

This release adds 3 notable features 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 sidebar pin button to prevent auto‑collapsing and persist its state across sessions.

Full changelog

What's Changed

Features

  • Sidebar Pin Button - Added a pin button to the sidebar that prevents it from auto-collapsing when clicking navigation items. Pin state persists across sessions. (#1604)
  • Virtual Node Message History - Virtual node now sends the last 10 messages to connecting mobile apps, so you can see recent chat history immediately. (#1603)
  • Desktop Virtual Node Config - Windows/macOS desktop app now supports enable_virtual_node and virtual_node_allow_admin config options in config.json. (#1605)
  • Purge Neighbors Button - Added button to clear stale neighbor info from the Messages page. (#1595)

Bug Fixes

  • Update Banner Auto-Dismiss - Fixed the upgrade notification banner not auto-dismissing after 5 seconds due to a React callback reference issue. (#1604)
  • Security Config Save Disabled - Temporarily disabled the security config save button in Remote Admin to prevent key loss. (#1602)

Documentation

  • BLE Bridge Windows Docs - Added documentation for Windows native EXE Bluetooth pairing. (#1594)

Translations

  • Updated translations from Hosted Weblate (#1596)

Issues Closed

  • #1600 - Virtual node does not return a list of messages to client
  • #1599 - Update banner obscures interface elements
  • #1598 - Sidebar collapses upon clicking an item
  • #1597 - How to enable virtual node on Windows desktop client
  • #1601 - Direct node sends all packets but not appear on map/list
  • #1591 - Stuck neighbor info from days ago

Pull Requests

  • #1605 - feat(desktop): add virtual node config options to Tauri app
  • #1604 - feat(ui): add sidebar pin button and verify upgrade banner auto-dismiss
  • #1603 - fix(virtual-node): send message history to connecting clients
  • #1602 - fix(admin): disable security config save button
  • #1596 - Translations update from Hosted Weblate
  • #1595 - feat(ui): add purge neighbors button to Messages page
  • #1594 - docs(ble-bridge): add Windows native EXE documentation

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.2.3...v3.2.4


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

📦 Installation

Docker (recommended):

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

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