Highlights

• MeshCore repeater admin: paginated Neighbors with Load more, clearer disconnect toasts, and safer CLI quick commands.
• Reticulum RNode: Wi‑Fi TCP keepalive so idle links stop dropping around ~6s, plus clearer macOS BLE pairing (in-panel PIN, 60s passkey window, less reconnect thrash).

What's Changed

Features

• MeshCore repeater admin — Paginated Neighbors with Load more (Repeaters panel + node detail), disconnect toasts for Status/Telemetry/Neighbors, and safer CLI quick pills (clock, clock sync, clear stats, advert, board) (#697)

Bug Fixes

• Reticulum RNode TCP keepalive — Overlay rsReticulum activity keepalive so Wi‑Fi RNodes do not idle-FIN around ~6s (#698)
• macOS BLE RNode pairing UX — Surface Admin Start pairing PIN in-panel (never Meshtastic 123456), extend connect grace/hints to ~60s for the OS passkey window, latch blePairingTimedOut into Connection + Diagnostics, and debounce pairing-transition reconnect thrash (#698)
• Meshtastic node delete — Wire Node Detail Confirm delete to the Meshtastic runtime so the button actually removes the node (#695)
• Meshtastic disconnect teardown — Abort inbound fromDevice pipe before awaiting toDevice.close, tolerate abrupt writable close errors, and reduce reconnect flakiness after serial/BLE disconnect (#693)

Other Changes

• Faster pre-commit — Staged-related Vitest (test:staged), staged ESLint with cache, and path-gated check:* scanners; PR CI and pnpm run release still run the full suite (#696)
• Patches / deps — Track upstream patch PRs in patches/README.md and Ratspeak overlay registry; sync usb MSVC C++17 build flags; routine dependency bumps (#693, #694)

Breaking Changes

(None)

Full Changelog

v5.24.0...v5.24.1

Building on 4.13's unified map core, this release adds a suite of Link Quality tools for the RF-minded, an early preview of several Meshtastic 2.8 features, and a broad round of map, MQTT, and messaging fixes.

Highlights: a Terrain Link Profile tool (elevation cross-section, Fresnel zone, and link-budget verdict) on Map Analysis; a per-node signal-trend / link-attenuation badge; Noise Floor on the Node Detail card; and position accuracy + location source surfaced in node popups. The Map Analysis toolbar is now icon-based with Show RF / UDP / MQTT transport toggles, and obscured markers offset intelligently by cell occupancy. On the 2.8 front (an early preview — 2.8 is not officially released yet, so this is built against the firmware development branch and is subject to change), MeshMonitor now decodes the XEdDSA signing shield, MeshBeacon packets, and the MEDIUM_TURBO preset. Also notable: telemetry requests now auto-recover from an upstream firmware NeighborInfo-hijack, a new noindex/robots.txt privacy toggle, and a gateway-aware MQTT Packet Monitor.

See the release blog post for the narrative walkthrough.

Link Quality & Terrain Link Profile

• Terrain Link Profile tool: elevation cross-section + Fresnel zone + link-budget verdict, auto-frequency by region, DEM-void handling, map-mirrored graph cursor (#4143, #4147, #4151, #4170, #4156)
• Derived signal-trend / link-attenuation badge per node (#4204)
• Noise Floor on the Node Detail quick-stats card (#4201)
• Position accuracy + location source in node popups, map & chat (#4188)
• Latitude/longitude/elevation shown as text in Node Info / Node Details (#4134)

Map Analysis

• Icon-based toolbar with labels in tooltips (#4171)
• Show RF / UDP / MQTT transport toggles (#4135)
• Occupancy-scaled, distance-capped obscured-node precision offset (#4164, #4168, #4181)
• "Discard invalid positions" setting, honored on ingest and render (#4158, #4182)
• Per-theme (light/dark) tileset preferences (#4118)
• Keep router short-name visible in Official pin style (#4184)
• Honor Default Map Center on Unified/Dashboard maps (#4128)
• Fixes: spiderfy opens the correct node (#4203), SNR overlay pins to merged marker (#4169), no route/heatmap render for marker-less or deleted nodes (#4167, #4175)

Meshtastic 2.8 — Early Preview

⚠️ Meshtastic 2.8 is not officially released. This support is built against the firmware development branch and is subject to change as 2.8 evolves.

• Pin 2.8-preview protobufs (develop@ba16bfc) with a 2.7 TrafficManagement compat shim (#4205)
• XEdDSA packet-signing shield in the Packet Monitor (#4209)
• MeshBeacon (MESH_BEACON_APP) decode + firmware-verified preset channel names (#4207)
• MEDIUM_TURBO modem preset + 2.8 opt-in FAQ (#4200)

MQTT

• Gateway-aware MQTT Packet Monitor — per-gateway reception capture + UI (#4127, #4138)
• Geo-ignore epic: fail-open geo filter, per-source ignore list, retroactive purge/sweep, observability (#4123, #4131, #4132, #4136)
• Route directed MQTT messages to the DM view, not their channel (#4161)
• Guard MQTT POSITION ingestion against Null Island fixes (#4150)

Messages, Nodes & Automation

• Auto-retry telemetry requests hijacked by the firmware NeighborInfo behavior (#4214)
• Stop unsynced-clock nodes rendering chat at ~1970 (#4208)
• MeshCore own-node messages show name, not public key (#4197)
• Short name shown alongside long name on message senders (#4196)
• "Message anyway" override for unmessageable nodes (#4187), and clearer hidden-composer messaging (#4140)
• Remote-admin (non-local) reboot target for the device-reboot automation (#4186)
• Compose draft scoped per-conversation (#4185)
• Reliably un-hide nodes from the map across sources (#4141)
• Traceroute no longer sends on a DISABLED channel slot (#4180)
• Reject precision-obscured Null Island fixes on ingest (#4149)

…

• feat(routes): add per-route max_path_length cap by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/321
• chore(deps): update actions/setup-python action to v7 by @renovate[bot] in https://github.com/ipnet-mesh/meshcore-hub/pull/320

Full Changelog: https://github.com/ipnet-mesh/meshcore-hub/compare/v0.16.1...v0.16.2

Test build. Turn on Get test builds (beta) on the device, use the Beta toggle on the web flasher, or grab a -merged.bin below. Stable stays on beta_46.

Fixed

• Crash that could reboot the device while typing in a chat (#98).
• Devices stuck on the boot screen after an update with a microSD card fitted. The boot-time copy of your data to the card could hang on a slow or damaged card; it is now guarded so the device always boots (#142, #148).
• MQTT bridge settings not saving. They were going to the wrong storage; now they stick across reboots (#128).
• Message times showing 1910 or other wrong dates. They now match the clock at the top of the screen (#100, #152).
• Dutch keyboard typing "ij" and "IJ" on the "1" and "!" keys (#144, #164).
• Message box letting you type past the real send limit and silently dropping the end of a long message (#119).
• Copy and paste cutting off long text (#120).
• Quick messages list not scrolling when there were more entries than fit on screen (#151).
• Room server names starting with an unusual character showing an empty box on the Join screen (#116).
• Tanmatsu: only about half the emojis were reachable in the picker (#141).
• Tanmatsu: the last settings item (About) being unreachable was already fixed in an earlier build, so it is sorted here too (#140).

Boards

T-Deck · Heltec V4 TFT · Heltec V4-R8 · ThinkNode M9 · RAK TAP v2 · T-LoRa Pager (LR1121 / SX1262) · Attaky Core · T-Display P4. Flash <board>-merged.bin at 0x0 for a full install, or <board>.bin for an app-only update.

Based on MeshCore v1.16.0 main@e8d3c53ba1ea863937081cd0caad759b832f3028

Correções

• CLIENTE: A página inicial do GPS agora fica oculta no carrossel quando nenhum GPS é detectado na porta série no arranque, em vez de aparecer sempre quando ENV_INCLUDE_GPS está ativado.
• REPETIDOR: Corrigido envio de anúncios por inundação (flood adverts): agora respeita o default_scope e o modo de hash de caminho (path_hash_mode nas preferências).
• REPETIDOR: Removida a redução probabilística de flood adverts.
• REPETIDOR: Corrigido um buffer overflow no acumulador de comandos série.

Melhorias

• CLI: Adicionada a leitura do motivo de arranque do ESP32 (get pwrmgt.bootreason).
• CLI: Reforçada a cópia segura de strings no tratamento de comandos.
• RÁDIO: Ajustado o atraso de retentativa CAD para intervalo entre 120 a 360 ms.

Observabilidade

• DISPATCHER: Adicionados logs de debug para conclusão de TX.
• ESTATÍSTICAS: Removidos parâmetros não usados na formatação de respostas.

Build e Configuração

• BUILD: Adicionada a variável DISABLE_DEBUG ao processo de build.
• BUILD: Reorganizadas as build flags no platformio.ini.

• fix(routes): clearing observers in the edit modal now persists by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/319

Full Changelog: https://github.com/ipnet-mesh/meshcore-hub/compare/v0.16.0...v0.16.1

• chore(deps): update anomalyco/opencode action to v1.17.18 by @renovate[bot] in https://github.com/ipnet-mesh/meshcore-hub/pull/303
• chore(deps): update dependency daisyui to v5.6.16 by @renovate[bot] in https://github.com/ipnet-mesh/meshcore-hub/pull/302
• Add GitHub funding link to FUNDING.yml by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/304
• chore(deps): update dependency daisyui to v5.6.18 by @renovate[bot] in https://github.com/ipnet-mesh/meshcore-hub/pull/305
• chore(deps): update tailwindcss monorepo to v4.3.3 by @renovate[bot] in https://github.com/ipnet-mesh/meshcore-hub/pull/309
• chore(deps): update anomalyco/opencode action to v1.18.3 by @renovate[bot] in https://github.com/ipnet-mesh/meshcore-hub/pull/307
• feat: Route Health Monitoring by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/308
• feat: HTTP Cache-Control, dashboard TTL bump, and route event-hash dedup by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/310
• fix: route_result not refreshing after route edit (plus cache invalidation infra) by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/311
• chore(deps): update fontsource monorepo to v5.3.0 by @renovate[bot] in https://github.com/ipnet-mesh/meshcore-hub/pull/312
• feat: dashboard route widgets + cache TTL consolidation by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/313
• feat: precompute route health + consolidated migration + observer badge fix by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/314
• UI polish: modal save spinners + route list sort by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/315
• chore(routes): default window_hours=48 and max_hop_span=8 by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/316
• chore(routes): default packet_count_threshold=5 and 3× clear multiplier by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/317
• feat(dashboard): limit Route Health widget to community routes by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/318

Full Changelog: https://github.com/ipnet-mesh/meshcore-hub/compare/v0.15.10...v0.16.0

Room server

If you're an admin on a room server, you can now manage it right from the room chat — tap the manage icon to reach status, telemetry, settings, neighbors, and the command line.

Replies that point at the right message

Replying in a channel now quotes the exact message you picked, instead of the person's most recent one. Mentioning someone with @ no longer accidentally turns your message into a reply, and quoted replies now appear correctly in other MeshCore apps too.

Smarter contact list

Nodes with a broken clock no longer show nonsense ages like "755 days ago". MeshTrax corrects the time and marks the contact with a small clock icon so you know why.

Notifications that go where you expect

Tapping a notification now opens the right conversation, even if the app was closed.

Bug fixes

Channel messages send more reliably over USB, message retries can be turned off, a reconnecting status now shows in chat, notifications no longer appear for unused channel slots, duplicate device info entries removed, and various fixes for improved compatibility with the latest device firmware.

Full Changelog: https://github.com/venamartin/meshtrax/compare/v1.6.3...v1.7.0

🧪 Test build. Flip Get test builds (beta) on-device, use the Beta toggle on the web flasher, or grab a -merged.bin below. Stable stays on beta_46.

🙏 Community contributions: thanks to @attakygit for the Attaky Core board port (#158) and @codemonkeybr (Tesso Codemonkey) for the T-LoRa Pager navigation fix (#162).

✨ Discover — find what's around you

• Active discovery — open the Discover app (app drawer → the ⟳ tile, next to Map): it sweeps for nearby nodes and lists every repeater / companion / room server that answers, ranked by signal — live RSSI/SNR, a green direct badge for anything in direct RF range, and a last-heard age.
• One-tap add — tap a node to add it straight to your contacts (it keeps the right type: repeater, companion or room).
• Wardriving — with a GPS fix it logs every node it hears against your position to a CSV on the SD card as you move, and paints your RF coverage on the map as a signal-coloured track (green = strong → red = weak). A standalone, on-device coverage mapper — no phone tethered.

📟 New boards

• Attaky Core (ESP32-S3, 16 MB flash / 8 MB PSRAM) — a new board (by @attakygit, #158). Experimental: beta channel only while hardware verification finishes.
• LilyGo T-Display P4 — TFT-LCD variant — early support for the LCD screen model (the AMOLED variant was already supported). Experimental; the wadamesh-tdisplay-p4-lcd-merged.bin asset below is for LCD-screen units (flash at 0x0).

🛠 Fixed

• LilyGo T-LoRa Pager — the rotary encoder now keeps its focus inside the chat message list, and the composer navigation keys are remapped so moving around and typing a message no longer collide (by @codemonkeybr, #162).

📦 Boards

T-Deck · Heltec V4 TFT · Heltec V4-R8 · ThinkNode M9 · RAK TAP v2 · T-LoRa Pager (LR1121 / SX1262) · Attaky Core · T-Display P4. Flash <board>-merged.bin at 0x0 (full install) or <board>.bin for an app-only/OTA update.

⚠️ Pre-release (release candidate). This build is for testing ahead of the v4.13.1 stable release. Not recommended for production deployments.

This fourth release candidate continues the Meshtastic 2.8 readiness work and lands a mix of node-detail and map improvements on top of rc3. It adds a noIndexEnabled privacy toggle so a publicly-exposed dashboard can serve X-Robots-Tag: noindex, nofollow headers plus a disallow-all /robots.txt (belt-and-suspenders for Cloudflare-tunnel setups that strip custom headers). On the 2.8 front, it decodes MESH_BEACON_APP with firmware-verified preset channel names, pins the 2.8-preview protobufs with a 2.7 TrafficManagement compat shim, adds an XEdDSA signature shield in the Packet Monitor, and ships the MEDIUM_TURBO preset with 2.8 opt-in docs. Node detail gains a derived signal-trend / link-attenuation badge and a Noise Floor quick-stat. Two bug fixes round it out: chat from unsynced-clock nodes no longer renders at ~1970, and cluster spiderfy no longer opens the popup for a nearby unrelated node.

Features

• Privacy: noIndexEnabled toggle serving X-Robots-Tag: noindex, nofollow + disallow-all /robots.txt (#4212, closes #4202)
• 2.8 / Packet Monitor: XEdDSA signature shield for firmware 2.8 packets (#4209)
• 2.8 / MeshBeacon: decode MESH_BEACON_APP + firmware-verified preset channel names (#4207)
• 2.8 / Protobufs: pin 2.8-preview develop@ba16bfc with 2.7 TrafficManagement compat shim (#4205)
• Nodes: derived signal-trend / link-attenuation badge per node (#4204, closes #4110)
• Nodes: show Noise Floor on the Node Detail quick-stats card (#4201, closes #4109)
• 2.8: MEDIUM_TURBO preset, MESH_BEACON_APP portnum, traffic-management & 2.8 opt-in docs (#4200)

Bug Fixes

• Messages: stop unsynced-RTC nodes rendering chat at ~1970 (rxTime now clamped to receipt time) (#4208, closes #4206)
• Map: spiderfy no longer selects a nearby unrelated node instead of fanning the cluster (#4203, closes #4199)

Issues Resolved

• #4202 — [FEAT] Robots.txt / X-Robots-Tag toggle to discourage crawlers/bots
• #4206 — [BUG] Chat from unsynced-clock nodes renders at ~1970
• #4199 — [BUG] Spiderfy click opens popup for wrong nearby node
• #4109 — [FEAT] Show Noise Floor on Node Detail quick-stats card
• #4110 — [FEAT] Derived signal-trend / link-attenuation indicator per node
• #4074 — Modem preset tables missing MEDIUM_TURBO (enum 16)
• #3999 — [2.8 tracking] Position & telemetry broadcast now opt-in by default
• #3547 — Docs: Traffic Management module documentation

Full changelog: https://github.com/Yeraze/meshmonitor/compare/v4.13.1-rc3...v4.13.1-rc4

🚀 MeshMonitor v4.13.1-rc4

📦 Installation

Docker (recommended):

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

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

Installation

sudo ./manage.sh install

Upgrade

sudo ./manage.sh upgrade

If anyone needs the TFT version let me know via the discussions page, otherwise I'll add it as soon as I can.

• New: Sensors screen. (Companion — all platforms)

  A new Sensors page on the Home screen. Battery shows a 24-hour rolling battery-percentage history as a bar chart, one bar per hour. If an environment sensor is attached, long press cycles through its readings — temperature, humidity, pressure, altitude, voltage, current, power, distance, or gas resistance — as a plain value+unit grid (°C, hPa, V...). The header shows the sensor's actual name (e.g. "BME280") while viewing its page, and precise Vbat voltage while viewing "Battery". With only one sensor attached, the page title just reads "SENSOR"; with more than one, pages are numbered by detection order ("Sensor 1", "Sensor 2"...) rather than the raw LPP channel number.

• Message Persist setting now available in the WiFi Companion Portal, and included in backup/restore. (Companion — WiFi transport, V3, V4, E213, E290, Wireless Paper, XIAO S3)

  The Message Persist toggle (added in v1.16_0714) was previously only reachable via CLI or the on-device UI. It's now also a checkbox under General Settings in the Companion Portal, and its value round-trips through the portal's Backup/Restore.

EastMesh observer-eastmesh firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware v1.16.0 plus upstream dev updates (as of 2026-07-09).

This release syncs with upstream MeshCore dev — bringing power-off/deep-sleep improvements, SX1262 LDO support, hardware channel-activity detection, and board/platform fixes — realigns saved settings storage with upstream so future syncs can't shift or corrupt EastMesh settings, and restores EastMesh/MeshMapper broker TLS trust after a server-side certificate change.

What's Changed

• Merged upstream MeshCore dev updates including power-off/deep-sleep improvements, SX1262 LDO support, hardware channel-activity detection, radio gain fixes, and board/platform fixes.
• Realigned saved node settings to upstream byte offsets and moved EastMesh-specific fields behind a reserved gap so future upstream syncs no longer shift or corrupt them.
• Restored EastMesh and MeshMapper broker TLS trust after mqtt2.eastmesh.au moved from Let's Encrypt to a Google Trust Services certificate.
• Bumped CI build and docs workflows to Python 3.13.

Breaking Changes

• The saved settings layout changed: devices upgrading from 2026.6.6 or earlier may need EastMesh-specific settings (such as fan control and bridge peer) and recently added radio settings reconfigured after the update.

Notes

• If your observer stopped uplinking to eastmesh-au or meshmapper with TLS certificate errors, this release is the fix — update and the connection will recover on its own.
• After updating, check your fan control, bridge peer, and recently added radio settings (see Breaking Changes) and re-set any that came back at defaults.
• eastmesh-au remains the recommended MQTT endpoint once mqtt.iata is configured; meshmapper and waev are available as global second brokers.
• Select brokers from the Primary and Secondary dropdowns in the web panel, or toggle them from the CLI (set mqtt.eastmesh-au on, set mqtt.meshmapper on, set mqtt.waev on, etc.). A maximum of two brokers can be enabled at once.
• waev (mqtt.waev.app) uses a 1-hour auth token that the firmware refreshes automatically, so no extra configuration is needed. Set your Waev account email with set mqtt.email <email> so Waev can link the observer to your account.
• MQTT status messages report cumulative packets_sent and packets_received alongside the existing radio stats; both counters reset on reboot.
• LetsMesh EU/US are retired but still selectable for legacy use.
• Custom MQTT is available for private broker deployments and uses username/password auth only. For TCP custom MQTT, use the broker host and port as before. For WSS custom MQTT, set the host and port, select WSS transport, and the firmware connects using wss://host:port/mqtt.
• WSS uses TLS encryption and validates against the ESP-IDF x509 root CA bundle.
• For maximum heap headroom on busy observers, use the web panel for setup and troubleshooting, then disable it with set web off.
• Browsers may still require accepting the self-signed certificate warning on first HTTPS access.
• flood.max.unscoped defaults to 64; lower it only if you want to limit how far unscoped flood traffic repeats.
• flood.max.advert controls the hop limit for flooded advert packets.

Documentation

xjarid.github.io/MeshCore-EastMesh

Flashing

• flasher.eastmesh.au
• flasher.meshcore.io

Assets

• .bin - standard update image
• -merged.bin - full ESP32 image for flashing after erase

Highlights

Reticulum grows into a full comms suite this release: a new Relay Chat (RRC) IRC-style multi-hub client, a Remote tab for rnsh shells and rncp file transfer, watch-folder Nomad hosting with an upgraded Micron renderer, identity slots, propagation-node rename/delete, and much faster Peers at large path-table sizes. A broad protocol-parity pass adds QR generation/scan, lxm:// deep links, GPX export, LoRa signal metering, Meshtastic module event history, and per-send MeshCore flood-scope presets (now behind a split Send button). Messaging is more resilient (one-click location share, chat outbox drain on reconnect, extended reconnect budgets, humanized send-NAK errors), and cold-start BLE is serialized so an RNode connects before the RF radios. MeshCore MQTT now steers non-Colorado users to LetsMesh by default.

What's Changed

Features

• Reticulum Remote tab (rnsh + rncp) — New Remote tab (Shell / Transfer / Saved / Settings) with an xterm shell, file send/fetch/listen, saved address book + inbound policy, and Chat DM rncp controls; trust-boundary hardening (picker-backed save dirs, size/offer caps, allow/block lists) (#692, implements #688, #689)
• Reticulum Relay Chat (RRC) — IRC-style multi-pane client with up to 8 concurrent hub sessions, Favourites/Discovered hub picker, rooms + nicklist, /-command router, @mention unread badges + tray/toast notifications, and SQLite-persisted room history with retention pruning (#680, fixes #648)
• Watch-folder Nomad hosting + Micron rendering — Host bounded static Nomad Network sites from a watched folder with auto-restore and filesystem watching; vendored RFnexus Micron parser adds table/anchor/partial support (#683, closes #613)
• Protocol parity tools — Meshtastic module event history, LoRa signal metering, GPX export, MeshCore MCU temperature parsing, per-send flood-scope overrides, QR generation + camera/file ingest, custom lxm:// deep links, cross-platform camera permissions, and Reticulum identity slots with restart-based switching + contact fingerprint verification (9890611e, fixes #218, #477)
• MeshCore flood-scope presets — User-managed scope list (seeded from the radio hashtag, cap 20) replacing Colorado/Denver hardcodes; scope now lives behind a chevron split-Send menu instead of an always-visible select (#692)
• Messaging resilience — One-click chat location share (OSM text + optional Meshtastic waypoint) with outbox enqueue on failure, chat outbox drain on RF reconnect, extended BLE/serial reconnect budgets (8 attempts) with transport-aware "reconnecting N/M" banner, conservative/aggressive Store & Forward catch-up setting, and a hung-only Reticulum sidecar health watchdog (#692)
• Reticulum propagation node management — Rename/delete remote propagation nodes with confirm dialog and persistence guards (#679)
• Scale Reticulum Peers — Incremental peers_updated patches, path-table TTL, forced ?refresh=1 dumps, batched Map updates, and retention parity (hard 100k ceiling / 50k user cap) keep the UI responsive at ~50k peers ([#677](https://github.com/Colorado-Mesh/mesh-client/pull/677 …

⚠️ Pre-release (release candidate). Rolls up 13 PRs merged since rc2 — position-quality & Map Analysis refinements plus a cluster of messaging correctness fixes. Please test and report issues before the stable 4.13.1.

Highlights

This RC sharpens position quality and node identity. Node popups now show position accuracy and GPS location source; the "Discard invalid positions" toggle is honored on the render side (not just ingest); and the obscured-node precision offset is occupancy-scaled and distance-capped. On the messaging side it fixes several real correctness bugs: compose drafts no longer leak across conversations (a message meant for one node could be sent to another), MeshCore own-node messages show the node's name instead of a raw public key, and message senders now display their short name alongside the long name. Rounding it out: automations can now target a remote node for admin reboot, unmessageable nodes get a "Message anyway" override, traceroute no longer fails with NO_CHANNEL on a disabled channel slot, and the v1 default source alias scopes correctly.

Features

• #4188 — Position accuracy + location source in node popups (chat & map), migration 124
• #4187 — "Message anyway" override for unmessageable-node DM banner
• #4186 — Automation: remote-admin reboot target for the device-reboot action
• #4196 — Show short name alongside long name on message senders (Unified Messages)
• #4182 — Honor the "Discard invalid positions" toggle on the render side
• #4181 — Occupancy-log-scaled, distance-capped precision offset for obscured nodes

Bug Fixes

• #4197 — MeshCore: own node's messages show the name, not a public key
• #4191 — v1 default source alias deep-scopes by the resolved id (mergeParams re-derivation)
• #4185 — Scope the compose draft per-conversation (prevents wrong-recipient sends)
• #4184 — Keep router short-name visible in the Official pin style
• #4180 — Traceroute no longer sends on a DISABLED channel slot (NO_CHANNEL)
• #4175 — Drop heatmap/coverage density for deleted nodes

Docs

• #4179 — Meshview Link Responder added to the User Scripts Gallery

Full changelog: https://github.com/Yeraze/meshmonitor/compare/v4.13.1-rc2...v4.13.1-rc3

🚀 MeshMonitor v4.13.1-rc3

📦 Installation

Docker (recommended):

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

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

Release candidate 7 for the beta-0.1.45 cycle. 181 commits since beta-0.1.44-RC6.

Flash with esptool

# Full flash (first install):
esptool.py --chip esp32s3 --port /dev/ttyACM0 write_flash 0x0 firmware-merged.bin

# App update (keep settings):
esptool.py --chip esp32s3 --port /dev/ttyACM0 write_flash 0x10000 firmware.bin

Web Flasher

Use manifest.json with esptool.js.

Features

• Companion protocol: binary peer requests (CMD_SEND_BINARY_REQ), anonymous requests (CMD_SEND_ANON_REQ), zero-hop control data (CMD_SEND_CONTROL_DATA), direct raw data (CMD_SEND_RAW_DATA)
• UI: message detail sheet, contact list power tools, bounded field notifications, timestamped repeater CLI transcripts
• GPS: demand-driven polling with time sync
• Mesh: surface repeater session failures
• CI: dependency scanning, CodeQL analysis gates, release evidence enforcement
• Performance: virtualized message/packet lists, bounded sparse tile loading
• Storage: unified message history store

Fixes

• Companion/BLE: install private flood-scope keys, synchronize BLE callback/app state, BLE RX queue backpressure, time out unauthenticated connections, defer BLE init until enabled, migrate stale prefs, update pairing PIN, preserve CLI data semantics, accept time unconditionally, enable BLE by default, page full companion backlog, gate repeat by radio profile, align async push IDs
• Mesh: clear login sessions on identity import, ACK drop counter, require durable mesh mutation commits, scoped flood interop proof, update MeshCore for race-free ISR, reject oversized hashtag names, preserve UTF-8 message boundaries
• UI: restore textarea date/time inputs, accumulate home grid offsets, bound textarea inputs, route nested screens through nav history, free QR canvas on screen delete, always show repeater login status
• System: clamp snprintf buffer (CodeQL), make deep sleep persistence-safe, OTA boot-health rollback, fail closed for GitHub OTA channels, support unknown-size multipart OTA, preflight/bound PNG tile decoding, handle HAL allocation failures
• Build/CI: add -Wall -Wextra, expand sanitizer suite, compile every firmware env, reject stale warning budgets, pin transitive deps, consolidate PlatformIO cache, regenerate dep lock file
• GPS: route RTC sync through tracked clock sources, preserve mesh clock handoff
• SD: de-assert non-SD CS pins before mount
• Various: encode advert path responses safely, validate NMEA semantics, complete message store recovery, expire pending binary requests, update companion delivery state, reject oversized companion pushes, wrap map tiles at antimeridian, propagate NVS write failures, decode trace SNR correctly, validate encoded path lengths

Documentation

• Reconcile companion support and missing-features status with pinned MeshCore
• Refresh README, screen guides, ROADMAP, FEATURES_OVERVIEW, Launcher docs
• Add Noto Emoji license notice
• Document companion message visibility limitation

Hardware Tested (beta-0.1.45-RC7)

• Native tests: 1219/1220 passed
• Production build: RAM 39.3%, Flash 40.0%
• T-Deck boot verified: radio 869.525 MHz, noise floor -94 dBm
• All 12 screens navigate without crashes
• Soak: 420 seconds idle, zero crashes, heap stable at 146,808
• RF transmission confirmed on #testingslopos
• CI pre-existing: dep hash + golden frame pin fixed; remaining 2 test infra issues pre-date this release

Evidence

Release evidence: release-evidence/beta-0.1.45-RC7.json

What's Changed

• Fix multibyte path hash handling in MishMesh by @Bjorkan in https://github.com/burakcan/MeshCore-mishmesh/pull/9

New Contributors

• @Bjorkan made their first contribution in https://github.com/burakcan/MeshCore-mishmesh/pull/9

Full Changelog: https://github.com/burakcan/MeshCore-mishmesh/compare/mishmesh-v1.0.0...mishmesh-v1.1.0

What's new

• Nodes is now the single node hub. "Nearby Nodes" is renamed Nodes and gains on-device contact management — no phone app needed: Hold Enter on a row opens Add contact (for a scanned-but-unknown node), Favourite/Unfavourite (pins to the first free Favourites Dial slot, shown as a star in the list), and Delete contact (confirm first, defaults to Cancel). The filter strip (LEFT/RIGHT) is now a visible, wraparound tab carousel instead of a hidden mode. The old read-only Recent adverts home page is retired — its passively-heard nodes now simply show up in the Nodes list (All filter) — so there's one list instead of two.
• On-device channel management. Messages › Channels gets a "+ Add channel" row and per-channel Edit/Delete — no phone app required. Adding a channel now starts with a type picker, matching the phone app: Public (re-adds the well-known default channel, no typing needed), Hashtag (type just a topic name, e.g. test — the channel name and secret are both derived from it, same convention as the app's #topic channels), or Private (manual Name + Secret, typing either a passphrase hashed to the channel secret, or the exact 32-hex-character key from a channel QR code).
• Tools › Admin — administer a remote repeater/room from the device. Log into a node you have admin rights on (same self-healing saved-password handshake as room logins) and browse its settings in category tabs — System (name, owner info), Radio (Frequency/Bandwidth/Spreading factor/Coding rate/TX power), Routing (Repeat/Advert interval/Flood advert interval/Max hops), Actions (reboot, send advert, sync clock, …) — plus a free-text Custom command… escape hatch (with {}-key command-name completion) for anything not covered. Radio and Routing fields use a type-appropriate editor instead of raw text — a digit-cursor for Frequency (the same widget Settings' own Radio screen uses locally), discrete-set stepping for Bandwidth/Spreading factor/Coding rate, plain number steppers for the rest, and an ON/OFF toggle for Repeat — adjusting a value costs no mesh traffic until you actually confirm it with Enter (Cancel sends nothing). Reachable either from Tools › Admin (opens the same Nodes list to pick a target) or directly via a repeater/room's own Hold Enter › Admin action.
• Auto-Reply Bot gains a third target: room servers, alongside DM and Channel, with its own trigger/reply/commands — the screen is redesigned as a circular tab carousel (Direct/Channel/Room/Other, LEFT/RIGHT to switch, UP/DOWN within a tab) instead of one long list. Each target's Enable and Commands toggle is now fully independent (they used to secretly share the DM tab's setting for Channel/Room too). New {name}/{hops} reply placeholders, a DM allow-list (all chat contacts or favourites only), and a dedicated stepper for Quiet Hours.
• Keyboard: accent popup, selectable main script, better editing. Holding Enter on a Latin letter with accented variants (a c d e i l n o r s t u y z) now opens a one-row popup of that letter's accents — e.g. holding a offers á à â ã ä å ą — covering every European Latin-diacritic letter (Polish, Czech, Slovak, German, French, Spanish, Portuguese, Nordic, …) from one popup instead of a separate page per language. Settings › Keyboard splits Alphabet into Main and Additional: Main picks which script (Latin/Cyrillic/Greek) the keyboard opens on by default, Additional picks the second one reached via the #@/abc cycle key — so a Cyrillic or Greek typist can make their own script the default instead of always landing on Latin first. Shift is now one-shot by default (capitalises just the next letter; Hold Enter on Shift toggles the old sticky caps-lock back on), Hold Enter on Backspace clears the whole field, and UP from th …

⚠️ Pre-release (release candidate). For testing ahead of the 4.13.1 final. No :latest Docker tags are published for RC builds.

This RC is a Map Analysis release: it lands the full Terrain Link Profile tool and a wave of map-accuracy improvements on top of v4.13.1-rc1. Plan a link between two points and MeshMonitor now profiles the terrain between them, draws the Fresnel zone, computes a link budget, and colors a clear/marginal/obstructed verdict — with per-source auto-frequency and RX-sensitivity defaults. As you scrub the elevation graph, a marker now tracks the matching spot on the map so you can see exactly where a given point on the profile sits. Obscured-GPS (reduced precision_bits) markers are now decluttered intelligently — a node alone in its accuracy cell stays centered, and only nodes that actually share a cell are spread — applied consistently across the Dashboard, Nodes, and Map Analysis maps from one shared implementation. Position quality also got a hard look: Null Island (0,0) fixes are now rejected on ingest across Meshtastic, MeshCore, and MQTT (including the precision-obscured (0,0) fixes that used to slip through as ~0.013°), with a new Discard invalid positions Map setting to control it. The Map Analysis toolbar was tidied into icons (labels move to tooltips) to cut clutter, MQTT-sourced direct messages now render in the DM view instead of as broadcasts, and several map layers stopped drawing artifacts for marker-less nodes. Internally, the CI pipeline's Node-24 coverage hang was eliminated so future builds are faster and don't wedge.

✨ Features

• Terrain Link Profile tool — profile terrain, Fresnel clearance, and link budget between two points, with clear/marginal/obstructed verdict coloring, per-source auto-frequency + RX-sensitivity defaults, DEM-void handling, and a settings UI (#4147, #4151)
• Link Profile graph → map hover marker — moving the cursor over the elevation graph drops a marker on the map at the corresponding geographic point along the link (#4170)
• Smarter obscured-node decluttering — the within-cell offset for low-precision_bits markers now only spreads nodes that actually share an accuracy cell; a lone node stays at its reported center (#4164, closes #4155)
• Discard invalid positions — a new global Map setting to control whether Null Island / invalid GPS fixes are discarded on ingest (default on = current behavior) (#4158)
• Icon toolbar for Map Analysis — action and layer buttons are now icons with the text as tooltip/aria-label, decluttering the top bar (#4171)

🐛 Bug Fixes

• Reject precision-obscured Null Island fixes on Meshtastic ingest — a true-(0,0) node on a reduced-precision channel arrives re-centered as ~(0.013°, 0.013°) and used to slip past the filter (#4149, #4150, #3763)
• Route MQTT-sourced direct messages to the DM view instead of rendering them as channel/broadcast messages (#4161, closes #4152)
• Stop drawing route segments & heatmap density for marker-less (position-stripped) nodes (#4167, closes #4162 / #4163)
• Pin the SNR overlay dots to the merged marker position for multi-source nodes (#4169, closes #4166)

♻️ Refactoring

• Consolidate the obscured-GPS within-cell offset into one shared occupancy-gated implementation used by every map surface — no more per-map "snowflake" behavior (#4168)

🔧 CI / DevOps

• Remove the unused coverage/Codecov runner that hung @vitest/coverage-v8 for 30+ min on Node 24, repeatedly blocking merges — CI is now faster and hang-free (#4172)

📝 Docs

• Link Profile documentation accuracy pass — multi-source auto-frequency, REST API reference, anchor fixes (#4156)

Issues Resolved

#4111 (Terrain Link Profile epic — Phases 2 & 3) · #3763 (Null Island filtering) · #4152 (MQTT directed-message rendering) · #4155 (lone-node offset) · #4162 · #4163 · #4166

Upgrade Notes

No breaking changes and no manual migration …

✅ Stable channel. Install via the web flasher (Stable), the LauncherHub WADAMESH entry, or a -merged.bin below. Newer test builds live on the Beta channel.

🙏 Community contribution: huge thanks to @codemonkeybr (Tesso Codemonkey) for the Do Not Disturb feature (originally #156).

🛠 Fixed

• Contacts no longer go missing between reboots on microSD devices. Saves are now atomic — written to a temp file and swapped in only once fully written — so an interrupted write can never truncate your contact list, and the card is mounted far more reliably at boot. (If you've ever lost repeaters/contacts overnight, this is the fix — update to it.)
• Heltec V4-R8 — the microSD card now mounts, and the freeze when waking the device from sleep is fixed.
• LilyGo T-Pager — the map no longer shows a "storage error" under the launcher; it now caches tiles to the microSD card (like the T-Deck).
• Heltec V4 (portrait) — the Bluetooth icon no longer overlaps the clock, and control-center buttons no longer clip when tapped.

✨ New

• Redesigned control center — round quick-toggle buttons that spread to fill the panel, a frosted-glass look, real lock/bell glyphs, and a confirmation popup on every toggle.
• Do Not Disturb (by @codemonkeybr, #156) — set quiet hours in Settings → Sound to silence the incoming-message chime during a daily window, with a bell in the status bar while it's active. Plus a matching control-center quick-toggle (a bell that gains a slash while quiet hours are on).

📦 Boards

T-Deck · Heltec V4 TFT · Heltec V4-R8 · ThinkNode M9 · RAK TAP v2 · T-LoRa Pager (LR1121 / SX1262) · T-Display P4. Flash <board>-merged.bin at 0x0 (full install) or <board>.bin for an app-only/OTA update.

Based on MeshCore v1.16.0 main@e8d3c53ba1ea863937081cd0caad759b832f3028

Correções

• CLIENTE: A página inicial do GPS agora fica oculta no carrossel quando nenhum GPS é detectado na porta série no arranque, em vez de aparecer sempre quando ENV_INCLUDE_GPS está ativado.
• REPETIDOR: Corrigido envio de anúncios por inundação (flood adverts): agora respeita o default_scope e o modo de hash de caminho (path_hash_mode nas preferências).
• REPETIDOR: Removida a redução probabilística de flood adverts.
• REPETIDOR: Corrigido um buffer overflow no acumulador de comandos série.

Melhorias

• CLI: Adicionada a leitura do motivo de arranque do ESP32 (get pwrmgt.bootreason).
• CLI: Reforçada a cópia segura de strings no tratamento de comandos.
• RÁDIO: Ajustado o atraso de retentativa CAD para intervalo entre 120 a 360 ms.

Observabilidade

• DISPATCHER: Adicionados logs de debug para conclusão de TX.
• ESTATÍSTICAS: Removidos parâmetros não usados na formatação de respostas.

Build e Configuração

• BUILD: Adicionada a variável DISABLE_DEBUG ao processo de build.
• BUILD: Reorganizadas as build flags no platformio.ini.

⚠️ Pre-release / Release Candidate. This build is for testing. It ships no :latest Docker tags. Please report any issues before the final 4.13.1 release.

Summary

This release resolves the long-running #4115 investigation where specific nodes produced zero data over MQTT: the geo filter is rearchitected from a fail-closed membership gate (which permanently blackholed GPS-less nodes and froze on encrypted feeds) to a fail-open, per-source ignore-list model with retroactive purge, automatic reappearance when a node comes back in-bounds, and a start/config-change sweep — shipped across four phases (#4123, #4131, #4132, #4136). A new MQTT Packet Monitor lands (per-gateway reception capture backend #4127 plus a gateway-aware UI #4138). Map and node UX improvements include lat/lon/elevation shown as text in Node Info/Details (#4134), Show RF/UDP/MQTT transport toggles in Map Analysis (#4135), per-theme light/dark map tilesets (#4118), and a backend elevation service for upcoming terrain link profiles (#4143). Two reported bugs are fixed: nodes can now be reliably un-hidden from the map across sources (#4141), and the Conversation page explains why the DM composer is hidden for unmessageable nodes (#4140). Also fixed: a Default Map Center regression on the Unified/Dashboard map (#4128), MeshCore-only installs whose global schedulers never started (#4146), and a stale-config Docker armv7 build (#4122). Finally, two latent cross-platform bugs surfaced during release validation were fixed: a directory case-collision that broke the macOS/Windows desktop build (#4144), and a MySQL 8 collation mismatch that aborted a migration on MySQL deployments (#4145).

Features

• MQTT geo-ignore rearchitecture (fixes #4115): fail-open ingestion with a per-source ignore list, retroactive purge, and auto-reappearance — #4123 (data layer), #4131 (fail-open gating), #4132 (retroactive sweep), #4136 (observability + docs)
• MQTT Packet Monitor: per-gateway packet reception capture — #4127 (backend), #4138 (gateway-aware UI)
• Show latitude/longitude/elevation as text in Node Info & Node Details — #4134
• Map Analysis: Show RF / UDP / MQTT transport toggles — #4135
• Per-theme (light/dark) map tileset preferences, including custom tiles — #4118
• Backend elevation service for terrain link profiles (Phase 1) — #4143

Bug Fixes

• Reliably un-hide nodes from the map across sources; consolidate orphaned rows from removed sources — #4141
• Explain the hidden DM composer for unmessageable nodes — #4140
• Honor the Default Map Center setting on the Unified/Dashboard map — #4128
• Keep global schedulers alive on MeshCore-only installs — #4146
• Migration 122: fix illegal collation mix on MySQL 8 — #4145
• Consolidate Mqtt/ into MQTT/ to fix the desktop-build case-collision on macOS/Windows — #4144
• Drop deleted watchdog scripts from the armv7 Dockerfile — #4122

Chore

• Bump version to 4.13.1-rc1 — #4142

Issues Resolved

#4115, #4137, #4139, #4130, #4129, #4125, #4124, #4096, #4020

Full changelog: https://github.com/Yeraze/meshmonitor/compare/v4.13.0...v4.13.1-rc1

🚀 MeshMonitor v4.13.1-rc1

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:4.13.1-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.

[!IMPORTANT]

Before you upgrade

ESP32-S3 / ESP32-C boards — one-time serial reflash required; WiFi-OTA cannot bridge this update. This release moves the application to a new flash location (0x10000). A board on the old layout can't update to this build over WiFi-OTA or the browser flasher — flash the -merged.bin once over USB/serial. Affected boards: Heltec V3 / V4 / V4.3, Station G2, Wireless Tracker / V2, XIAO ESP32-S3 / C3 / C6, LilyGo T-Lora C6. Your identity, contacts, channels, prefs, and BLE bonds are preserved. After this reflash, OTA and app-updates work again.

nRF52, classic ESP32 (T-Beam / PICO-D4 / TTGO LoRa32), STM32WL, and native Linux are unaffected — upgrade as usual.

From v1.16.2 / v1.16.3 / v1.16.4 — clean flash, no re-bond, bonds and data survive.

From v1.16.1 or older — flash it; on first boot it clears BLE bonds automatically (identity, contacts, channels, prefs preserved). Re-bond your phone/desktop once.

Coming from Arduino MeshCore — flash it; auto-formats on first boot (new identity, clean storage).

Take this with a grain of salt — try the formatters if anything anomalous happens with your node.

The headline of this release: Adaptive CAD, a self-tuning listen-before-talk that calibrates itself to each site; V-Contact, an in-app admin "channel" for companions; and a batch of LoRa-driver reliability fixes.

Highlights

Fixed: ESP32 WiFi-OTA silently reverted — upload hit 100%, then booted the old firmware

On ESP32-S3 / ESP32-C boards, the app and MCUboot bootloader were using different flash partition tables, so each OTA update landed at an address the bootloader never checked. Every upload "succeeded" and then quietly did nothing. Both images now share one partition map, and OTA works correctly. (The XIAO C3/C6 and T-Lora C6 used the stock layout and were never affected.)

ESP32 app slot moved to 0x10000

The ESP32 app slot moved from 0x20000 to 0x10000 — matching the Arduino / ESP-IDF offset. This is the change that fixes OTA above, and it also enables the configurator's fast app-only update (rewrites just the app, keeps your settings). Requires the one-time serial reflash (see Before you upgrade).

New: Adaptive CAD — listen-before-talk that tunes itself to your site

Every transmission is preceded by a Channel Activity Detection (CAD) check that listens for other LoRa traffic and holds off if the channel is busy. How sensitive that check is has always been a single hardcoded number — but the right value depends on where the node lives. A quiet valley node and a 50-network hilltop need very different thresholds: too sensitive and the node keeps deferring for phantom traffic (wasted airtime, latency); not sensitive enough and it transmits over real packets (collisions).

Nodes now measure their own RF environment and adjust automatically. In the background, between transmissions, the radio runs short calibration probes, tracks how often each sensitivity level produces a false "busy", and settles on the lowest false-positive threshold for that site — responding to a changing environment within an hour or two. It runs on repeaters and companions, and it is on by default; there is nothing to configure.

• get cad — watch what it's doing: the current threshold and per-level false-positive statistics.
• set cad.auto off — turn off the auto-adjust to observe or hand-tune with set cad.offset.

Quiet sites end up more sensitive than the old fixed default (fewer stomped packets); noisy sites back off until the false alarms stop. CAD also now uses 4 detection symbols everywhere, which improves detection of an in-progress packet's payload (not just its preamble). Full guide, including the honest limitation that the "missed detection" side isn't locally observable, is in **[ADAPTIVE_CAD.md](https://github.com/liquidraver/ZephCore/blob/master/zephcore/ADAPTIVE …

Device firmware for LilyGo T-Deck and ThinkNode M9. Install via SD card (firmware.bin) or the in-firmware updater.

SHA-256:

• TDeck: 2f9f587f41fc751e8f91900772f000c2aa1ef68eefd585bd604d407b2341a9d2
• M9: a58f9a8b5cf2516022c26c8075d52ed97896c245945da519eeca40cd3c6420e7

✅ Stable channel. Install via the web flasher (Stable), the LauncherHub WADAMESH entry, or a -merged.bin below. Newer test builds live on the Beta channel.

🙏 Community: big thanks to @codemonkeybr for the entire LilyGo T-LoRa Pager port (#149).

✨ Control wadamesh from a browser (over Wi-Fi — no app, account or cloud)

• Web control panel — run the device from a phone or laptop browser: full Chats, Contacts, Discovered, Terminal and Settings tabs, served by the device itself. Turn on the VNC app, then open http://<device-ip>:8765/ on the same network.
• VNC mirrors the live screen and lets you drive it; REMOTE renders the whole UI at a larger, browser-friendly resolution with a Rotate button for desktop/phone layouts.
• Web Contacts (search/sort/filter, distance + last-heard, per-contact actions, one-tap "Add" for Discovered nodes) and Chats (arrival pop-ups + beep, auto-refresh, acks + repeats-heard on messages you send from the browser).

🌐 On-device web browser + links in chat

• New "Web" app (8 MB boards — T-Deck, Tanmatsu): open a URL and read the page as plain readable text — no proxy, tracking, JS or images — with tappable links and back/forward/refresh.
• Links in chat are tappable — "Open in web", or "Create QR" to scan the link onto your phone (works on every board, incl. the Heltec V4).

📟 New boards

• LilyGo T-LoRa Pager (ESP32-S3) — QWERTY + rotary-encoder handheld, no touchscreen; both radio variants (LR1121 / SX1262). (by @codemonkeybr, #149)
• LilyGo T-Display P4 (ESP32-P4) — AMOLED touchscreen handheld. Early port ("partially supported"): mesh, chat, map, GPS, phone-app companion work; BT pairing unavailable (stock coprocessor limit — use Wi-Fi/USB).
• Heltec V4-R8 (8 MB PSRAM + Expansion Kit V2 microSD) — "partially supported" while hardware testing finishes.

🛠 Fixed

• Heltec V4 map tiles now fill the whole map (2 MB-PSRAM tile-pool fix), and web/tile fetching is more resilient under memory pressure.
• Heltec V4-R8 random hard-freezes (shared-I2C bus wedge) fixed.
• Tanmatsu / keyboard-only boards — the Wi-Fi name + password fields are selectable/editable again.
• T-Display P4 clock sets over Wi-Fi even where NTP is blocked; no more stuck bad-date.
• French (AZERTY) on-screen keyboard spacebar restored in the normal letter view.
• REMOTE works on the Heltec V4 (and 2 MB boards); keyboard-less boards leave it by holding the screen ~3 s, and the web page has an "Exit remote" button.

📦 Boards

T-Deck · Heltec V4 TFT · Heltec V4-R8 · ThinkNode M9 · RAK TAP v2 · T-LoRa Pager (LR1121 / SX1262) · T-Display P4.

MeshMonitor 4.13.0 is the largest release of the 4.x line, stabilized through three release candidates. The headline is the Map Consolidation epic: every map surface — Dashboard, Nodes, Map Analysis, MeshCore, Unified, and embeds — now shares one rendering core, one layer library, and one popup family, so features and fixes land everywhere at once. On top of that come node selection and Follow mode, a distance-measurement tool, a polar grid overlay, and a long list of map interaction fixes. MeshCore gains message delete/purge, automatic send retries, Auto-Pathfinding target filtering, a configurable CLI timeout, and a completed Virtual Node command surface. Automations pick up multi-channel triggers, a scheduled device-reboot action, and per-source tapback routing. The long-standing "low-battery alerts silently never fire" bug — reported five separate times — is fixed at its root. Under the hood, a major architecture remediation unified the source-manager registry, moved fresh installs to migration-replay bootstrap, and deleted the legacy synchronous database API. Three deliberate breaking changes ship in this release: auto-upgrade is retired, TRUST_PROXY defaults to false, and source-scoped API endpoints require an explicit sourceId — see Upgrade Notes below. Docker users: :latest now only moves on stable releases like this one; RCs publish to :dev.

📖 Release announcement · Full changelog

Features

Maps

• Map Consolidation epic: shared BaseMap shell, layer library, unified node-marker factory, one popup family, canonical traceroute rendering on all maps including embeds — #4049, #4051, #4057, #4060, #4064, #4065, #4066, #4067, #4068 (epic #4047)
• Node selection, emphasis & Follow mode with auto-zoom on Map Analysis — #4010, #4012 (#3788)
• Node-to-node line-of-sight distance measurement tool on all maps — #4013 (#3636)
• Polar grid overlay (Map Analysis, Unified, MeshCore) — #3983, #4071 (#3971)
• Pan/zoom/spiderfy interaction polish: zoom clamp, scaled animations, zoom-gated spiderfy — #4072 (#4046)

MeshCore

• Delete/purge messages: per-message, per-conversation, purge-all — #3984 (#3981)
• Automatic DM retry via same-path + flood cadence; opt-in auto-retry for automated channel sends — #3980, #3988 (#3977, #3979)
• Auto-Pathfinding target filtering: allowlist, name regex, last-heard, hops, signal — #4039 (#4024)
• Configurable remote/local CLI reply timeout — #4033 (#4027), honored in VN relay via #4107
• Virtual Node: relay status requests & neighbour queries — #3991, #3993 (#3904)
• Collapsible node list for mobile map access — #4079

Automation

• Multi-channel message trigger OR-list — #3982 (#3974)
• Scheduled device-reboot action — #4002 (#3995)
• "Send via sources" selector on the tapback action — #3997 (#3996)

Other

• UDP Broadcast network setting (enabled_protocols) exposed — #4113 (#4112)
• Update-available notifications with per-deployment upgrade instructions (replaces auto-upgrade) — #4108

Bug Fixes

• Low-battery/inactive-node alerts lost to split per-source notification preferences — #4035 (#3417, #3462, #3671, #3884, #4020); leftover UNIQUE(user_id) autoindex dropped — #4045 (#4044)
• Map: popup/spiderfy decoupling + obscured-marker declutter on all maps — #4022, #4028 (#4015, #4016)
• Map: click no longer snaps view back or freezes interaction; wheel zoom, zoom-to-node, chunk-reload self-heal — #4071, #4080, #4082, #4098
• Map: Null Island / out-of-range positions filtered from markers and line endpoints — #4077, #4078, #4099, #4101, #4103
• Map: ROUTER_LATE renders as repeater tower — #4076 (#4075); tileset switch no longer remounts/flickers the raster layer — #4097
• Dashboard map: neighbor lines honor the configured map endpoint — #4055 (#4042), thanks @temalo
• MeshCore: automation DM triggers populate …

Based on MeshCore v1.16.0 main@e8d3c53ba1ea863937081cd0caad759b832f3028

Correções

• CLIENTE: A página inicial do GPS agora fica oculta no carrossel quando nenhum GPS é detectado na porta série no arranque, em vez de aparecer sempre quando ENV_INCLUDE_GPS está ativado.
• REPETIDOR: Corrigido envio de anúncios por inundação (flood adverts): agora respeita o default_scope e o modo de hash de caminho (path_hash_mode nas preferências).
• REPETIDOR: Melhorada a rotina de sleep com rearmar de wake sources. (upstream v1.16.0 bug)
• REPETIDOR: Removida a redução probabilística de flood adverts.

Melhorias

• CLI: Adicionada a leitura do motivo de arranque do ESP32 (get pwrmgt.bootreason).
• CLI: Reforçada a cópia segura de strings no tratamento de comandos.
• RÁDIO: Ajustado o atraso de retentativa CAD para intervalo entre 120 a 360 ms.

Observabilidade

• DISPATCHER: Adicionados logs de debug para conclusão de TX.
• ESTATÍSTICAS: Removidos parâmetros não usados na formatação de respostas.

Build e Configuração

• BUILD: Adicionada a variável DISABLE_DEBUG ao processo de build.
• BUILD: Reorganizadas as build flags no platformio.ini.

Important: Reticulum contacts cleanup (one-time)

If you use Reticulum and see non-contacts (peers / announce-only destinations) listed under Contacts, that comes from an earlier bug that promoted announces into the contact list. This release stops that pollution going forward, but existing bad rows are not removed automatically.

One-time fix: App tab → Danger Zone (Reticulum) → Clear all LXMF contacts.
Peers stay on the Peers tab with their names; chat history is kept. Real contacts return when you message someone or use Save as contact.

Highlights

Reticulum gets much more reliable LXMF DMs (delivery announces, Direct/path-aware sends, saturation hardening), a safer contacts model, faster Peers at large path-table sizes, and interface UX fixes (TCP/UDP/I2P auto-restart, copy LXMF hash, mic for voice clips). Official macOS builds can now be Developer ID signed and notarized. Chat hop badges for MeshCore and Meshtastic are fixed, packaging/smoke and long-session stability are hardened, and several flasher / i18n / BT PIN nits land with it.

What's Changed

Features

• Apple code signing and notarization — Official macOS artifacts can be Developer ID signed and notarized when repo secrets are set; fork/local builds still skip gracefully (#657)
• Reticulum interfaces and chat UX — Auto-restart stack after TCP/UDP/I2P/pipe (and host/port) interface changes; copy full LXMF hash from Network identity; microphone permission path for LXMF voice clips; clearer DM egress badges; DM pills promoted into the main chat row; quieter propagation sync (#674)
• Reticulum DM path reachability — Active DM destination probe / reachability indicator when the stack is live (#672)

Bug Fixes

• Reticulum LXMF delivery and inbound receive — Emit LXMF delivery announces, register inbound destinations, prefer Direct/path-aware signed sends, mark stale queued rows failed (#672)
• Reticulum contacts vs announces — Named announces no longer create contacts; App Danger Zone can clear all LXMF contacts while keeping Peers and chat (#672)
• Reticulum under transport saturation — Path-request backoff, diagnostics for link/timeouts/share_instance conflicts, stuck Sending → failed, propagation-node Chat notice (#669)
• Reticulum identity / Peers / Nomad — Restore Reticulum tab on launch; header shows Network display name; faster Peers at large tables and after announces; JSON/msgpack peer name parsing; stack restart race fixes (#672, #666, #667)
• Reticulum chat polish — Unread badges clear after reading DMs; hop count restoration; identity/announce defaults (#674, #667)
• Chat hop badges (MeshCore + Meshtastic) — Companion pathLen → hop count; wider raw-log correlation fallback; Meshtastic viaMqtt / hopStart===0 aligned with node/diagnostics semantics (#670)
• RNode flasher resilience — KISS command timeouts, ESP32/nRF52 stall watchdogs, BT pairing timeout, humanized errors (#664, #665)
• Packaging / CI smoke — ZIP+DMG verification (mount before validate), AppImage extract cwd, no raw .app CI uploads, CodeQ …

• Neuer Service services/calibre_books: zieht das Buecherregal "Fennek" (Shelf, Name oder ID) von Calibre-Web via OPDS und laedt neue EPUBs nach /books (Basic-Auth, Dateiname aus Content-Disposition)
• Nur-hinzufuegend: Manifest /.fennek/calibre.tsv, max. 8 Downloads/Lauf
• Auto-Sync vor dem Auto-Standby hoechstens alle 6 h + RTC-Back-off
• Konsole: calibre url/user/pass/shelf/on/off/sync + Status

🤖 Generated with Claude Code

(re-release because vContact caused regression in settings import / update)

[!IMPORTANT]

Before you upgrade

ESP32-S3 / ESP32-C boards — one-time serial reflash required; WiFi-OTA cannot bridge this update. This release moves the application to a new flash location (0x10000). A board on the old layout can't update to this build over WiFi-OTA or the browser flasher — flash the -merged.bin once over USB/serial. Affected boards: Heltec V3 / V4 / V4.3, Station G2, Wireless Tracker / V2, XIAO ESP32-S3 / C3 / C6, LilyGo T-Lora C6. Your identity, contacts, channels, prefs, and BLE bonds are preserved. After this reflash, OTA and app-updates work again.

nRF52, classic ESP32 (T-Beam / PICO-D4 / TTGO LoRa32), STM32WL, and native Linux are unaffected — upgrade as usual.

From v1.16.2 / v1.16.3 / v1.16.4 — clean flash, no re-bond, bonds and data survive.

From v1.16.1 or older — flash it; on first boot it clears BLE bonds automatically (identity, contacts, channels, prefs preserved). Re-bond your phone/desktop once.

Coming from Arduino MeshCore — flash it; auto-formats on first boot (new identity, clean storage).

Take this with a grain of salt — try the formatters if anything anomalous happens with your node.

The headline of this release:

New: flash ZephCore from your browser — Mesh America configurator

ZephCore is now a listed provider in the Mesh America Device Configurator. Pick your board and flash directly — companion (BLE and USB) or repeater — no toolchain, no drag-and-drop.

Adaptive CAD, a self-tuning listen-before-talk that calibrates itself to each site;

V-Contact, an in-app admin "channel" for companions; and a batch of LoRa-driver reliability fixes.

Highlights

Fixed: ESP32 WiFi-OTA silently reverted — upload hit 100%, then booted the old firmware

On ESP32-S3 / ESP32-C boards, the app and MCUboot bootloader were using different flash partition tables, so each OTA update landed at an address the bootloader never checked. Every upload "succeeded" and then quietly did nothing. Both images now share one partition map, and OTA works correctly. (The XIAO C3/C6 and T-Lora C6 used the stock layout and were never affected.)

ESP32 app slot moved to 0x10000

The ESP32 app slot moved from 0x20000 to 0x10000 — matching the Arduino / ESP-IDF offset. This is the change that fixes OTA above, and it also enables the configurator's fast app-only update (rewrites just the app, keeps your settings). Requires the one-time serial reflash (see Before you upgrade).

New: Adaptive CAD — listen-before-talk that tunes itself to your site

Every transmission is preceded by a Channel Activity Detection (CAD) check that listens for other LoRa traffic and holds off if the channel is busy. How sensitive that check is has always been a single hardcoded number — but the right value depends on where the node lives. A quiet valley node and a 50-network hilltop need very different thresholds: too sensitive and the node keeps deferring for phantom traffic (wasted airtime, latency); not sensitive enough and it transmits over real packets (collisions).

Nodes now measure their own RF environment and adjust automatically. In the background, between transmissions, the radio runs short calibration probes, tracks how often each sensitivity level produces a false "busy", and settles on the lowest false-positive threshold for that site — responding to a changing environment within an hour or two. It runs on repeaters and companions, and it is on by default; there is nothing to configure.

• get cad — watch what it's doing: the current threshold and per-level false-positive statistics.
• set cad.auto off — turn off the auto-adjust to observe or hand-tune with set cad.offset.

Quiet sites end up more sensitive tha …

• Schlaf-Diagnose im RTC-RAM (Phase-Breadcrumb + Wake-Historie, beim nächsten Vollboot ins battlog)
• Task-Watchdog um Timer-Wake-Minimalpfad (30 s) und enterStandby (60 s), Loslass-Warteschleife mit 10-s-Timeout
• Crash-Loop-Bremse: 3 abnormale Resets in Folge → Not-Standby (nur Knopf-Wake), Crash-Boots flushen sofort auf SD
• Tiefentladeschutz: ≤5 % auf Akku → sofort Standby, im Schlaf keine Stunden-Wakes mehr (Wecker bis 3 %)
• GPIO42 (Tastatur-Backlight-Gate) über Deep Sleep gehalten, E-Ink-Controller vor Deep Sleep in hibernate()
• Launcher: Kachel-Icons links + Text-Label, Lage/Gyro-App deaktiviert

• New setting: choose whether unsynced messages are saved to flash. (Companion — all platforms)

  Companion → Settings → Message Persist, or CLI get/set msg.persist. Off by default — unsynced messages only live in RAM until the app syncs them. Turn on to also persist them to flash so they survive a crash, reboot, or dead battery before the app catches up. Turning off immediately clears any already-persisted copy from flash.

  On NRF52 boards (T096, RAK4631), each persisted message costs one physical flash-page erase, on a small 100KB partition shared with contacts — fine for normal personal use, but sustained heavy traffic (hundreds to 1000+ msgs/day) wears against that partition's erase-cycle lifetime faster than typical usage. ESP32 boards aren't affected: SPIFFS appends into already-erased space and only erases a block during garbage collection, not on every message write.

⚠️ Pre-release (Release Candidate). This build is for testing the 4.13.0 map-consolidation and MeshCore work ahead of the stable release. Not recommended for production; back up your database before upgrading.

This release candidate builds on rc2 with a focused round of map interaction fixes and a MeshCore Virtual Node correctness fix. The map work resolves several regressions from the map-consolidation epic: click-to-pan now targets the actual node marker instead of the raw center, user gestures (zoom/pan) correctly cancel node-centering instead of snapping back and freezing, and raster tile layers no longer remount and flicker when the tileset changes. Null Island (0,0) coordinates are now filtered from both markers and line endpoints, and out-of-range/invalid node positions are detected and trimmed. Pan/zoom/spiderfy behavior was polished with a zoom clamp, scaled animations, and zoom-gated spiderfy. ROUTER_LATE nodes again render as repeater-tower icons on the NodesTab and Dashboard maps. On MeshCore, the Virtual Node login now relays the admin flag and firmware level, and the mobile node list is collapsible so the map is reachable without selecting a node. This candidate also folds in a large batch of dependency updates and a translations refresh.

Features

• Map: pan/zoom/spiderfy interaction polish — zoom clamp, scaled animations, zoom-gated spiderfy, re-spiderfy on zoom (#4072, resolves #4046)
• MeshCore: collapsible node list — reach the map on mobile without selecting a node (#4079)

Bug Fixes

Map

• Click pans to the node marker, not the raw center, for obscured nodes (#4082)
• User gesture cancels node-centering — zoom no longer snaps back (#4098)
• Fixed map snapping back to node on click and freezing interaction (#4080)
• Stopped raster tile layer remounting on tileset change (abort/flicker) (#4097)
• Detect and trim out-of-range (invalid) node positions (#4099)
• Widen Null Island radius + skip it in the unified merge (#4077)
• Null-island filter for line endpoints — routes + neighbors no longer run to 0,0 (#4078)
• ROUTER_LATE renders as a repeater-tower icon on NodesTab + Dashboard maps (#4076, resolves #4075)
• Integrate resolveMapEndpoint into DashboardMap neighbor lines (#4055, resolves #4042)
• Post-epic fixes: wheel zoom, zoom-to-node, chunk-reload self-heal; MeshCore polar grid + map loading states (#4071)

MeshCore

• Relay admin flag + firmware level in Virtual Node login (#4095, resolves #4094)

Translations

• Translations update from Hosted Weblate (#4006)

Dependencies

• Bump the production-dependencies group with 9 updates (#4084)
• Bump the development-dependencies group with 3 updates — @types/node, eslint, vitest (#4083)
• Bump protobufjs 8.6.6 → 8.7.0 (#4090)
• Bump helmet 8.2.0 → 8.3.0 (#4092)
• Bump lucide-react 1.22.0 → 1.24.0 (#4085)
• Bump re2 1.25.0 → 1.26.0 (#4088)
• Bump @typescript-eslint/eslint-plugin 8.62.1 → 8.63.0 (#4089)
• Bump @typescript-eslint/parser 8.62.1 → 8.63.0 (#4087)

Issues Resolved

• #4094 — MeshCore: Virtual Node functionality still does not work correctly
• #4093 — MeshCore: Channels no longer marked unread
• #4075 — ROUTER_LATE renders as generic pin (not repeater tower icon) on NodesTab and Dashboard maps
• #4046 — Map UI: improve pan/zoom-to-center behavior and its interaction with marker spiderfy
• #4042 — Dashboard Unified map: neighbor-info lines don't follow merged node marker position

Full changelog: https://github.com/Yeraze/meshmonitor/compare/v4.13.0-rc2...v4.13.0-rc3

🚀 MeshMonitor v4.13.0-rc3

📦 Installation

Docker (recommended):

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

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

Device firmware for LilyGo T-Deck and ThinkNode M9. Install via SD card (firmware.bin) or the in-firmware updater.

SHA-256:

• TDeck: 5a7da903153d2ba4790585b1a692ad443021f85c47798afe18015ac3a7115622
• M9: b44357a68874adc43e9b0d3a579006d8a5d7e726b61df39ce81510878dfe003b

Flash it from flasher.wadamesh.com (flip the Beta toggle), or grab a -merged.bin below (flash at 0x0). On the device, beta testers can also enable Settings → Get test builds (beta).

New - on-device web browser

A new Web app opens a URL and shows the page as plain, readable text - articles, wikis, docs, plain sites - right on the device. No proxy, no tracking, no JavaScript or images: just the words. Links are tappable, with back / forward / refresh.

The browser needs the RAM only the 8 MB boards have (T-Deck, Tanmatsu), so it is hidden on the 2 MB Heltec V4 - that board can't complete an on-device HTTPS handshake.

New - tappable links in chat

Links in a chat now render in blue. Tap one for a small menu:

• Open in web - loads the page in the on-device browser (8 MB boards).
• Create QR - shows a scannable QR code so you can open the link on your phone. This works on every board, including the Heltec V4 - so even where the browser isn't available, you can still bounce a link to your phone.

Fixed

• French (AZERTY) on-screen keyboard: the spacebar (and the OK / keyboard-switch keys) are back in the normal letter view. You no longer have to switch to the symbols page just to type a space. (A stray empty entry was cutting the keyboard map short.)
• Heltec V4: web page fetching and map tiles are more resilient when memory is tight.
• Home signal & traffic box: the "tap for details" cue is back at the top of the box.

This is a test-channel (beta) build. Devices on the beta update feed will offer it; stable stays on beta_40.

• Debug logs are now kept locally for 7 days instead of 24 hours. Logs are kept on your device.

Bug Fixes

• Fixed an issue where a momentary gap during automatic reconnect could silently drop the radio connection until the app returned to the foreground.
• Reduced unnecessary re-pair prompts. A brief encryption hiccup at the edge of Bluetooth range no longer tells you to re-pair a radio whose pairing still works.

Full Changelog: https://github.com/Avi0n/MeshCoreOne/compare/v1.2.0...v1.2.1

v1.0.42 - 2026-07-12

Added

• Tropospheric Ducting Forecast: View 6-day VHF/UHF ducting forecast maps from dxinfocentre.com. Select from 23 global regions, scrub through 28 forecast frames (3h intervals for first 36h, 6h intervals after), pinch to zoom, and animate with playback controls. Region selection persists between sessions. Access from Settings under the Atmospheric Ducting section.

• Link/image preview settings are now easier to understand. Both images and link previews are now under "Show Link Content" in Chat settings.
• Repeater neighbors can now be viewed on a map. In Telemetry > Neighbors, tap "View on Map" to see a full-screen map of its neighbors and signal strength to each.
• Message path maps now display the total hop count and path distance.
• Map controls are now cleaner and simpler across all map screens.
• Contact nicknames are now shown in channels
• Visual tweaks to channel/chat/contact info pages to make them more uniform.
• Theme aware QR code.
• Scanning MeshCore contact QR codes with the system camera app now offers to open MC1.
• Telemetry now shows Direct/Flood for Packet metrics. Packet graphs now show both metrics. NOTE that this will start a new chart because it graphs both direct and flood packets.
• Opening the Nodes tab now defaults to Favorites if you have at least one favorited node.
• In Trace Path tool, removed 10x batch option and defaulted to 3x.
• In Trace Path tool results, now shows a percentage of successful batch traces.
• Added a Chile community radio preset.

Bug Fixes

• Fixed sent messages not listening long enough for heard repeats
• Fixed an "item not found on device" error when logging into a repeater whose contact was missing from the radio (for example after a backup restore or radio reset). The app now restores the contact and retries automatically.
• You can now enter negative latitude and longitude for remote nodes, and comma decimal separators no longer break coordinate entry.
• Remote-node coordinates and names are now validated before saving, so out-of-range values or over-long names are caught up front instead of being silently altered by the firmware.
• Fixed incorrect centering on the message path, neighbor, and trace path maps.
• Fixed duplicate chat messages that could appear when a repeated broadcast arrived after the previous match window.
• Fixed inability to remove a nickname
• Fixed Repeat Mode not enabling correctly for 869.495 Mhz
• Fixed zero hop ping timeout being too long
• Fixed BLE not reconnecting in the background in some situations
• In Telemetry Neighbors, neighbors no longer have a "New" tag when they weren't actually new.
• Fixed some website image preview cards not loading
• Fixed Repeater Management not getting the correct TX value from repeaters running ZephCore

New Contributors

• @mabahamo made their first contribution in https://github.com/Avi0n/MeshCoreOne/pull/336
• @bwees made their first contribution in https://github.com/Avi0n/MeshCoreOne/pull/342
• Full list of @bwees contributions:
  • https://github.com/Avi0n/MeshCoreOne/pull/342
  • https://github.com/Avi0n/MeshCoreOne/pull/344
  • https://github.com/Avi0n/MeshCoreOne/pull/352
  • https://github.com/Avi0n/MeshCoreOne/pull/353
  • https://github.com/Avi0n/MeshCoreOne/pull/354
  • https://github.com/Avi0n/MeshCoreOne/pull/358
  • https://github.com/Avi0n/MeshCoreOne/pull/359
  • https://github.com/Avi0n/MeshCoreOne/pull/360
  • https://github.com/Avi0n/MeshCoreOne/pull/361

Full Changelog: https://github.com/Avi0n/MeshCoreOne/compare/v1.0.1...v1.2.0

Device firmware for LilyGo T-Deck and ThinkNode M9. Install via SD card (firmware.bin) or the in-firmware updater.

SHA-256:

• TDeck: a96356b479cce107d6359546592a49e88a61782e0407e42ade909513fb47c25a
• M9: 576925cf23254c60fa877a664116742302b4ca6d8f8474669124e1a3d5413a2d

Flash it from flasher.wadamesh.com, or grab a -merged.bin below (flash at 0x0). Boards: LilyGo T-Deck and Heltec V4 TFT.

New - web control panel

The browser panel is now a full remote app, so you can run the device from a phone or laptop without picking up the T-Deck. Proper Chats, Contacts, Terminal and Settings tabs.

• Contacts: search, sort and filter; each contact shows distance, coordinates and last-heard age; tap for the same actions as on the device (favourite, block, reset path, remove).
• Discovered nodes appear in the browser with a one-tap Add to save them as contacts, so you can build your whole contact list from the web app.
• Chats: pop-up notifications (with an optional beep) on a new message, and the open chat refreshes on its own as replies come in.
• Acknowledgements and repeats-heard now show for messages sent from the web app.
• A Settings page for the everyday options that make sense remotely, including live radio changes.
• A quick-command button in the Terminal that drops common commands into the input.

Fixed

• Heltec V4 map tiles: tiles downloaded but only the top of the map rendered (the rest stayed black). The 2 MB-PSRAM V4 was running out of contiguous memory for the tile grid; tiles now reuse a small fixed pool and only load what is on screen, so the whole map fills in smoothly again.
• Heltec V4 remote/VNC: typing from a physical keyboard in the browser now works (it previously only worked on the T-Deck).
• Remote-access screen on the device is clearer: the IP address is at the top, the explanation is shorter and more accurate, the toggles sit above it, and the address box only appears once remote access is on.
• Terminal help now lists every command, on both the device and the web terminal.

Changed

• The web app header shows the same signal, Wi-Fi, Bluetooth and battery icons as the device status bar, and the title reads WADAMESH.
• Contact and chat sort/filter controls open a menu to pick an option instead of cycling on each tap.
• New developer Tile debug overlay toggle in Map options (off by default) for diagnosing map-tile issues.

This is a test-channel (beta) build. Devices on the beta update feed will offer it; stable stays on beta_40.

Flash with esptool

# Full flash (first install):
esptool.py --chip esp32s3 --port /dev/ttyACM0 write_flash 0x0 firmware-merged.bin

# App update (keep settings):
esptool.py --chip esp32s3 --port /dev/ttyACM0 \
  write_flash 0x10000 firmware.bin

Web Flasher

Use manifest.json with esptool.js.

What's Changed

• fix: safe SPIFFS init with erased-partition auto-format (closes #750) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/751
• Phase 1: Switch keyboard to key mode for multi-model T-Deck compatibility (#752) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/753
• Phase 2: Multi-language keyboard layout system (12 layouts) — #752 by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/754
• Phase 3: I2C robustness improvements — #752 by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/755
• fix: keyboard doesn't work — I2C timeout kills cold boot (#752) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/756
• [codex] use C3 key mode for multi-model keyboards by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/757
• [codex] Add persisted international keyboard layouts by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/758
• [codex] Harden shared I2C initialization and recovery by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/759
• Fork Merge: Radio profiles, diagnostics, RX-only mode, CI fixes by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/760
• fix: battery -% on menu nav, cursor visibility, RSSI chart labels by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/766
• fix(ci): exclude LauncherCompatibility.md from doc reference check by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/767
• docs: comprehensive repository-wide audit (audit.md) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/770
• fix(gps): correct GPS-to-Unix-epoch conversion (BUG-001) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/771
• fix(ui): prevent dangling g_wifi_icon use-after-free (BUG-002) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/772
• fix(hw): guard deep-sleep RTC-GPIO calls on non-RTC DIO1 pin (HW-001) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/773
• fix(mesh): hoist sender_buf out of if-block to prevent use-after-scope (BUG-003) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/774
• fix(mesh): return correct contact in processAck instead of contact[0] (BUG-004) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/775
• fix: batch of low-severity fixes (HW-002, DEAD-002..004, DOC-001, BUILD-001) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/776
• fix(security): add OTA PIN brute-force rate limiting (SEC-001) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/777
• docs: add remediation status to audit.md (7 PRs submitted) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/778
• perf(display): lazy-allocate emergency buffer, reclaim 12.8KB DRAM (PERF- …

• New: reach Companion via mDNS hostname instead of typing an IP. (Companion — WiFi transport, V3, V4, E213, E290, Wireless Paper, XIAO S3)

  When connected over WiFi, the node is now reachable at meshcore-xxxx.local (xxxx = the first 2 bytes of its public key, unique per node) instead of needing to know its DHCP-assigned IP. Confirmed working with the official MeshCore app.

• New: unsynced messages now survive a crash or reboot. (Companion)

  Previously, any message received while the app wasn't connected only lived in RAM — a crash, reboot, or dead battery before the app had a chance to sync meant it was gone for good. Unsynced messages are now also saved to flash and restored automatically on boot, along with the on-device unread indicator. USB-connected companions are covered too, since USB has no reliable way to detect whether the app is actually listening — messages are saved as they arrive rather than waiting for a disconnect that may never be seen in time.

• New: e-ink ghost-clearing. (Companion, Repeater, Room Server — E213, E290, Wireless Paper)

  Each boot now runs a quick black/white flush to prevent ghosting from building up, Companion adds a Settings → Clear Ghost action for a deeper manual clean, and a static screen gets an automatic full refresh every 5 minutes of idle to prevent burn-in.

⚠️ Pre-release — release candidate for testing; not recommended for production deployments. Docker images are not tagged :latest.

Summary

This release candidate lands the Map Consolidation epic (#4047): MeshMonitor's ten independent Leaflet map implementations are now one shared BaseMap shell, one composable layer library, one popup family, and one marker-icon factory. Traceroutes render identically on every surface — one canonical 4-band SNR color scale (previously three different scales), unified MQTT dashing and coloring, and the Dashboard finally renders return legs. Node markers, popups, neighbor links, and accuracy regions are likewise single-sourced, so future fixes apply to every map at once, and public embed maps now show the same canonical traceroute visuals as the app. The epic also surfaced and fixed several latent bugs, including a hidden-node position leak in the public embed traceroutes endpoint and Dashboard coloring segments with unscaled SNR values. On top of the epic, this RC brings map interaction polish (#4046): center-on-node never zooms out and its target zoom is user-configurable, pan/zoom animations scale with distance, clicking a marker at low zoom now zooms in instead of exploding a giant spiderfy fan, and open fans survive zoom changes. Live testing fixes include restored wheel/double-click zoom, correct zoom-to-node for one-way traceroutes, loading indicators on initial map data fetch, a polar grid for MeshCore maps, and a self-healing reload when a stale cached page requests rotated asset chunks after an upgrade.

Map Consolidation Epic (#4047)

• #4068 — Epic integration: one shell, one layer library, one popup family (phases below)
  • #4049 Phase 1 — shared BaseMap shell; pickers and editors migrated
  • #4051 Phase 2 — Map Analysis legend/polar-grid/trails reconciliation
  • #4057 Phase 3 — unified traceroute rendering across all app maps
  • #4060 Phase 4 — unified node-marker factory + shared NodeMarkersLayer
  • #4064 Phase 5 — one popup family with composable source-tech sections
  • #4065 Phase 6 — public embeds adopt canonical traceroute rendering (includes a hidden-node position leak fix 🔒)
  • #4066 / #4067 Phase 7 — shared neighbor-links/accuracy/waypoints layers; all maps on BaseMap

Features

• #4072 — Map interaction polish: zoom clamp with configurable target (default 17), distance-scaled animations, zoom-gated spiderfy with zoom-in-first clicks, re-spiderfy after zoom (#4046)
• #4071 — MeshCore map polar grid; map loading indicators during initial fetch

Bug Fixes

• #4071 — Wheel/double-click zoom restored on all maps; zoom-to-node no longer hijacked by route-fit on one-way traceroutes; one-time reload on stale-chunk load failures after upgrades
• #4055 — Dashboard neighbor-info lines follow the merged node marker position (#4042) — thanks @temalo!
• #4045 — Notifications: drop inline autoindex UNIQUE(user_id) missed by migration 079 (#4044)

Issues Resolved

• #4047 — Consolidate 10 independent Leaflet maps into a shared BaseMap shell + composable layer library
• #4046 — Map UI: improve pan/zoom-to-center behavior and its interaction with marker spiderfy
• #4042 — Dashboard Unified map: neighbor-info lines don't follow merged node marker position
• #4044 — Can't configure Apprise Notifications for a second source

Upgrade Notes

• Map visuals converge to one canonical look: the per-source Nodes map moves from a 3-band to the 4-band SNR color scale, no-data segments render dashed gray, the Dashboard gains traceroute return legs, the traceroute widget's legs use the theme color, and embeds show SNR-colored traceroutes instead of uniform mauve.
• New per-user setting: Settings → Map → center-on-node target zoom (default 17).

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v4.13.0-rc1...v4.13.0-rc2

🚀 MeshMonitor v4.13.0-rc2

📦 Installation

Docker (recommended):

docker run
…

• Fixed bug on showing repeaters farther that 50 miles away as unknown. by @venamartin in https://github.com/venamartin/meshtrax/pull/24
• Bugfix: DM duplicate message by @venamartin in https://github.com/venamartin/meshtrax/pull/25
• Chore/flutter analyze cleanup by @venamartin in https://github.com/venamartin/meshtrax/pull/26
• Feature/auto connect last by @venamartin in https://github.com/venamartin/meshtrax/pull/27
• chore: add Google Play Store icon and feature graphic by @venamartin in https://github.com/venamartin/meshtrax/pull/28
• Feature/UI improvements by @venamartin in https://github.com/venamartin/meshtrax/pull/29
• chore: remove dead code files by @venamartin in https://github.com/venamartin/meshtrax/pull/30
• Play Store readiness: moderation, terms, notifications, and defaults by @venamartin in https://github.com/venamartin/meshtrax/pull/31
• Fix/notification tap and names by @venamartin in https://github.com/venamartin/meshtrax/pull/32
• Docs/readme screenshots by @venamartin in https://github.com/venamartin/meshtrax/pull/33
• chore: set Play Store package name to com.vena.meshtrax by @venamartin in https://github.com/venamartin/meshtrax/pull/34
• Lost ble notification by @venamartin in https://github.com/venamartin/meshtrax/pull/35
• fix: resolve ack-queue race that falsely marked USB channel sends as failed by @venamartin in https://github.com/venamartin/meshtrax/pull/36
• chore: bump version to 1.6.2+2 by @venamartin in https://github.com/venamartin/meshtrax/pull/37
• Fix/channel reply wire format by @venamartin in https://github.com/venamartin/meshtrax/pull/38

Full Changelog: https://github.com/venamartin/meshtrax/compare/v1.5.5...v1.6.3

Fixes for the REMOTE mode introduced in beta_41.

Install from the web flasher at https://flasher.wadamesh.com (test channel), or grab a bin below.

Fixed

• REMOTE mode now works on the Heltec V4 TFT (and other 2 MB-PSRAM boards) instead of showing a black screen in the browser. Its off-screen renderer needed more free memory than those boards had, so nothing streamed; the buffers are sized to fit now, and the render is a bit smaller and faster as a result. VNC was never affected and already worked.
• Keyboard-less touch boards (Heltec V4, RAK WisMesh Tap) can leave REMOTE mode again: touch and hold the device screen for about 3 seconds. Those boards have no SPACE key, which used to be the only on-device way out.

New

• The web page has an "Exit remote" button (with a confirmation) that leaves REMOTE mode from any browser, on any board.

Boards in this build: LilyGo T-Deck, Heltec V4 TFT, ThinkNode M9, RAK WisMesh Tap V2.

Experimental web control: view and drive the wadamesh UI from a phone or desktop browser over Wi-Fi. Two new apps, VNC and REMOTE.

Install from the web flasher at https://flasher.wadamesh.com (test channel), or grab a bin below.

New

• VNC app (app drawer, between Advertise and Signal): mirrors the live device screen into a web browser over Wi-Fi and lets you drive it. Taps and typing in the browser control the device, and anything that changes on the device shows up in the browser. Turn it on, then open http://<device-ip>:8765/ from any browser on the same network. The app page itself is scrollable.
• REMOTE app: a headless mode that renders the whole UI at a larger, browser-friendly resolution and serves it over Wi-Fi, while the device's own screen drops to a placeholder showing the address to open. Turning it on or off reboots the device. On the web page a Rotate button flips between landscape (desktop) and portrait (phone); on the device, double-tap the space bar to leave remote mode.
• Both are served by the device itself over plain Wi-Fi, no phone app, no account, no cloud.

Note

This is an experimental first cut, and an honest heads-up from Kaj: for me the remote UI still feels too slow, and I will most likely move toward a dedicated, lighter remote client instead of streaming the entire live UI. It is in this test build mainly because community feedback on it would be genuinely useful. If you try it, let us know how it runs for you and what you would actually want from a web or remote client.

Boards in this build: LilyGo T-Deck, Heltec V4 TFT, ThinkNode M9, RAK WisMesh Tap V2.

Highlights

This release adds Reticulum RMAP v4 discovery (publish, per-interface controls, and a local discovery map tab), unified Reticulum identity import, and a much more scannable Sniffer tab across all protocols. It also fixes Meshtastic MQTT messages landing on the wrong channel tab, hardens triple-protocol BLE coexistence when Reticulum uses a Noble RNode alongside Meshtastic/MeshCore, and migrates the Colorado Mesh MQTT preset to port 443.

What's Changed

Features

• Reticulum RMAP v4 discovery — Publish enabled interfaces to RMAP v4 using App GPS coordinates; per-interface discoverable toggles for RNode, KISS, BLE peer, I2P, UDP, and pipe; Connection tab status strip and sync badges; default hub sync with skip/repair/add; new Map tab with local discovery map (Leaflet), filters, path-table reachability, and link to rmap.world (#649)
• Reticulum identity unification and import — Single unified identity apply path in the sidecar; backup JSON and private key import (hex/base64/file) on the Network tab with replace confirmation (#651)
• Sniffer tab scanability — MeshCore on-air hop chains and path display; Meshtastic collapsed hops and transport/type badges; sortable columns, quick-filter chips, relative timestamps, and hover tooltips across all protocols (#643)

Bug Fixes

• Meshtastic MQTT channel routing — Prefer MQTT topic channel name over sender-local MeshPacket.channel slot for inbound text; add @index hint in Connection panel for MQTT-only setups (#644)
• Triple-protocol BLE coexistence — Suspend Noble for Reticulum RNode pairing on macOS/Windows; paired yield lifecycle so the scan mutex releases on connect, grace expiry, or sidecar stop; reconnect hardening and quieter logs when Meshtastic/MeshCore resume after yield (#645, #653, #655)
• Colorado Mesh MQTT preset — Align MeshCore broker preset to TLS WebSocket on port 443; migrate saved settings off legacy port 1883 (#647, #651)
• Reticulum discovery map resilience — Cap discovery rows (2,000) with 7-day TTL eviction; preserve last-good data on fetch failure; clear stores on disconnect; partial-failure toasts for RMAP apply/disable (#650)
• Meshtastic TCP connect — 20s timeout aligned with other transports; disconnect orphaned sockets on failed connect (#644)
• Channel PSK validation — Reject keys shorter than 16 bytes; accept 1-byte default PSK and bare decrypt-only lengths consistent with MQTT manager (#646, #651)
• Reticulum diagnostics — Omit expected SharedInstanceServer runtime note from actionable faults (#652)
• I2P peer validation — Accept official 60-char testnet .b32.i2p addresses (#649)
• MeshCore waiting-messages poll — Gate idle 5-minute safety poll; treat silent sync timeouts as empty queue (#655)
• Connection banner accessibility — Status region labels, decorative reconnect pulse layer, improved contrast (#655)

Othe

…

• docs: remediation plan + epic status doc (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3966
• feat(server): process-level safety net for unhandledRejection/uncaughtException (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3967
• fix(security)!: default trust proxy to false when TRUST_PROXY is unset (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3968
• chore(deps): pin meshcore.js fork to commit SHA (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3969
• fix(security): strip hot-path console logging and CSRF token exposure in api.ts (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3970
• chore(lint): enable @typescript-eslint/no-floating-promises as error (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3972
• feat(db)!: withSourceScope fails closed — omitting sourceId throws, ALL_SOURCES sentinel for intentional cross-source (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3976
• feat(automations): multi-channel message trigger OR-list (#3974) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3982
• feat(map): add polar grid overlay to Map Analysis and Unified maps (#3971) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3983
• fix(meshcore): auto-retry DM via same-path + flood cadence on ack timeout by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3980
• ci(types): type-check test files via tsconfig.tests.json, non-blocking first (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3985
• fix(meshcore): populate fromName on DM automation triggers, clarify trigger.from vs fromName by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3978
• feat(meshcore): delete/purge messages — per-message, per-conversation, purge-all (#3981) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3984
• test(routes): integration-grade route-test harness with real auth middleware (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3986
• fix(meshcore): exact decrypt-and-match for channel 'repeaters relayed' echo (#3979 pt1) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3987
• feat(meshcore): opt-in auto-retry for automated channel sends (#3979 Part 2) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3988
• chore(lint): count-based lint ratchet — new violations block, existing debt baselined; CI lint now blocking (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3989
• feat(server): codify the { success, error, code } response envelope in ok()/fail() helpers (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3990
• feat(meshcore-vn): relay SendStatusReq(27) status requests to the physical node (#3904) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3991
• test(db): schema-drift tripwire — CI fails on createTables vs migration-replay divergence (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3992
• feat(meshcore-vn): relay GetNeighbours via SendBinaryReq(50) to the physical node (#3904) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3993
• chore(logging): trim default log volume — reclassify routine info→debug, add trace tier by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3994
• refactor(registry)!: MeshCoreManager implements ISourceManager — one unified source registry (#3962) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/4004
• Fix Virtual Node Server boot race and listen-error zombie state by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/4001
• feat(automation): add "Send via sources" selector to the tapback action by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/3997
• feat(automation): add scheduled device-reboot action (#3995) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/4002
• fix(meshcore): match-scope replies unscoped for unnameable trigger scope (#3998) by @Yeraze in https://github.com/Yeraze/meshmonitor/pull/4003

…

Device firmware for LilyGo T-Deck and ThinkNode M9. Install via SD card (firmware.bin) or the in-firmware updater.

SHA-256:

• TDeck: af26586a4d6f7c991c5390827d7d80d0b3479f1b86e02d6054a180a2fec7d78a
• M9: 6f80d53b4d7b7743096a40331aedd261a6efeff8887921b540cdb00778553876