What's Changed
Features
- Unified SaveBar Component - Replaced individual Save buttons across 30+ settings components with a unified SaveBar that appears as a fixed bar at the bottom when changes are detected. Includes smooth slide-in animation, Save/Dismiss buttons, and support for multiple sections with unsaved changes. (#1628)
- Remote Telemetry Configuration - Added Telemetry Configuration section to Remote Admin's Module Configuration area, allowing remote configuration of Device, Environment, Air Quality, and Power telemetry settings. (#1612)
- Transport Mechanism Tracking - Enhanced packet logging to track full transport mechanism (Radio, MQTT Uplink, MQTT Downlink) instead of just via_mqtt boolean. (#1622, #1623)
Bug Fixes
- Virtual Node Message History - Removed 10-message history replay on client connect to fix duplicate messages and incorrect hop counts on iOS clients. (#1610, #1621)
- Message Action Icons - Moved message action icons above the bubble to prevent overlap with hop count links. (#1616)
- PostgreSQL/MySQL Packet Clear - Fixed async support for clearing packet logs on PostgreSQL and MySQL databases. (#1620)
- Docker Healthchecks - Added curl to Docker container for proper healthcheck support. (#1614)
- Dashboard Favorites - Fixed rendering of Smart Hops and Link Quality on favorites dashboard. (#1607)
Translations
- Updated translations from Hosted Weblate (#1611)
Maintenance
- Version bump to 3.2.5 with Virtual Node CLI test fixes (#1618)
Issues Closed
- #1619 - 'TransportMechanism' field is missing from packet_log table
- #1617 - Failed to clear packet logs
- #1615 - Quick action icons overlap with the hop count link
- #1608 - Channel messages error on virtual node
- #1589 - Remote Admin Telemetry Missing
- #1557 - Auto Responder scripts save successfully but disappear afterward
Pull Requests
- #1628 - feat(ui): add unified SaveBar component for settings changes
- #1623 - refactor(packets): replace via_mqtt with full transport_mechanism enum
- #1622 - feat(packets): add via_mqtt column to packet_log table
- #1621 - fix(virtual-node): remove 10-message history replay on client connect
- #1620 - fix(api): add async support for clearing packet logs on PostgreSQL/MySQL
- #1618 - chore: bump version to 3.2.5 and fix Virtual Node CLI test
- #1616 - fix(ui): move message actions above bubble to prevent hop count overlap
- #1614 - fix(docker): add curl for container healthchecks
- #1612 - feat(admin): add telemetry configuration to remote admin
- #1611 - Translations update from Hosted Weblate
- #1610 - fix(virtual-node): improve message history replay for iOS clients
- #1607 - fix(dashboard): render Smart Hops and Link Quality favorites correctly
Full Changelog: v3.2.4...v3.2.5
๐ MeshMonitor v3.2.5
๐ฆ Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:3.2.5๐ Upgrade Notes
- The SaveBar replaces individual Save buttons throughout the UI - changes are now saved from a unified bar at the bottom of the screen
- Virtual Node no longer sends message history on client connect (fixes iOS duplicate message issues)
- Packet logs now track transport mechanism with more granularity (Radio/MQTT Uplink/MQTT Downlink)
Proxmox LXC Template
This release includes a Proxmox-compatible LXC container template for MeshMonitor.
Installation
- Download the
.tar.gztemplate file - Verify the SHA256 checksum (optional but recommended)
- Upload to your Proxmox server:
scp meshmonitor-*.tar.gz root@proxmox:/var/lib/vz/template/cache/ - Create a new LXC container from the template via Proxmox web UI
- Configure
/etc/meshmonitor/meshmonitor.envwith your Meshtastic node IP - 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.5
๐ฆ Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:3.2.5๐งช 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.