MeshMonitor v4.17.0-rc9

Summary

This release candidate adds an All Channels view to Unified Messages, records every MeshCore TRACE the radio hears with per-hop SNR history, and lets an automation trace MeshCore paths on a schedule. Avoid PKI mode sends telemetry and neighbor requests channel-encrypted instead of PKI-encrypted. Aircraft handling gains manual marks and an opt-in position request. Map Analysis can add on-air waypoints, MQTT hop-raise has finer controls, and several sources hearing one packet now raise one notification. Two migrations run on first start (200, 201).

Features

• Unified Messages: All Channels view with a channel tag on each message; no DMs, pages back through full history (#5736, builds on #5654)
• MeshCore: capture every TRACE the radio hears and keep per-hop SNR history, with a card showing each link's trend (#5733)
• Automations: trace MeshCore paths on a schedule, each path on its own interval (#5735)
• PKI: Avoid PKI mode: telemetry, LocalStats and neighbor requests go channel-encrypted; DMs are untouched (#5724)
• Aircraft: mark a node as aircraft or not aircraft by hand (#5725)
• Aircraft: ask a newly flagged aircraft for its position, opt-in (#5727)
• Map Analysis: add on-air waypoints, with a per-source picker (#5732)
• MQTT: per-bridge skip raise, text messages in the raise picker, subscription-scoped handling (#5726)
• Notifications: one notification when several sources hear the same packet (#5731)

Bug Fixes

• MeshCore: own DMs and room posts show their real delivery state (#5730)
• Notifications: turning Emoji Reactions off also mutes protocol tapbacks and keycap emoji (#5721)

Upgrade Notes

• Migrations 200 and 201 run on first start: a manual aircraft mark on nodes, and the meshcore_hop_snr table.
• Scheduled traces transmit. Limits: at least 10 minutes between traces of one path, at most 12 traces per source per hour, at most 20 paths per action. The last-run times are stored, so a restart or a save does not fire a burst.
• Aircraft position requests are off. When on, a newly flagged aircraft gets 3 requests over 4 minutes, and at most 2 such sequences start per source per hour.
• Avoid PKI is off and has had no live radio check yet. Test it on a spare node before you rely on it.
• Trace history is kept for 90 days and read with the source's Traceroute read permission.
• Manual aircraft marks need Nodes write on the source.
• All Channels follows the same permissions as a single channel: Messages read on a source opens all of its channels; otherwise each channel needs its own read grant.

Thanks

Thanks to @Cryptoteep for the All Channels view (#5654).

Full changelog: v4.17.0-rc8...v4.17.0-rc9

🚀 MeshMonitor v4.17.0-rc9

📦 Installation

Docker (recommended):

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

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