MeshMonitor v4.13.1 builds on the "one map core" foundation from 4.13 with a set of link-quality tools for the RF-minded, and an early preview of several Meshtastic 2.8 features so you can start seeing them the moment you flash a 2.8 build. There's also a firmware-quirk fix worth calling out for anyone requesting telemetry from neighbour-info nodes.

Link Quality: see how your links are really doing

If you care about why a node is hard to reach — not just that it is — this release is for you.

• Terrain Link Profile. On Map Analysis, pick two nodes and get a full terrain cross-section between them: the ground profile from real elevation data, the Fresnel zone, and a link budget verdict (clear / marginal / obstructed) colored right on the graph. It auto-picks the frequency for your region, handles elevation-data voids gracefully, and the graph cursor mirrors onto the map so you can see exactly where along the path that ridge is. This is the tool for answering "would a repeater on that hill actually help?"
• Signal-trend / link-attenuation badge. Each node now carries a derived badge summarizing whether its link is holding steady, improving, or degrading over time — an at-a-glance read on link health without digging into graphs.
• Noise Floor is now on the Node Detail quick-stats card, alongside SNR and RSSI, so you can tell a weak-signal problem from a noisy-environment problem.
• Position accuracy & source in popups. Node popups (map and chat) now show how precise a position is and where it came from — GPS, a fixed position, or an estimate — so you know how much to trust that dot.

Map Analysis: the toolbar grew up

• The Map Analysis toolbar is now icon-based, with labels moved to tooltips — more map, less chrome.
• New Show RF / UDP / MQTT transport toggles let you filter the map by how packets actually arrived.
• Obscured-node handling got smarter: overlapping markers are offset only when they genuinely share a map cell, scaled by how crowded that cell is, so lone nodes stay put and dense clusters fan out cleanly.
• A "Discard invalid positions" map setting (honored on both ingest and render), plus a pile of fixes: spiderfy no longer opens the wrong node's popup, SNR overlay dots pin to the merged marker for multi-source nodes, and route/heatmap density no longer renders for marker-less or deleted nodes.

Meshtastic 2.8 — Early Preview

⚠️ This is an early preview. Meshtastic 2.8 has not been officially released — there's no 2.8 tag yet, so MeshMonitor builds this support against the firmware's development branch. Expect these features to change as 2.8 evolves, and treat anything here as subject to revision until the firmware ships stable.

With that caveat firmly in place, 4.13.1 gets a head start on 2.8 so the data shows up automatically when you run a preview build:

• XEdDSA signature shield. 2.8 can cryptographically sign packets. The Packet Monitor now decodes MeshPacket.xeddsa_signed and shows a 🛡️ shield next to signed packets, with the signing status persisted per packet (tri-state: unknown / unsigned / device-verified). The first signed packet from a 2.8 node will light it up.
• MeshBeacon decoding. The new MESH_BEACON_APP beacons are decoded and surfaced in the Packet Monitor — beacon text plus the channel/preset it's advertising.
• MEDIUM_TURBO preset. The new modem preset is in the preset tables, with firmware-verified channel-name derivation (which also fixed a long-standing naming bug in the older presets along the way).

A firmware heads-up while you're here: 2.8 makes position and telemetry broadcast opt-in, and a freshly flashed node defaults position precision to off. If a node goes quiet on the map or stops reporting telemetry after upgrading, that's expected 2.8 behavior — not a MeshMonitor bug. The FAQ has the details.

Also in this release

• Telemetry that survives a firmware quirk. Some 2.x nodes with neighbour-info enabled hijack the reply to a telemetry request and send NeighborInfo instead (an upstream firmware behavior — firmware#11071). MeshMonitor now detects this and automatically retries the telemetry request, so you get the metrics you asked for instead of silence.
• Privacy toggle: a new setting serves X-Robots-Tag: noindex headers and a disallow-all robots.txt, so a publicly-exposed dashboard can ask search engines and crawlers to stay out.
• TRUST_PROXY and boolean env vars are now parsed case-insensitively — True, TRUE, and true all work.
• Chat timestamps from unsynced-clock nodes no longer render back in 1970.
• Plus MQTT, message, and MeshCore fixes, dependency updates, and the usual round of polish. The full changelog has every entry.

As always, a lot of the best fixes here started as detailed bug reports — thank you. Flash a 2.8 preview build and let us know what the shield and beacons look like in the wild.