MeshMonitor v3.12.0 brings new telemetry visualization modes, channel management improvements, API enhancements, and several bug fixes.

New Features

• Gauge and numeric telemetry display modes — Telemetry dashboard widgets now support gauge and numeric display modes in addition to the existing chart view, giving you more flexibility in how you monitor your mesh's sensor data (#2537)
• Delete Channel button — Channels can now be deleted directly from the channel configuration UI (#2531)
• Channel message cleanup on delete — When a channel is deleted, all associated messages and database records are automatically purged (#2533)
• /api/v1/status endpoint — New status API endpoint for health checks and monitoring integrations (#2527)
• WebSocket Bearer token auth — WebSocket connections now support Bearer token authentication in addition to session cookies (#2527)
• MeshCore auto-connect on startup — MeshCore connections now automatically reconnect when MeshMonitor starts, eliminating the need to manually reconnect after a restart (#2543)

Bug Fixes

• Packet monitor encryption status — Fixed incorrect encryption status display by using the decryptedBy flag for the isEncrypted check (#2541)
• Mark-as-read on PostgreSQL — Fixed a PostgreSQL compatibility bug where marking messages as read would fail (#2535)
• MeshCore map marker labels — Zoom-based label visibility now correctly applies to MeshCore node markers on the map (#2529)
• Map preferences database compatibility — Map preferences storage migrated from raw SQL to Drizzle ORM for improved multi-database compatibility (#2526)