MeshMonitor v4.17.3-rc1

⚠️ Pre-release (Release Candidate 1). For testing ahead of the 4.17.3 official release. Docker images are tagged 4.17.3-rc1 only — :latest is unchanged.

First release candidate for 4.17.3. It is a MeshCore-heavy cycle: virtual channels now decrypt on Companion sources and show on the Channels page, DM and Room history survives busy-channel traffic, a per-source Required Repeater gate controls when the resend button clears, and a new MeshWars forwarder reports heard-repeater results to the territory game. Meshtastic/config picks up a drop-a-pin fixed-position picker, and a round of Virtual Node, MQTT-bridge and config reliability fixes land on top. Ten PRs since v4.17.2.

Features

• MeshCore: decrypt Companion OTA GRP_TXT frames against virtual channel keys and show those channels (receive-only, (Virtual) tag) on the Companion's Channels page (#6183)
• MeshCore: per-source Required Repeater gate — the resend button stays until that repeater is heard relaying the message, not just any repeater (#6184)
• MeshCore: forward heard-repeater results to MeshWars — off by default, admin-only, one capped HTTPS POST, nothing on the radio (#6005)
• Config: set a node's fixed position by dropping a pin on a map (Meshtastic + MeshCore) (#6174)

Bug Fixes

• MeshCore: page DM and Room history per peer so it survives channel traffic — no more "No messages yet" / collapsed room counts once 100 newer messages arrive (#6187)
• MeshCore: don't prefix non-hashtag channel names with a decorative # (#6182)
• Virtual Node: don't relay our own want_config_id config burst to VN clients, so the hourly node-DB refresh no longer makes the Android app lose its channel names (#6180)
• Virtual Node: ack-and-drop the blocked add_contact so app DMs no longer stall ~30 s (#6179)
• MQTT bridge: uplink a node's own map report instead of dropping it on the ok_to_mqtt gate — map reports carry no ok_to_mqtt bit, Map Reporting is their opt-in (#6176)
• Config: Reload Config re-reads MQTT Map Reporting and Report Location (proto3-elided false handled) (#6177)

Contributors

Thanks to @maxhayim for the MeshWars forwarder, the fixed-position map pin, and the MQTT-bridge / Reload-Config fixes this cycle.

Full changelog: v4.17.2...v4.17.3-rc1

🚀 MeshMonitor v4.17.3-rc1

📦 Installation

Docker (recommended):

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

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