Yeraze/meshmonitor v3.0.0-beta6

v3.0.0-beta6 - PostgreSQL/MySQL Improvements

on GitHub

What's Changed

Bug Fixes

• fix: Resolve PostgreSQL async query issues for packet monitor - Fixed node names not displaying, Hide Own Packets filter, and parameterized query issues
• fix: Add async database mocks to v1-api tests
• fix: Align MySQL migration schema with app schema
• fix: Add automatic PostgreSQL sequence reset after migration
• fix: Improve migration script schema handling and column mapping
• fix: Complete PostgreSQL/MySQL sync method compatibility
• fix: Resolve PostgreSQL sync method errors for poll routes
• fix: Convert auth routes to async for PostgreSQL support

Features

• feat: Add database info to system status - System Status modal now shows database type (SQLite/PostgreSQL/MySQL) and version
• feat: Add MySQL schema and improve migration tool
• feat: Add database migration CLI to Docker and migration guide

UI Improvements

• Show "Pending" instead of "Failed" for traceroutes less than 1 minute old
• Widen Slot column in Packet Monitor to show full encrypted channel IDs

Changes since v3.0.0-beta5

• PostgreSQL packet monitor now correctly displays node names
• "Hide Own Packets" filter now works with PostgreSQL (BIGINT type conversion)
• Database type and version shown in System Status modal
• Traceroute pending state for recent requests
• Packet Monitor Slot column widened for encrypted packets

Full Changelog: v3.0.0-beta5...v3.0.0-beta6

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)