MeshMonitor v4.15.2-rc8

⚠️ Pre-release — this is a release candidate for testing. Docker images are not tagged :latest.

This candidate reworks the Mesh Issues Router Cluster rule after real-world feedback: clusters are now mutually-audible cliques instead of transitive connected components, groups glued only by shared-gateway co-reception downgrade to info, and a new tunable distance guard (default 30 km) filters MQTT-bridged traceroute "hops" that never happened over RF — on a live Florida mesh this cut phantom clusters from 345 km spans to coherent metro pods. The B2 Redundant Router rule gains the same range gate, so routers 40–120 km apart are no longer called redundant coverage of each other. Router Cluster cards also gain a Show map toggle that plots the members with the best-sited node highlighted. Purging telemetry from a node's charts works again for every source type — the request was missing its sourceId and always failed. The Mesh Issues report also picks up the A5 telemetry-cadence clause, wire-level pagination, and a tunable auto-close setting.

Bug Fixes

#4977 — Mesh Issues: Router clusters are mutually-audible cliques with a distance guard; co-reception-only groups downgrade to info; B2 covered-by pairs range-gated (#4976)
#4973 — Telemetry purge sends sourceId, fixing "Failed to purge telemetry data" for MeshCore and all sources (#4963)

Features

#4975 — Mesh Issues: map on Router Cluster findings with member markers and best-sited highlight (#4974)
#4972 — Mesh Issues post-epic follow-ups: A5 telemetry-cadence clause, wire-level pagination, auto-close setting (#4964)

Chores

#4980 — version bump to 4.15.2-rc8

Issues Resolved

#4976 — B1 Router cluster merges far-apart routers via transitive chains
#4974 — Mesh Issues: show a map on Router Cluster findings
#4963 — Purge Telemetry fails for MeshCore sources
#4964 — Mesh Issues epic (post-epic follow-ups)

Full changelog: v4.15.2-rc7...v4.15.2-rc8