MeshMonitor v4.17.0-rc7

Summary

This release candidate fixes a map bug present in rc6: vector maps drew without roads, water or labels on pages that only use the 2D map. It also stops the whole app going blank in a browser with no WebGL; a standard map is shown instead. Navigation is now the same on every source type: Device Configuration (satellite icon) for settings that live on the device, and Settings (gear) for MeshMonitor's own behaviour, with each control moved to the page its name promises. Auto-Acknowledge now waits 5 to 30 seconds before answering a channel message and stays quiet when enough other nodes have already answered. New this round: a read-only estimate of what tighter Traffic Management settings would drop, a card that explains hardware MeshMonitor cannot flash, Analyzer Observer presets for meshcore.ca and RF Lab, and a "Sent to radio" mark on MeshCore channel sends. Three MeshCore permission gaps are closed.

Features

• Auto-Acknowledge: wait 5-30 s and stay quiet when enough nodes have already answered (#5695)
• Traffic Management: read-only replay for position dedup and rate limit, and corrected docs (#5681)
• Firmware: explain hardware that cannot be updated, in place of the update UI (#5680)
• Automations: trigger.ageMinutes on MeshCore node triggers (#5679)
• MeshCore: meshcore.ca and RF Lab presets for the Analyzer Observer (#5678)

Bug Fixes

• Map: 2D vector maps load their worker again, and a browser with no WebGL2 gets a raster map instead of a blank app (#5688)
• Settings: each per-source control is on the page its name promises (#5694)
• Nav: one icon and one label for Device Configuration and Settings on every source type (#5684)
• MeshCore: unrelayed channel sends are marked "Sent to radio" (#5693)
• MeshCore: per-section /snapshot grants, anonymous neighbour reads, and tabs that follow their grant (#5674)

CI and Translations

• CI: bound the ClamAV install step and add job timeouts (#5673)
• Translations update from Hosted Weblate (#5475)

Issues Resolved

#5666, #5667, #5668, #5671, #5672, #5675, #5677, #5683

Upgrade Notes

• No new migrations.
• Auto-Acknowledge now waits. An acknowledgement to a channel message arrives 5 to 30 seconds after the message (about 17 on average), not at once. If two other nodes have already replied or sent a tapback by then, MeshMonitor sends nothing. Change the count under Automation → Auto Acknowledge → "Maximum number of responses" (0 = no limit). Direct messages are answered as before. A Pre-Send Delay longer than 5 seconds adds to the wait. MeshCore auto-acknowledge is unchanged.
• Where things moved:
  • Meshtastic: Firmware update is now under Device Configuration; PKI DM decryption is under Settings.
  • MeshCore: default path hash size, default region/scope, the radio contact list, and Refresh contacts / Advert / Discover are under Device Configuration.
  • MQTT bridge: the bridge setup is the first section of that source's Settings; its separate nav entry is gone and old links redirect.
  • Reticulum: the destination retention cap is under Global Settings.
  • A pointer sits where each control used to be.
• Labels: the per-source entry that read "Device" (Meshtastic) or "Configuration" (MeshCore, Reticulum) now reads "Device Configuration"; the dashboard gear reads "Global Settings". Other languages show the English label until translated.
• Maps: a browser without WebGL2 shows a standard (raster) map and a note; the saved tileset is not changed.
• Firmware Updates pane: nodes MeshMonitor cannot flash over Wi-Fi (meshtasticd, nRF52, RP2040 and STM32 boards, and models with no mapped build) now show an explanation in place of the update controls. The server answers such a request with a 400 and a code, not a 500.
• Config saves: unchanged from rc6.
• MeshCore permissions: /snapshot returns contacts and nodes only with nodes:read; position history needs nodes:viewOnMap; the Channels, Rooms, Node Details, Telemetry and Settings tabs are hidden without their grant. An anonymous account that holds nodes:read can now read neighbour lines.
• MeshCore "Sent to radio": shown on your own channel message when the radio accepted it and no repeater has been heard relaying it. MeshCore radios do not report transmissions, so it does not mean the message was heard.
• Traffic Management: the docs no longer say the node broadcasts TrafficManagementStats; no current firmware sends it, so those graphs stay empty. The new Estimate panel reads MeshMonitor's packet log only and needs packet logging on.

Thanks

Thanks to @n30nex for confirming the meshcore.ca observer details.

Full changelog: v4.17.0-rc6...v4.17.0-rc7