What's new

• Live Location Sharing — broadcast your position over the mesh as [LOC] messages, movement-gated, to a channel or a single contact. Others who share theirs show up as pins on the map with live distance/bearing in Nearby Nodes, and a status-bar indicator appears while your own share is active. [LOC] is parsed in DMs, channel messages and room messages; DM shares name the sender.
• Locator (geofence) — arm a geofence around a target — a saved waypoint or a person (their live [LOC] or last-known position) — and get an alert when you arrive/leave or they get near/far, with an optional homing beeper that ticks faster the closer you get (and overrides a muted buzzer). Arm it from Tools › Locator or straight from Nearby Nodes / Waypoints; pick the target from a list (favourites first, then any contact), and clear it via a "None" entry. The active target is drawn as a flag on the map.
• One active target across Locator / Navigate / Map — a single "Set as target" action everywhere, backed by a shared resolver that prefers a live [LOC] share over the last-advertised GPS, so the three features always agree on where you're headed.
• Follow live contacts — Navigate to a contact who is live-sharing and the view follows them as they move, adding an ETA line. Quick-share your own position straight from the Map.
• Map & status-bar upgrades — the home mini-map gains a north marker and a scale tick; the status line shows the tracked-node count and, with a fix, an arrow + distance to the nearest tracked contact (e.g. Track:3 →120m); a GPS fix icon sits in the top status bar (boxed once a fix is valid, plain while searching), shown only on GPS boards while GPS is enabled in Settings.
• Trail auto-pause — recording freezes on stops (banking elapsed time and breaking the map line across the idle gap) and resumes on movement without ending the session; the home-screen blink keeps going while paused.
• Collapsible Tools — tools are grouped into fold-in-place Location / Comms / System sections, the same model as Settings (Tools always opens folded to the section list), and the home carousel now uses page-indicator icons instead of dots.
• Waypoint coordinate editor — add a waypoint by scroll-editing its latitude/longitude digit by digit.
• On-device room login with saved passwords — log in to a room server straight from the device (no phone app): pick the room and the password prompt appears automatically (a blank password works for open rooms), or re-login any time via the room's context-menu "Login…". The password is remembered across reboots, so a room you've used before logs back in without retyping; a failed login (e.g. the server's password changed) forgets the stale password so the next attempt prompts again. Saved passwords are written with the same atomic, crash-safe persistence as contacts and channels.

Fixes

• Critical — low-heap hang and contact loss on RAM-tight builds. With MAX_CONTACTS=350 and OFFLINE_QUEUE_SIZE=256 the device ran with very little free heap; an allocation in the input/menu path could then fail and hang the UI (notably when entering Diagnostics), and a crash or reset mid-save could wipe all contacts. Fixed by two independent changes:
  • Right-sized message-history rings — the on-device scrollback rings were halved (96→48 channel, 64→32 DM), recovering ~14 KB of free heap (measured 3 → 17 KB). History is RAM-only, so the only cost is shorter on-device scrollback.
  • Atomic persistence — contacts, channels and prefs are now written to a temp file and atomically renamed into place; an interrupted save (crash, reset, full flash) leaves the previous good file intact instead of truncating it.
• USB host stall — `Serial.write …

Fixed / 修复

• Fixed #64 and #41. / 修复 #64 和 #41。

Full Changelog: https://github.com/vicliu624/trail-mate/compare/v0.1.30-alpha...v0.1.31-alpha

A unified release across all three boards — LilyGo T-Deck, Heltec V4 TFT, and the Tanmatsu (ESP32-P4).

Flash it the easy way at https://flasher.wadamesh.com, or grab a bin below. On a normally-flashed device you can also update straight from Settings → About.

✨ New

• Topographic maps — turn on Map → Options → Topographic map for terrain-relief tiles; OpenStreetMap stays the default. Thanks to @samuelcoustet for the proxy work (#52).
• More emoji in the picker: ⚽ 🏈 🗿 🏳️‍⚧️.
• Contacts sorting gained ascending/descending and a new Nearest first distance sort; the Discovered list gets the same sort options.
• The Chats header is tidied up — add / mark-read / share grouped on the left, with a proper QR icon for sharing your contact.

🐛 Fixed

• The USB/PC companion connection no longer drops or throws "bad state" errors — also fixes repeater admin mode disconnecting and member-room login (#25, #54, #23).
• Map edge/corner tiles now fill in as you pan instead of needing a manual reload (#20).
• ~41 KB of memory reclaimed (moved a large buffer to PSRAM) — fixes the Heltec V4 rebooting when loading map tiles, and frees headroom on every board.
• The map's Show link lines toggle now survives a reboot. Thanks to @Yazutsu (#61).
• Settings category names fit on one line (no more mid-word splits); keyboard-nav toggling no longer jumps the list to the top (#45).
• Heltec V4: node name no longer covers the clock (#47a). T-Deck: keyboard backlight no longer stuck on after flashing (#33).
• More reliable crash reporting and fewer stray reboots while saving settings.
• Tanmatsu: LoRa radio changes (frequency, etc.) now take effect immediately without a reboot, and the app's settings drive the radio.

Everything from beta_16 (and the Tanmatsu's beta_17) is included.

Fixed

• RAK3401 1W companion radio dead on Offband (no TX/RX). Offband's GPS support (#104) probed a pin that doubles as the radio's power-enable on the RAK3401; with no GPS attached it left the radio unpowered, so it couldn't transmit or receive. GPS is now disabled on the RAK3401 companion build until the probe is fixed. (#211)

Which file do I download?

⚠️ ESP32: the app-only *.bin will not boot if flashed at 0x0 — use *-merged.bin for a fresh install. A full erase / "Full Firmware" wipes the device's identity + saved config, so use it only for a first install or recovery, never a routine update.

What's Changed

• docs(#192): Photon-1W (MeshSmith) support design-of-record by @Strycher in https://github.com/OffbandMesh/meshcore-firmware/pull/195
• chore(#197): CLAUDE.md -- record no-upstream-merge policy by @Strycher in https://github.com/OffbandMesh/meshcore-firmware/pull/198
• fix(#89): exclude SerialBLEInterface.cpp from Xiao_S3_WIO USB companion by @Strycher in https://github.com/OffbandMesh/meshcore-firmware/pull/200
• fix(rak3401): companion GPS probe floats WB_IO2, killing the 1W radio (#211) by @Strycher in https://github.com/OffbandMesh/meshcore-firmware/pull/212

Full Changelog: https://github.com/OffbandMesh/meshcore-firmware/compare/offband-v1.1.0...offband-v1.1.1

EastMesh observer-eastmesh firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware v1.16.0.

This release adds the Waev curated broker as a selectable MQTT uplink — with automatic short-lived auth tokens to satisfy Waev's requirements — and widens the Custom MQTT settings panel in the web panel.

What's Changed

• Added the waev curated broker (wss://mqtt.waev.app:443/mqtt) using WSS, verified TLS, and MeshCore JWT authentication with the broker host as the token audience.
• Added get mqtt.waev and set mqtt.waev on|off to toggle the Waev broker, and added Waev to the Primary MQTT and Secondary MQTT dropdowns in the web panel.
• Added per-broker JWT auth token lifetimes; Waev receives a 1-hour token to match its shorter maximum token lifetime, while the other brokers keep the existing lifetime.
• Fixed the web panel so the Custom MQTT settings panel spans the full width of the MQTT Servers card when Custom is selected.
• Updated the README and custom CLI guides for the Waev broker.

Breaking Changes

• None in this release.

If you are upgrading from before 2026.6.4, that release's changes still apply: get mqtt.status switched from per-broker fields to p:/s: broker slots, and saved LetsMesh EU/US selections are cleared once on upgrade.

Notes

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

What's new

• Live Location Sharing — broadcast your position over the mesh as [LOC] messages, movement-gated, to a channel or a single contact. Others who share theirs show up as pins on the map with live distance/bearing in Nearby Nodes, and a status-bar indicator appears while your own share is active. [LOC] is parsed in DMs, channel messages and room messages; DM shares name the sender.
• Locator (geofence) — arm a geofence around a target — a saved waypoint or a person (their live [LOC] or last-known position) — and get an alert when you arrive/leave or they get near/far, with an optional homing beeper that ticks faster the closer you get (and overrides a muted buzzer). Arm it from Tools › Locator or straight from Nearby Nodes / Waypoints; pick the target from a list (favourites first, then any contact), and clear it via a "None" entry. The active target is drawn as a flag on the map.
• One active target across Locator / Navigate / Map — a single "Set as target" action everywhere, backed by a shared resolver that prefers a live [LOC] share over the last-advertised GPS, so the three features always agree on where you're headed.
• Follow live contacts — Navigate to a contact who is live-sharing and the view follows them as they move, adding an ETA line. Quick-share your own position straight from the Map.
• Map & status-bar upgrades — the home mini-map gains a north marker and a scale tick; the status line shows the tracked-node count and, with a fix, an arrow + distance to the nearest tracked contact (e.g. Track:3 →120m); a GPS fix icon sits in the top status bar (boxed once a fix is valid, plain while searching), shown only on GPS boards while GPS is enabled in Settings.
• Trail auto-pause — recording freezes on stops (banking elapsed time and breaking the map line across the idle gap) and resumes on movement without ending the session; the home-screen blink keeps going while paused.
• Collapsible Tools — tools are grouped into fold-in-place Location / Comms / System sections, the same model as Settings (Tools always opens folded to the section list), and the home carousel now uses page-indicator icons instead of dots.
• Waypoint coordinate editor — add a waypoint by scroll-editing its latitude/longitude digit by digit.

Fixes

• Critical — low-heap hang and contact loss on RAM-tight builds. With MAX_CONTACTS=350 and OFFLINE_QUEUE_SIZE=256 the device ran with very little free heap; an allocation in the input/menu path could then fail and hang the UI (notably when entering Diagnostics), and a crash or reset mid-save could wipe all contacts. Fixed by two independent changes:
  • Right-sized message-history rings — the on-device scrollback rings were halved (96→48 channel, 64→32 DM), recovering ~14 KB of free heap (measured 3 → 17 KB). History is RAM-only, so the only cost is shorter on-device scrollback.
  • Atomic persistence — contacts, channels and prefs are now written to a temp file and atomically renamed into place; an interrupted save (crash, reset, full flash) leaves the previous good file intact instead of truncating it.
• USB host stall — Serial.write() is bounded so a stalled USB host can no longer hang the device indefinitely.

Under the hood

• Streaming trail simplification — GPS points are simplified as they're recorded via a fixed-corridor (Reumann–Witkam) pass: straight runs collapse to their two endpoints while curves stay bounded to within the Min dist tolerance of the real track, so the 512-point buffer covers a far longer route than a flat point budget would suggest.
• A UITask-decoupled active-target resolver (resolvePersonPos / activeTargetPos) replaces the duplicated target-resolution logic that lived sepa …

Added

• Manage rooms and channels from the companion app. The companion protocol gained the standard write/action commands the official MeshCore app uses, so things that previously failed against MCLite now work:

  • Room login (CMD_SEND_LOGIN): log into a configured room or repeater from the app. A blank password field uses the password already in the device config, and a wrong password instantly retries with the stored one. Thanks to the reporters (#32).
  • Add / remove channels (CMD_SET_CHANNEL): join a Public, hashtag, or private channel — or remove one — from the app. Adding applies instantly with no reboot — the channel is usable right away and its share QR shows the real key, not zeros, with the session staying connected. Removing a channel still reboots to apply (a known limitation — MeshCore offers no way to remove a channel from the running radio, so the device rebuilds its channel table from config at boot; the app reconnects on its own). Gated by the permissions.conversation_management setting, so a locked-down device still refuses it (#31).
  • Add / edit / remove contacts (CMD_ADD_UPDATE_CONTACT, CMD_REMOVE_CONTACT): add a contact, rename one, or delete one (and its chat history) straight from the app. Adding and renaming apply instantly (the app stays connected); removing reboots to apply (the app reconnects) — see the consistent add/remove model below. Editing maps to the contact's display name; per-contact permission flags stay device-owner settings (the config tool / on-device Admin), and the app's own contact flags remain app-local. Gated by permissions.conversation_management (#33).
  • Share a contact (CMD_SHARE_CONTACT) re-broadcasts a contact's advert so a nearby device can add them, and reboot (CMD_REBOOT) is now honoured from the app's button.
  • The app's Local vs Flood advert buttons were already handled; confirmed during this work. With this, the companion can fully manage rooms, channels, and contacts (#31, #32, #33 all closed). A consistent rule across both contacts and channels: adding and editing apply instantly; removing reboots to apply (the app reconnects on its own). The reboot on removal is required for channels — MeshCore has no way to drop a channel from the running radio — and kept for contacts so the behaviour is uniform and predictable. Live changes are reflected on the device's own UI too — a contact/channel added or renamed from the app shows up in the on-device conversation list and Admin screens right away, no reboot. In-place editing of a contact's permission flags / a channel's settings still arrives alongside on-device editing.

• Change device settings from the companion app. With permissions.settings set to full, a connected app can now set the device name, radio parameters (frequency / spreading factor / bandwidth / coding rate), TX power, the BLE pairing PIN, and the path-hash mode (1/2/3 bytes per hop). Values are range-checked; the device name applies instantly to mesh adverts (the Bluetooth scan name refreshes on the next reboot), while radio / TX / PIN / path-hash save and apply on a quick reboot (the app reconnects). Path-hash mode is especially useful on large meshes — it lets app users match a 3-byte network without hand-editing config.json (see #36). A device left at restricted or none refuses these. Identity keys, advert location (MCLite advertises GPS at the configured precision), and auto-add stay device-managed by design and are rejected.

• Set the region/scope from the companion app. The companion now honours CMD_SET_DEFAULT_FLOOD_SCOPE (set the persi …

Added

• MeshSmith Photon‑1W support — ESP32‑C6 + nRF52 (#193, #194) — vendors MeshSmith's MIT Photon variants (meshsmith_photon_esp32c6, meshsmith_photon_nrf52; Seeed XIAO ESP32‑C6 / XIAO nRF52840 + Ebyte E22‑900M30S 1 W radio) and wires all roles into CI + the release pipeline. ESP32‑C6 needed minimal MeshCore‑consistent base edits (antenna‑switch virtuals, protected _gps_serial, NimBLE dep); nRF52 needed none. Not yet bench‑verified — vendored drivers kept for round‑1; review findings tracked as bench checkpoints on #193/#194.

Fixed

• Xiao_S3_WIO_companion_radio_usb build (#89) — exclude SerialBLEInterface.cpp from the USB companion env (it has no BLE), resolving the NimBLEDevice.h regression from the #288 NimBLE migration.

Changed

• CLAUDE.md: no‑upstream‑merge policy (#197) — Offband does not merge from upstream MeshCore; the upstream remote stays fetch‑only for reference. Keep MeshCore nomenclature/coding‑standard consistency for clean rebasing.

Which file do I download?

⚠️ ESP32: the app-only *.bin will not boot if flashed at 0x0 — use *-merged.bin for a fresh install. A full erase / "Full Firmware" wipes the device's identity + saved config, so use it only for a first install or recovery, never a routine update.

What's Changed

• docs(#192): Photon-1W (MeshSmith) support design-of-record by @Strycher in https://github.com/OffbandMesh/meshcore-firmware/pull/195
• chore(#197): CLAUDE.md -- record no-upstream-merge policy by @Strycher in https://github.com/OffbandMesh/meshcore-firmware/pull/198
• fix(#89): exclude SerialBLEInterface.cpp from Xiao_S3_WIO USB companion by @Strycher in https://github.com/OffbandMesh/meshcore-firmware/pull/200

Full Changelog: https://github.com/OffbandMesh/meshcore-firmware/compare/offband-v1.1.0...offband-v1.2.0-beta1

Added / 新增

• Added support for the T-Echo Lite keyboard kit, including the nRF52 build target, e-paper mono UI adaptation, physical keypad input with EN/123/CN modes, T9-style Chinese candidate input, device I/O settings, 10px Fusion Pixel font support, and TrailMate logo sleep page / 新增 T-Echo Lite 键盘套件支持，包括 nRF52 构建目标、电子纸 mono UI 适配、实体键盘 EN/123/CN 输入、九宫格中文候选输入、设备 I/O 设置、10px Fusion Pixel 字库支持，以及 TrailMate logo 息屏页面
• Added nRF52 MeshCore discover entry points and protocol-aware chat send eligibility, so MC/MT channels and contacts can be browsed across protocol modes while sends stay limited to the active protocol / 新增 nRF52 MeshCore Discover 入口与协议感知的聊天发送资格控制，使 MC/MT 频道和联系人可跨协议查看，但发送仍限制在当前活动协议内
• Added issue #33 support for firmware-provided Emoji input/display candidates and issue #61 support for firmware-provided Symbol candidates, replacing the earlier extension-pack-only route with built-in candidate sets for constrained devices / 针对 issue #33 新增固件内置 Emoji 输入/显示候选支持，并针对 issue #61 新增固件内置 Symbol 候选支持，用内置候选集替代此前仅依赖扩展包的路线，适配受限设备
• Added issue #57 Pager-only main-menu keyboard backlight control, including a bottom Help hint and Help-modal shortcut documentation for adjusting keyboard backlight from the Pager main menu / 针对 issue #57 新增仅限 Pager 的主菜单键盘背光控制，包括底部 Help 提示，以及在 Pager 主菜单 Help 弹窗中说明调节键盘背光的快捷键
• Added the European Cyrillic Extended language bundle with Russian locale coverage, Cyrillic external font coverage, and a Russian Cyrillic keyboard IME; the package remains installable through Extensions with locale, font, and IME metadata in the Pages pack catalog / 新增欧洲西里尔扩展语言包，包含俄语 locale 覆盖、西里尔外部字体覆盖和俄语西里尔键盘输入法；该包仍通过 Extensions 安装，并在 Pages 包目录中保留语言、字体和输入法 metadata
• Added Walkie monitor mode controls and top-bar modulation/listen indicators, including LoRa/FSK modulation badges and a persistent monitor state surfaced outside the Walkie page / 新增对讲机守听模式控制与顶部栏调制/守听状态指示，包括 LoRa/FSK 调制标记，并在对讲机页面之外展示持续守听状态

Changed / 变更

• Moved the protocol runtime closer to the 0.1.30 architecture target by routing MeshCore/Meshtastic UI actions, discover, text send, node actions, position sharing, traceroute/reply handling, and protocol effects through shared runtime/facade boundaries / 按 0.1.30 架构目标继续收敛协议 runtime，将 MeshCore/Meshtastic 的 UI 动作、discover、文本发送、节点动作、位置共享、traceroute/reply 处理和协议 effect 统一路由到共享 runtime/facade 边界
• Reworked ESP shared SPI and storage ownership around a single SdFat/SdFs runtime, retaining the legacy /chat/index.bin plus /chat/*.log chat layout while removing the new /chat_messages.bin bypass and Arduino SD.h/FS.h storage backend paths / 围绕单一 SdFat/SdFs runtime 重做 ESP shared SPI 与存储所有权，保留旧的 /chat/index.bin + /chat/*.log 聊天布局，同时移除新的 /chat_messages.bin 旁路和 Arduino SD.h/FS.h 存储后端路径
• Retired the unused T-LoRa Pager NFC runtime, build dependencies, board facts, power path, and shared-SPI CS participation, because NFC has no active product feature and was verified to interfere with reliable high-speed SD startup on the shared SPI bus / 移除未使用的 T-LoRa Pager NFC runtime、构建依赖、板级事实、电源路径和 shared SPI CS 参与；NFC 当前没有 active 产品功能，并经实机验证会干扰 shared SPI 上高速 SD 启动稳定性
• Refined localization, IME, and language-pack handling for the 0.1.30 UI surface, including external CJK font-pack loading, manual language-load busy overlays, settings/team copy, and keyboard layout descriptor decoupling / 调整 0.1.30 UI 表面的本地化、输入法和语言包处理，包括外部 CJK 字体包加载、语言加载 busy overlay、设置/Team 文案，以及键盘布局描述符解耦
• Updated Team, Contacts, and Nearby presentation to prefer short names and last-seen age semantics instead of online/offline labels where the protocol does not provide a reliable online state / 更新 Team、Contacts 与 Nearby 展示逻辑，在协议没有可靠在线状态时优先展示短名和 last-seen 时间语义，不再使用误导性的 online/offline 标签
• Reworked Pager Walkie layout and input focus behavior so monitor controls no longer trap the rotary encoder as a volume-only control / 调整 Pager 对讲机布局和输入焦点行为，使守听控制不再让滚轮被音量控件单独吞掉
• Updated GitHub Pages release co …

Flash or update at https://flasher.wadamesh.com, or grab it on-device under Settings → About if you're on a normally-flashed board.

New

Heltec V4 Expansion Kit · thanks @samuelcoustet (#29)

If you've got the sensor expansion board on a Heltec V4, there's finally a proper home for it: a dedicated Sensors tab (temperature, humidity, pressure, GPS and battery, each with a small history chart), an environment readout on the Home screen, and an on-device mesh console for poking at the radio directly. None of it shows up on a bare V4 — it only appears when a sensor board is actually detected, so nothing changes for everyone else.

Worth being honest about this one: it was a real grind to land. It came in as a big pull request built against an old beta, so getting it in cleanly meant re-doing most of it by hand against current code and carefully gating every piece so it can't bloat or destabilise the T-Deck and Tanmatsu builds. The original work is @samuelcoustet's — thank you.

European keyboards · thanks @samuelcoustet (#29)

French, Dutch, German, Spanish and Italian layouts, both on-screen and on the T-Deck's physical keyboard. Choose one of those as your interface language and the matching layout is selected automatically.

Wi-Fi updates are back — and you can roll back

On a normally-flashed device (not installed through the Launcher), firmware updates over Wi-Fi return: Settings → About, no cable needed. New this round: Install a previous version — pick one of the last few betas and reinstall it over Wi-Fi, with an "are you sure?" first since it's a downgrade.

Fixed · thanks @tun0

• Closing a dialog no longer lets a scroll carry through to the page behind it (#50).
• The contact action sheet no longer overflows the screen in landscape (#49).
• The per-channel region field now shows your default region as the hint, instead of a generic placeholder (#48).
• The status-bar clock no longer overlaps the node name on the V4.

Everything from beta_15 is included. Thanks to @samuelcoustet and @tun0 for the contributions this round.

OTA: firmware.bin angehängt.

Two new touches, a couple of satisfying fixes, and one sensible default change.

✨ New

• Amber power-save battery — idle power-saving now tints the status-bar battery amber, just like iPhone's Low Power Mode, instead of showing a separate moon icon. (T-Deck)
• @-mention picker — type @ in the message box to pick a contact from a list and drop their name in. Thanks @robinshizuyo-dev (#42).

🩹 Fixed

• Lists stay put — closing a settings item, menu or chat no longer snaps the list back to the top; it stays where you left it. Thanks @ZorkaTheDog (#45).
• App-sent messages appear on the device — a DM sent from the MeshCore companion app now also shows in the right conversation on-screen. Thanks @HonzaDandy (#46).
• Typing reliability (T-Deck / Tanmatsu) — tapping a text field, even one that's already highlighted, starts typing right away, and the accent pop-up no longer interrupts typing outside of chats.
• Cursor cue — the text cursor only appears when a field is actually ready for input, so it's a dependable "you can type now" hint.
• Smoother map panning — tile rendering no longer trips the watchdog and reboots during heavy scrolling.

⚙️ Changed

• Keyboard navigation is now OFF by default. Prefer driving the UI with the trackball / arrow keys? Turn it back on in Settings → Keyboard (your choice sticks until you change it). The Tanmatsu keeps it on, since it has no touchscreen.

Everything from beta_14 is included.

▶️ Flash in the browser: https://flasher.wadamesh.com — or install via the Launcher / on-device update. 🙏

Added

• Companion-API config command (Epic F, #159) — configure a WiFi observer from the MeshCore/Offband app over BLE: WiFi credentials, the full MQTT broker pool (per-slot url / port / transport / auth / JWT claims / CA-cert / topic-prefix / IATA), enable / disable / clear a slot, and display settings. Wholly observer-gated and surfaced behind a new WIFI_OBSERVER_SUPPORT capability bit + FIRMWARE_VER_CODE 14, so stock companions are unaffected. (#160–#169)
• Per-broker live state in the broker read (#172) — each slot now reports its live connection state (connecting / up / backoff / held …) + last-error class, so the app shows whether a broker actually connected, not just that it's enabled.
• Resolved-default hints (#173, #186) — when jwt_owner / iata_override are unset, the read shows the value the device will actually use at connect (its own pubkey / the global IATA) as a placeholder instead of a confusing blank — in both the pool dump and the per-field read.

Changed

• Honest observer config writes (SAFELANE §6, #181) — the config / NVS write path used to silently swallow failures (a broker disable could ACK success while nothing changed). Every writer, the live-reload path, and the crash logger itself now surface + log failures with context. This is what root-caused #179.
• Compact broker config storage + seamless migration (#182) — broker config is stored as small per-key entries (no blank fields) rather than one ~1 KB blob, so writes fit a near-full NVS; a one-time invisible boot migration reclaims space on upgrade, so the operator never sees a transient write error.
• CoreScope (okimesh) default broker → mqtt://mqtt1.okimesh.org:1883 (#170).
• Offband tell in MQTT (#174) — observer nodes append a 📡 to their display name in MQTT payloads, so feeds / maps can flag Offband observers.

Fixed

• #179 — a broker disable ACK'd success while the dump still reported enabled=1. Root-caused as a near-full-NVS write failure the old code lied about; fixed by #181 (honest write) + #182 (storage that fits). Verified on hardware.
• Observer capped at 1 concurrent TLS broker (#171) — a heap guard stops the OOM reboot when a 2nd TLS/wss broker's ~60 KB mbedTLS context exhausts the Heltec V3 heap. Measured on hardware (1 wss ≈ 63 KB free, 2 wss ≈ crash).
• BLE connect survives the client's reconnect-thrash (#178) — a deeper ESP32 BLE frame queue (4 → 12) + stream terminators on reconnect, so a mid-stream reconnect can't leave the app's contact / settings sync hung. Affects companion and observer. (The root — the client's uncapped reconnect retry — is paced client-side in meshcore-client.)
• Crash log reliable for the whole boot (#183) — the 1 Hz heartbeat was flooding the 4 KB RTC crash-ring (wrapped in ~50 s) and evicting real crash diagnostics; the heartbeat now writes the ring every 30 s / on a sharp heap drop, so a post-reboot dump keeps the evidence that explains a crash past boot+50 s.

CI / build

• Heltec T114 (nRF52) companion added to the CI matrix (#185) — first nRF52-companion build coverage (complements the existing RAK4631 repeater).

Which file do I download?

Added

• Companion-API config command (Epic F, #159) — configure a WiFi observer from the MeshCore/Offband app over BLE: WiFi credentials, the full MQTT broker pool (per-slot url / port / transport / auth / JWT claims / CA-cert / topic-prefix / IATA), enable / disable / clear a slot, and display settings. Wholly observer-gated and surfaced behind a new WIFI_OBSERVER_SUPPORT capability bit + FIRMWARE_VER_CODE 14, so stock companions are unaffected. (#160–#169)
• Per-broker live state in the broker read (#172) — each slot now reports its live connection state (connecting / up / backoff / held …) + last-error class, so the app shows whether a broker actually connected, not just that it's enabled.
• Resolved-default hints (#173, #186) — when jwt_owner / iata_override are unset, the read shows the value the device will actually use at connect (its own pubkey / the global IATA) as a placeholder instead of a confusing blank — in both the pool dump and the per-field read.

Changed

• Honest observer config writes (SAFELANE §6, #181) — the config / NVS write path used to silently swallow failures (a broker disable could ACK success while nothing changed). Every writer, the live-reload path, and the crash logger itself now surface + log failures with context. This is what root-caused #179.
• Compact broker config storage + seamless migration (#182) — broker config is stored as small per-key entries (no blank fields) rather than one ~1 KB blob, so writes fit a near-full NVS; a one-time invisible boot migration reclaims space on upgrade, so the operator never sees a transient write error.
• CoreScope (okimesh) default broker → mqtt://mqtt1.okimesh.org:1883 (#170).
• Offband tell in MQTT (#174) — observer nodes append a 📡 to their display name in MQTT payloads, so feeds / maps can flag Offband observers.

Fixed

• #179 — a broker disable ACK'd success while the dump still reported enabled=1. Root-caused as a near-full-NVS write failure the old code lied about; fixed by #181 (honest write) + #182 (storage that fits). Verified on hardware.
• Observer capped at 1 concurrent TLS broker (#171) — a heap guard stops the OOM reboot when a 2nd TLS/wss broker's ~60 KB mbedTLS context exhausts the Heltec V3 heap. Measured on hardware (1 wss ≈ 63 KB free, 2 wss ≈ crash).
• BLE connect survives the client's reconnect-thrash (#178) — a deeper ESP32 BLE frame queue (4 → 12) + stream terminators on reconnect, so a mid-stream reconnect can't leave the app's contact / settings sync hung. Affects companion and observer. (The root — the client's uncapped reconnect retry — is paced client-side in meshcore-client.)
• Crash log reliable for the whole boot (#183) — the 1 Hz heartbeat was flooding the 4 KB RTC crash-ring (wrapped in ~50 s) and evicting real crash diagnostics; the heartbeat now writes the ring every 30 s / on a sharp heap drop, so a post-reboot dump keeps the evidence that explains a crash past boot+50 s.

CI / build

• Heltec T114 (nRF52) companion added to the CI matrix (#185) — first nRF52-companion build coverage (complements the existing RAK4631 repeater).

Which file do I download?

Fixes a beta_13 regression: with keyboard navigation turned off (Settings → Keyboard), the physical keyboard stopped typing into text fields entirely on the T-Deck and Tanmatsu. Typing now works again with keyboard-nav off; with it on, behaviour is unchanged. (The Heltec V4 was never affected — it has no keyboard navigation.)

Everything from beta_13 is included — the community features from @Yazutsu, @tun0, @Vybo and @samuelcoustet (room-post author names, the Direct 0-hop filter, beer emoji / status-bar unread tap / new-contact toast toggle / Czech accents, trackball edge-scroll, and the companion/TCP/OTA fixes) plus the keyboard-nav, special-characters picker and 12-hour-clock work. See the beta_13 notes for the full list and credits. 🙏

▶️ Flash in the browser: https://flasher.wadamesh.com — or install via the Launcher / on-device update.

A big community release: most of the headline features came straight from contributor pull requests, alongside the keyboard, typing and quality-of-life fixes promised after beta_12. Huge thanks to everyone sending PRs, opening issues and reporting bugs — @Yazutsu, @tun0, @Vybo and @samuelcoustet all have their work in this build. 🙏

▶️ Flash in the browser: https://flasher.wadamesh.com — or install via the Launcher / on-device update.

From contributors

Room-server posts show the author — by @Yazutsu (#40, closes #32)

Room-server messages now show the actual poster's name on each bubble instead of the room's own name.

Direct (0-hop) filter — by @tun0 (#39)

A new "Direct (0-hop)" filter for the contact list and the map: show only the nodes you're hearing directly, with no repeater hops in between.

Trackball edge-scroll — by @tun0 (#38)

Optional "edge scroll" — push the trackball cursor past a screen edge to scroll the list underneath it (off by default, under Settings → Keyboard).

Emoji, unread tap, contact toast, Czech accents — by @Vybo (#22)

Beer emoji baked in colour, tap the status-bar unread badge to jump to your Chats, a new "notify on new contact" toggle, and Czech accents in the accent pop-up.

Companion / transport fixes — by @samuelcoustet (#29)

TCP now restarts immediately after off → on, the OTA action is hidden when there's no update slot to use, and a TCP-toggle alert race is fixed. (Cherry-picked from #29; the rest of that PR — the EU keyboards and the Expansion-Kit UI — will follow as focused PRs.)

Typing & keyboard navigation (T-Deck + Tanmatsu)

• Open a chat or channel and the cursor is ready — type straight away. Every other field waits for Enter before it captures the keyboard, so the letter-navigation keys keep working.
• Enter (or Esc / back) on an empty message box drops the cursor and re-selects the field, so you can navigate away with the buttons again.
• The menu-bar letter shortcuts no longer jump you to another page while you're typing.
• New "Show menu-bar letters" setting under Settings → Keyboard (off by default).
• The accent pop-up no longer grabs the keyboard when it appears.

Composer & clock

• New dedicated "Special characters" picker for symbols that aren't on the keyboard (% $ @ # & =, currency, maths, accents) — separate from the emoji picker.
• Long-press one of your sent messages to Resend it.
• The 12-hour clock setting now applies everywhere — top bar, chat bubbles and lock screen — not just the chat list.

Fixes

• Heltec V4: removed the after-crash report prompt — that board has no SD card or reachable storage to save the report to, so it was a dead end. (The T-Deck still offers it.)
• When both Wi-Fi and GPS are off, the clock now sets itself from the timestamps on messages received over the mesh.

Full notes in release-notes/beta_13.txt. Thanks again to all contributors and bug reporters — keep it coming! 🚀

A focused hotfix for the GPS slowdown several of you reported. Everything else from beta_11 is unchanged — this release is GPS-only.

🛰️ GPS fix

On the T-Deck, getting a position fix had gone slow — minutes instead of about a minute — and for some it wouldn't acquire at all. The GPS streams its data over a small serial buffer, and on the busy touch UI a single heavy screen redraw could stall long enough to overflow that buffer and drop the satellite data mid-stream, forcing the receiver to start the fix over. The buffer is now 16× larger, so redraws no longer cost you the fix. Confirmed on-device — acquisition is back to normal.

💬 A note from Kaj

More and more people are picking up wadamesh lately — which is genuinely awesome — and it's surfacing feature requests and bug reports fast, in big numbers. I can't get back to every post in every channel, but I'm on it: I'm prioritising the fixes and quality-of-life improvements, and I'll be working through them later today. Thanks for all the reports and for the patience! 🙏

Install: flasher.wadamesh.com · grab the bins below · update on-device (Settings → check for update) · or via the Launcher store.

EastMesh observer-eastmesh firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware v1.16.0.

This release replaces the retired LetsMesh brokers with the new MeshMapper broker and reworks broker selection into Primary and Secondary slots.

What's Changed

• Added the meshmapper curated broker (wss://mqtt.meshmapper.net:443/mqtt) using WSS, verified TLS, and MeshCore JWT authentication with the broker host as the token audience.
• Added get mqtt.meshmapper and set mqtt.meshmapper on|off to toggle the MeshMapper broker.
• Reworked the web-panel broker section into Primary MQTT and Secondary MQTT dropdowns that enforce the two-broker maximum and reveal the custom host, username, and password fields when Custom is selected.
• Retired the unmaintained LetsMesh EU/US brokers; they remain selectable but are marked retired, and saved selections are cleared once on upgrade so dead brokers stop retrying.
• Shortened get mqtt.status to report the two active broker slots as p:<broker>:<state> and s:<broker>:<state> (for example p:meshmapper:up), keeping the reply within the LoRa text limit.
• Custom MQTT remains username/password only; no JWT/web auth is used for custom brokers.
• Updated the README, web panel, and custom CLI guides for MeshMapper and the Primary/Secondary broker layout.

Breaking Changes

• get mqtt.status output changed from per-broker fields to p:/s: broker slots; update anything that parses the previous format.
• Saved LetsMesh EU/US broker selections are cleared once on upgrade; re-enable a broker such as MeshMapper if you need a second uplink.

Notes

• eastmesh-au remains the recommended MQTT endpoint once mqtt.iata is configured; meshmapper is available as a global second broker.
• 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, etc.). A maximum of two brokers can be enabled at once.
• LetsMesh EU/US are retired but still selectable for legacy use.
• Custom MQTT is available for private broker deployments. 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

v4.11.4 was pulled because migration 033 crashed startup on PostgreSQL and on fresh installs with column "sourceId" does not exist (#3657). v4.11.5 fixes that and carries everything that was in v4.11.4.

If you ran v4.11.4, update to v4.11.5. The boot crash is resolved.

🔴 Hotfix (#3657)

• Migration 033's channel_database backfill is now guarded on the legacy sourceId column existing (it's global-by-design — migration 021 no longer adds it and 063 drops it). Fixes the PostgreSQL / fresh-install boot crash introduced in v4.11.4.

Also included (from the retracted v4.11.4)

Critical

• PostgreSQL boot-loop fix (tables can have at most 1600 columns) (#3639)

Features

• MeshCore role icons in the map + DM node lists (#3647)
• MeshCore favorites pinned to the top of the DM list (#3620)
• Marker spiderfying for overlapping nodes on Map Analysis + Unified maps (#3612)
• Channel "overshadow" warning for same-key/different-name Channel Database entries (#3644)
• Traceroute packetId for cross-source correlation (#3623)

Fixes

• Node disconnects / TX failures since 4.11.x (#3637)
• Custom-LoRa-config primary channel mislabeled "LongFast" (#3644)
• TCP reconnect shows the real per-source address (#3611)
• Fictitious traceroute segments removed; incoming traceroutes visible (#3622)
• MeshCore hashtag #channel secrets over plain HTTP-via-IP + at save time (#3606, #3607)
• MeshCore Last Heard preserved across reconnect (#3645)
• MeshCore new nodes populate fully when heard live (#3646)
• Unified-map neighbor lines follow the merged marker (#3642)
• Adaptive node-type filter per source protocol (#3610)
• Saner single-anchor position-estimate uncertainty (#3616)

🚀 MeshMonitor v4.11.5

📦 Installation

Docker (recommended):

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

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

Flash it: flasher.wadamesh.com (Chrome/Edge, USB) · or pull it on-device via Settings → About → Check for updates · or side-load through the Launcher store.

The headline this round is full keyboard navigation — and every key is hotkey-bindable. This is the foundation for upcoming keyboard-first devices like the Tanmatsu T-Pager that have no touchscreen, and it already gives every T-Deck a fast, reliable way to drive wadamesh entirely from the keyboard.

⌨️ Keyboard navigation (new — on by default)

• Drive the whole UI without the touchscreen: the WASDZ cluster moves the on-screen selection in the actual direction you press (W up, A left, Z down, D right), S selects, Q goes back.
• Each bottom tab has its own hotkey — E Messages, R Contacts, T Home, U Map, I Settings — shown as a small letter on the tab icon. The Home hotkey mirrors tapping Home: press again to flip between Commander and the app drawer.
• New scroll up / down keys (default F / C).
• Everything is remappable — directions, select, back, the per-tab hotkeys, and the scroll keys — under Settings → Keyboard. Toggle the whole feature off there too (the choice persists).
• Cleaner focus: the selected item shows as reverse-video (a bright outline for switches) instead of a coloured border, and the highlight only appears while you're actually navigating with the keys.

🛡️ Stability

• Fixed a reboot that could occur when receiving a message, especially during advert/message floods — a use-after-free while a list rebuilt mid-scroll (#27).
• After a crash, the device now detects it on the next boot and offers to save the crash report so you can send it in — no more digging through Settings.

🗺️ Map

• Map options can now switch the zoom control between the slider and a +/- button pair, like older builds (#26).
• Route replay now opens on a wide overview so you can see where the hops start and the whole path at a glance — and you can pan and zoom freely while it plays.

🏠 Home

• New "App drawer as home" option (in the app drawer's cog) makes the launcher your home screen instead of the Commander view.

🔓 Open source

• The in-progress Tanmatsu (ESP32-P4) port source is now part of the public tree.

Boards: LilyGo T-Deck · Heltec V4 TFT. Use *-merged.bin for a fresh full-flash at 0x0; the plain .bin is the app-only OTA/Launcher image.

• Tic-Tac-Toe: Fennek macht mit 20 % Wahrscheinlichkeit einen zufälligen Zug statt Minimax — der Spieler hat jetzt eine echte Chance zu gewinnen
• Adaptives Polling: Eingabe-Polling drosselt sich nach 3 s Leerlauf von ~100 Hz auf ~30 Hz (spart Core-1-Wachzeit ohne spürbare Latenz)
• Tap-Log-Drossel: Gehaltener Finger flutete Serial-Konsole mit Dauer-Taps — jetzt max. 1 Log-Zeile alle 400 ms
• power::idleMs(): Neue Funktion gibt Millisekunden seit letzter Aktivität zurück

• Auto-reconnect — an optional toggle that automatically retries the last device after an unexpected drop, before the disconnect alarm. Shown only where it can actually work (not for Bluetooth in a mobile browser).
• Nicer packet sound — a pleasant bell whose pitch still tracks signal strength, plus a new "disconnect only" sound mode. The disconnect alarm now sounds on every unexpected drop.

Changed

• Location now starts automatically when you connect (Android) — no need to tap the 3D map's "Enable location" button anymore.
• Steadier location on the 3D map — occasional GPS jumps (sudden ~200 m hops) are filtered out.
• 3D map zooms in to street level even on large maps, and deep zoom is smoother.
• 3D camera framing — "Center on me" no longer jerks at the end of its move, and repeaters are framed with a little headroom above them.

Fixed

• 2D charts could stop updating with Display set to All, until you switched the Display window and back.
• Help (?) tooltips could appear away from their icon.
• Seen Repeaters now shows the true last RSSI/SNR, not a rounded/averaged value.
• Received Packets always lists every repeater as a column, not only the ones on the current page.
• 3D map selection no longer clears itself on its own.
• 3D map tiles no longer flicker while panning or zooming.
• Footer text now has proper contrast in light mode.

• Chat screen header buttons: contact's map, requesting telemetry, and info dialog. by @jason-s13r in https://github.com/laserir/MCLite/pull/30
• Add more radio presets by @jason-s13r in https://github.com/laserir/MCLite/pull/29

Full Changelog: https://github.com/laserir/MCLite/compare/v0.3.9...v0.4.0

What's Changed in v1.12.3

Keyboard LED -- adjustable brightness

The keyboard backlight (toggled by pressing both Shift keys together) was previously fixed at a very dim level, too faint to be useful for some users. A new Keyboard LED setting now lets you choose the brightness.

• Found in Settings, directly below Backlight Brightness.
• Adjustable from 5% to 100% in 5% steps, defaulting to 50% -- noticeably brighter than before.
• The level takes effect the next time you toggle the keyboard backlight on.

Standalone unread counter -- now updates as expected

On standalone builds (no BLE or WiFi companion), the MSG count on the home screen and the unread badges in the channel picker stayed at zero even as messages arrived and displayed normally. The device was effectively behaving as though a companion app were permanently connected, which marks each message as read the instant it arrives.

Standalone builds now track unread messages correctly:

• The home-screen MSG count and per-channel *N badges climb as messages come in.
• Opening a channel clears its unread count, as before.
• The direct-message counter and the new-message screen wake, which were suppressed by the same issue, work again.

BLE and WiFi builds are unaffected -- they already track their real connection state, so on-device counts intentionally stay at zero while the companion app is connected and update once it disconnects.

Only the T-Deck Max build is updated in this release; all other devices remain on v1.12.2.

First-Time Flashing

Each build comes in two forms:

• <name>-merged.bin -- bootloader, partition table, and firmware in a single image. Flash at address 0x0. Use this for a first-time flash, when coming from other firmware, or if a device will not boot after an update.

• <name>.bin -- application firmware only. Use this to update an existing Meck install, including OTA updates from your phone (Settings -> OTA Tools).

The partition layout supports dual OTA slots, so the previous firmware remains on the inactive partition as an automatic rollback target if a new image fails to boot.

MeshCore Companion Apps

BLE variants connect to the standard MeshCore companion apps:

• Web: https://app.meshcore.nz/
• Android: https://play.google.com/store/apps/details?id=com.liamcottle.meshcore.android
• iOS: https://apps.apple.com/us/app/meshcore/id6742354151

WiFi variants connect via TCP on port 5000:

• Web: https://app.meshcore.nz/
• meshcore.js: https://github.com/liamcottle/meshcore.js
• Python CLI: https://github.com/fdlamotte/meshcore-cli

What's new

• Repeater mode — a solo companion can now opt in to relaying mesh traffic, configured from a dedicated Tools › Repeater screen that consolidates the toggle, the forwarding filters, live forwarding stats, and a separate radio profile:
  • Forwarding filters (all flood-only, off by default) — skip-advert (don't re-flood the highest-volume advert traffic), max-hops (drop a flood once it has travelled too far), yield (extra retransmit-delay so a mobile node defers to better-sited fixed repeaters), and min-SNR (don't re-flood marginal fringe packets). Plus overhear suppression, which cancels a queued retransmit if a peer relays the same packet first.
  • Dedicated radio profile — an optional "Custom" Freq/SF/BW/CR used only while relaying, separate from the companion's own network and band-matched to the companion frequency by default. It's applied everywhere a radio change can happen (boot, on-device toggle, app-driven CMD_SET_RADIO_PARAMS, Settings edits) so the device never silently relays on the wrong params.
  • While relaying, Adaptive Power Control is pinned to the ceiling and duty-cycle RX is forced off — a repeater needs to hear and relay at consistent power.
• Radio settings overhaul (Settings › Radio) — 16 community-suggested presets plus manual Freq/SF/BW/CR tuning (digit-by-digit frequency editor), and 4 persisted user preset slots. Presets and the manual editor are now shared between Settings and the Repeater screen — a preset saved from either place shows up in both, and you can save the current profile as a named preset or delete one from either screen.
• On-device Diagnostics (Tools › Diagnostics) — a single scrollable screen showing packet counts by category (RX/TX), radio noise floor / RSSI / SNR, packet-pool free count and outbound queue length, actually-forwarded packet count, uptime, and live heap/stack headroom, with a reset-counters popup.

Fixes

• Channel storage hardening — saveChannels() skips unused (all-zero) slots, so /channels2 holds only configured channels instead of always writing ~2.7 KB; and findChannelIdx() rejects an all-zero secret so a corrupted/empty channel can't match an unused slot and misroute messages.
• e-ink UI scaling — self-sizing popup menu scaled for landscape e-ink (no stray header gap, tighter row tiling); popup menu uses the shared proportional scroll indicator instead of raw ^/v glyphs and stops the selection bar before the scrollbar gutter; compass tape ticks/pointer and trail-map markers scale for e-ink, with wrap-around map navigation.
• Joystick rotation is now persisted on e-ink builds.
• Trail capacity guard — a static_assert fails the build if TrailStore::CAPACITY ever outgrows the uint16_t save-header count, instead of silently truncating.

Under the hood

• Packet pool bumped 16 → 32 so queued retransmits no longer starve incoming-packet allocation while relaying.
• Shared, UITask-decoupled RadioPresetPicker and RadioParamsEditor (plus nearestBwIndex() in RadioPresets.h) replace ~6 duplicated methods and several state fields per screen.
• Mesh Dispatcher gains generic per-payload-type RX/TX counters and pool-free / queue-length getters; a new DeviceDiag helper reports nRF52 heap (linker-symbol + sbrk) and stack (FreeRTOS high-water-mark) headroom.
• build.sh tolerates control characters in pio project config's JSON dump.

What's new

T-Deck input

• Trackball mode — switch the T-Deck trackball between a mouse cursor (the default) and D-pad navigation (roll to move the selection, click to choose), under Settings → Keyboard. Handy if you prefer button-style navigation.

Map — #20

• microSD tiles now fill in as you explore. With Use microSD for tiles on, the device also downloads any missing tiles over Wi-Fi and saves them straight onto the SD card, so your offline library grows instead of showing blank areas past its edge. Thanks @1nerdherder (#20).

Power — by @Vybo (#19)

• Experimental battery saver (idle power-save). Throttles the CPU when the device is parked — screen off, on battery, no app connected and the mesh quiet — to trim idle power use, without ever missing a received packet. Off by default; enable under Settings → System → Battery. (#19)

Settings

• New "Battery" section under Settings → System — opens the battery & power-history screen (the same one you get by tapping the battery icon up top), and is where the battery saver now lives (it moved out of the Lock settings).

🙏 Thanks to Dan Vybiral (@Vybo) for the idle power-save feature (#19) and @1nerdherder for the microSD-tiles report (#20).

Boards: LilyGo T-Deck · Heltec V4 TFT.

• Auto-WLAN-Sync vor Standby (podcast::flushBeforeStandby) auskommentiert — brachte bei jedem Standby das WLAN über den 4-MHz-SD-Bus hoch
• Launcher-Kachel + appmgr-Registrierung + podcast::begin() aus → App vom Gerät verschwunden, Slot 13 (Seite 2) bleibt leer
• Code/Konsolen-Befehle/NVS-Toggle/i18n bewusst behalten (reaktivierbar)

Neues Spiel Sudoku in der Spiele-App (neben 2048, Minensucher, Schach, Tic-Tac-Toe).

• Arduino-freier Generator + Solver (sudoku_core.h, host-getestet): randomisiertes Backtracking für die Vollösung, dann eindeutigkeitsprüfendes Ausgraben — erzeugt nur Rätsel mit genau einer Lösung. Rekursionsfrei (iterativer Level-Stack).
• 9×9-Gitter à 26 px, Touch-Tap/WASD-Cursor, Zifferntasten 1–9 setzen, 0/Backspace/Mikrofon leeren, Konfliktzellen invertiert, „Gelöst"-Overlay mit Zeit.
• Schwierigkeit Leicht/Mittel/Schwer (40/32/26 Vorgaben).
• Beststände im NVS (gelöste Rätsel + Bestzeit), inkl. INI-Export/-Import.

OTA: firmware.bin angehängt.

This release adds a Dead Drop / Mailbox auto-responder — asynchronous "mesh voicemail" where a node can leave a message for another node that need not be online, retrieved later with inbox commands — contributed by new contributor @TheWISPRer. It also brings MeshCore node favoriting (pin any MeshCore node to the top of the list, stored server-side), FEM LNA Mode LoRa configuration surfaced on both the Device Configuration and Remote Admin panels for amplified hardware, and the MeshCore CLI bundled into the Docker image alongside the Meshtastic CLI. On the fixes side, a PostgreSQL/MySQL crash in the MeshCore neighbor query is resolved by widening the neighbor_info timestamp columns to BIGINT (they overflowed signed int32 with millisecond-epoch values), and a proto3 boolean-elision bug that silently re-enabled uplinkEnabled/downlinkEnabled after a container restart is fixed. Position history now captures and displays SNR for directly-heard (0-hop) nodes, the intermittently-blank MeshCore auto-ack {SNR}/{ROUTE} tokens are corrected, mesh-request endpoints return a meaningful 503 (not a generic 500) when the node is disconnected, and the macOS x64 desktop build no longer ships an arm64 re2.node that crashed on Intel Macs. Upgrades are automatic — three idempotent migrations (094–096) run on boot.

Features

• Dead Drop / Mailbox auto-responder — async "mesh voicemail" (#3538, @TheWISPRer) — a fifth auto-responder type. DM msg <name> <text> to leave a message; retrieve with inbox, inbox play [name], inbox delete <id>, inbox clear. Per-source, configured entirely through the Auto Responder UI, messages marked played only on delivery-success, expired rows purged by the maintenance sweep.
• MeshCore node favoriting — pin to top of list (#3595) — favorite any MeshCore node (Companion, Repeater, Room Server, …); stored server-side only (firmware has no native favorite concept), consistent with Meshtastic favorites.
• FEM LNA Mode LoRa configuration (#3600) — surfaces Config.LoRaConfig.fem_lna_mode (Disabled / Enabled / Not Present, firmware ≥ v2.7.20) on both the Device Configuration and Remote Admin LoRa panels.
• MeshCore CLI bundled in the Docker image (#3591) — ships meshcore-cli / meshcli alongside the Meshtastic Python CLI for a complete in-container toolkit.

Bug Fixes

• MeshCore neighbor query crashed on PostgreSQL/MySQL (#3602) — meshcore_neighbor_info.timestamp / .createdAt were 32-bit INTEGER/INT but store millisecond-epoch values that overflow int32; widened to BIGINT (migration 096).
• downlinkEnabled/uplinkEnabled: false reverted to true after restart (#3598) — proto3 elides boolean false, and a ?? true fallback re-inflated user-disabled channel flags on device reconnect; both now default to false.
• Position history dropped SNR for directly-heard (0-hop) nodes (#3593) — SNR is now captured per-fix and shown in the tooltip; the same 0 dB-drop guard was fixed on the central snr_local telemetry path.
• MeshCore auto-ack {SNR} / {ROUTE} tokens intermittently blank (#3592) — buffered SNR/route data is now correlated to the matching packet (freshness + pathLen, consumed once) instead of leaking across messages.
• macOS x64 (Intel) desktop crashed on launch (#3604) — the x64 DMG shipped an arm64 re2.node (ERR_DLOPEN_FAILED); the build now rebuilds re2 from source as x86_64 and backfills the missing CI arch flags.
• Mesh-request endpoints return 503 (not 500) when disconnected (#3597) — /api/traceroute, /api/position/request, /api/nodeinfo/request, /api/neighborinfo/request, /api/telemetry/request now return a meaningful 503 with the v1-API error shape.

Internationalization

• Translations update from Hosted Weblate (#3579, @weblate)

Issues Resolved

• #3587 — Add MeshCore CLI Python application to Docker image
• #3588 — MeshCore node favoriting (pi

…

• battery::external() (DSG-Bit aus BatteryStatus 0x0A) erkennt Netzteil zuverlässig, auch bei vollem Akku (charging() fiel bei Strom ~0 auf false)
• power::poll() nutzt external() statt charging() für die Dateien-Standby-Bremse

• Neues Alarm-Feld once (NVS byte0 Bit4, abwärtskompatibel)
• Einmalige Wecker feuern am nächsten hh:mm tageunabhängig und schalten sich danach selbst aus
• Editor-Preset "Einmalig" im Feld Tage; Liste/Editor zeigen es an
• Konsole: alarm <i> <hh:mm> einmal (once/1x)

OTA: firmware.bin angehängt.

• OTA -104 behoben: GitHub liefert für Release-Assets eine signierte Redirect-URL (release-assets.githubusercontent.com, ~900 Zeichen). Diese sprengte den 300-Byte-Puffer in apply() → abgeschnittene URL → httpUpdate-Fehler -104 (wrong http code). Puffer auf 1400 Byte vergrößert.
• notes_ai (Ollama) Timeout: HTTPClient::setTimeout() nimmt uint16_t (max 65535 ms); der Wert 120000 lief still auf 54464 ms über. Konstante auf 65000 ms korrigiert.

Erstes Release, mit dem OTA von einer früheren Version aus zuverlässig durchläuft.

• Drosselung des Request-Zähler-Voll-Redraws im RUNNING-Zustand von 5 s auf 50 s
• Zähler ist reine Info; seltenere Voll-Redraws sparen sichtbares E-Ink-Flackern

• On-Device-OTA-Knopf (Settings → Update → „Aktualisieren"): prüft GitHub-Releases und flasht direkt am Gerät mit Vollbild-Fortschritt (Phase + Balken + %). Kein Browser/Konsole mehr nötig.
• Notizen: Audionotiz-Player (Play/Pause, ±10 s, Region-Fortschritt) + hoch-scrollbarer Editor.
• Karteikarten: Übersicht mit Leitner-Fächer-Verteilung (fällig/bearbeitet).
• Kopfrechnen: adaptive Schwierigkeit, je-Modus persistierte Stufe.
• notes_ai: behutsamerer Korrektur-Prompt (nur Rechtschreibung/Umlaute, kein Umdichten).
• Tools: maps_tiles.py mit wählbaren Kachelquellen (--preset standard|cyclosm|topo).

OTA-Update

Geräte ab v2.5.1 können direkt am Gerät auf diese Version aktualisieren (Settings → Update → „Aktualisieren") oder via Web-UI (fennek.local) / Konsole (ota update).

Flashen (USB): firmware.bin in den inaktiven OTA-Slot bzw. via pio run -e fennek -t upload.

• Step-wise admin permissions. Beyond the existing security.admin_enabled (global on/off for the Admin screen), a new permissions config block scopes what's reachable inside Admin: permissions.settings (full / restricted / none) — restricted keeps only the basics editable (brightness, auto-dim, dim brightness, keyboard brightness, theme) and shows everything else read-only (no chevron); none makes all settings read-only. permissions.companion (default on) hides the Companion group (WiFi/USB/Bluetooth) when off — configured services still run. permissions.conversation_management (default off) is reserved for a future release (on-device add/edit/remove of contacts/channels/rooms; they stay read-only views for now). All three are provisionable from the config tool. Defaults are fully permissive, so existing configs are unchanged.
• Settings reorganised into per-section screens + Admin is now a pure hub. The on-device Admin screen no longer mixes settings, diagnostics and shortcuts — it's three labelled groups of links: Companion (WiFi / USB / Bluetooth), Conversations (Contacts / Channels / Rooms, read-only views), and Settings (Device, Radio, Display, Messaging, Sound, GPS, Battery, Security). Each section is its own screen mirroring the config tool, with all of its editable settings and its read-only diagnostics in one place (no more duplicated rows across Admin and Device Settings). Newly editable on-device: Radio (region preset picker — EU/UK/CH vs US/Canada — plus a TX-power slider and an advert-interval picker; frequency/SF/BW/CR/scope/path-hash stay read-only), Messaging (history, max-per-chat, location format, retries, telemetry request/badges/auto-refresh, canned messages, allow-mute), and GPS (enable, location-advert precision, timezone, clock offset, last-known max age). Offgrid mode and the live Heard-Adverts count now live at the top of the Radio screen. Each hub link carries an icon (gear for settings; @/#/R for contacts/channels/rooms; Wi-Fi/USB/Bluetooth for companion), and the 3rd-party licenses moved to an About block at the bottom of the hub. Radio/GPS changes reboot once on exit (same batched-save model as theme/language). The old single "Device Settings" screen is superseded by this layout.
• Selectable UI themes. Choose a color palette — Dark (default), Light, Amber (a "military" night mode that preserves night vision), or High contrast — on-device (Admin → Theme, reboots to apply) or via display.theme in config. Custom palettes can be defined under display.themes (start from a built-in base, override any color with #RRGGBB). Default appearance is unchanged. On/off switches now use the theme accent colour too. Thanks @jason-s13r (#24).
• Per-row Info + Map buttons on the Heard Adverts screen. Each heard node now has an explicit info (eye) button that opens its detail dialog, and — when the advert carries a location — a map button that opens the map centered on that node. Back now returns to the Admin screen. Thanks @jason-s13r (#15).
• Map screen pan buttons + windowed chrome. The map gains an on-screen D-pad (up/left/centre/right/down) alongside the existing drag-to-pan. On the T-Deck the map now keeps the status bar visible and uses the standard lv_win header with a back button (the T-Watch stays full-screen). Thanks @jason-s13r (#22, supersedes #20/#21).
• Uptime + last-charged in the Admin Battery section. Shows when the device booted (wall-clock + relative) and when charging last stopped (with the level at the time). Thanks @jason-s13r (#23).
• On-device Device Settings. A new editable settings screen (Admin → Device Settings, behind the existing admin.enabled gate) for changing device n …

• Configuration portal for Companion, Repeater, and Room Server — configure, back up, restore, and update firmware without the CLI. (ESP32 devices only)

  Open it the same way as before — start ota in the CLI, or Start OTA from the companion Settings menu. Previously this landed on a firmware-only upload page; it now opens the full configuration portal where you can configure, back up, restore, flash firmware, and reboot — all from one page in the browser.

  The companion backup covers custom preferences (Quick Send presets, saved locations, channel hop limits, display settings, WiFi credentials,...) that upstream MeshCore doesn't have — handy when moving to a new device. For the Repeater and Room Server, this is the first time backup and restore are available at all — no more re-entering everything from scratch after a node failure or hardware swap.

  The portal is password-protected. Companion: set one with set portal.password in the CLI. Repeater / Room Server: the existing admin password is used automatically.

  The backup format is compatible with the official MeshCore app — upstream preferences in the backup can be restored by the app. Passwords are never written to backup files.

• Config portal AP: open network, login page, 1-client limit, 10-minute idle auto-shutdown.

  The WiFi AP is open (no AP password); access is gated by a browser login page using the portal password described above. Only one device can associate with the AP at a time. If no device connects within 10 minutes of the AP opening, it shuts down automatically.

  

• Fix: full-flash (_merged.bin) images for Vision Master E213 and E290 were built with the wrong flash size.

  Both boards have 16 MB of flash, but their merged full-flash images were generated with an 8 MB flash-size header. The pre-merged images are now built with the correct 16 MB size. If you previously flashed an E213 or E290 using a _merged.bin, re-flash with the corrected image. OTA (.bin) updates were not affected.

• Feature: Per-message + analyzer region tag support
• Feature: Sortable neighbor list in repeater pane
• Feature: Option to disable autoscroll on packet feed
• Feature: Bot globals
• Feature: Add draft support for Open gifs + reactions
• Bugfix: Use correct last-heard time for repeater recency
• Bugfix: Configurable VAPID subject for iOS web push
• Misc: Library updates, logging, test

4.11.1 fails to boot on PostgreSQL/MySQL backends that have an existing Auto-Acknowledge configuration. Migration 093 (the Auto-Acknowledge 2×2 matrix backfill) inserted settings rows without the table's NOT NULL createdAt/updatedAt columns, aborting database initialization with null value in column "createdAt" … violates not-null constraint — a restart loop. On SQLite the violation was silently swallowed, so the matrix settings were never written.

Fixed

• Migration 093 now supplies createdAt/updatedAt in all three backends (SQLite / PostgreSQL / MySQL). A regression test runs the migration against a real settings table.

Recovery

Affected instances recover automatically on upgrade to 4.11.2 — migration 093 was never marked complete (it threw before committing), so it re-runs and now succeeds, correctly migrating your auto-ack settings. No manual database changes are required.

Full changelog: see CHANGELOG.md → [4.11.2].

🚀 MeshMonitor v4.11.2

📦 Installation

Docker (recommended):

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

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

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 the manifest at webflasher/manifest.json with esptool.js.

What's Changed

• fix: scope radio param force-override to dedicated debug flag by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/626
• [codex] docs: remove completed roadmap items by @gadgethd in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/638
• fix: bug sweep — display init, GPS baud timeout, DM name buffer, channel routing, save counter overflow by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/641
• [codex] ci: serialize release asset uploads by @gadgethd in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/640
• T13: SD lazy retry — single attempt at boot, retry on demand by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/642
• fix: QIO→DIO flash mode for PSRAM compatibility + CI smoke matrix expansion by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/662
• fix: HAL — battery Li-ion lookup, trackball LEFT deadtime, BLE state ordering by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/664
• fix: mesh — static sender buffer race + path discovery race by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/665
• fix: UI — chart data, nav stack, trace timer, brightness, search state by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/666
• fix: reset cache_clock on map reinit (#661) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/667
• fix: SPIFFS flush before device reset + NVS write dedup in radio setup by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/663
• fix: roomserver double-send + UTF-8 emoji truncation by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/668
• fix: free outgoing screen on navigation to stop LVGL pool leak / freeze (#670) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/671
• fix: theme change refreshes current screen immediately (#654) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/669
• fix: null guard getRTCClock() in updateSignalSample (fixes #675) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/676
• docs: correct HARDWARE.md inaccuracies and fix touch comment (fixes #679) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/680
• fix: add missing P_LORA_* build flags for MeshCore visibility (fixes #677) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/681
• chore: update MeshCore submodule to latest dev (fixes #678) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/682
• ci: add debug and remote_test_radio builds to PR matrix by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/684
• fix: restore Settings back navigation by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/674
• fix: resolve Launcher warm-handoff freeze + settings crash by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/685
• fix: chat channel-state corruption + harden WiFi OTA auth by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/689
• fix: SPIFFS warning spam (#683) + navigation hang (#672) by @hermes-gadget in https://github.com/hermes-gadget/SigurdOS-tdeck/pull/690

Full Changelog: https://github.com/ …

Features

• Device notifications surfaced as toasts + firmware 2.8 favorite/ignore cap handling (#3548): MeshMonitor now shows ClientNotification messages the connected node emits about its own operation — duplicate-key security warnings, invalid-config errors, duty-cycle limits, and more — as top-right toasts. These were always sent by the node but previously decoded and dropped. A server-side policy (clientNotificationPolicy.ts) suppresses the routine recurring ones (e.g. the power-saving "sleeping for N interval" message) and dedupes identical messages to at most once per minute per source, so the feed stays useful rather than noisy. On firmware 2.8, when a Set Favorite / Ignore is refused because the device's protected-node list is full, MeshMonitor reverts its optimistic star/ignore toggle to match the device and surfaces the refusal (this warning is only emitted for the locally-connected node, not remote-admin targets). No protobuf changes were needed — the 2.8 NodeDB warm-tier restructure and the snr_q4 on-disk field do not affect the over-the-air wire MeshMonitor reads (SNR stays a float in dB; a regression test guards this). See docs/internal/dev-notes/MT28_NODEDB_SUPPORT_PLAN.md.

• Auto-Acknowledge 2×2 matrix — message type × hop distance (discussion #3564): Auto-Acknowledge previously tangled two concepts — its "Direct" toggles actually meant 0 hops (not direct messages), tapback/reply were keyed only on hop distance (shared across channel & DM), and a single global "Respond via DM" applied everywhere. It's now a clean {Channel, Direct} × {0-hop, Multi-hop} matrix: each of the four cells independently configures Message (reply), Tapback (emoji reaction), and Respond via DM. "Respond via DM" applies to the reply only (tapback-via-DM is unreliable) and is disabled until Message is enabled; for Direct cells, replies are inherently DMs. Existing configurations are migrated automatically (migration 093) so behavior is preserved on upgrade. MeshCore auto-ack is unchanged.

• MeshCore node-type icons & filter on the source map (#3546, #3576): The per-source MeshCore map now renders role-based marker glyphs by advert type — Repeater (tower), Room Server (server rack), Sensor (broadcast), Companion (person) — instead of the generic "MC" badge (kept as the fallback for standard/unknown nodes). The Map Features panel gains a Node Types filter (per-category checkboxes, persisted) to show/hide markers by role, and the legend gains a matching Node Types section when shown. This brings the MeshCore source map to parity with the Map Analysis workspace. The shared map legend opts into the new section via a showNodeTypes prop, so the Meshtastic maps are unchanged.

🚀 MeshMonitor v4.11.1

📦 Installation

Docker (recommended):

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

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

• OTA: Semver-Vergleich für Update-Erkennung (tag_name != FENNEK_VERSION → korrekte Versionslogik)
• Akku: Batterieanzeige-Fix in der Statuszeile

Flashen

pio run -e fennek -t upload

oder OTA via fennek.local → Firmware-Update.

A reliability-focused drop — Wi-Fi recovery, a self-healing chat-history fix, crash-report export, plus room-server, map, contacts and app-drawer improvements.

Install / update: flash from flasher.wadamesh.com, grab it in LauncherHub, or use the on-device update check (Settings → About).

Stability

• Wi-Fi now reconnects on its own after the link drops — no more rebooting to get back online.
• Fixed reboot-on-every-received-message: a corrupted chat-history file could make the device reboot whenever a message arrived (and hide your messages). The bad file is now detected and reset automatically, so it recovers on its own.
• Boot hardening: NULL-guards on the display draw buffer so a unit with quirky/limited memory degrades gracefully instead of getting stuck on the boot logo.

Crash reports

• After a crash, Settings → About shows an "Export crash report" button that saves the crash dump to the microSD card — so you can send it to the devs and get the bug fixed.

Chat & room servers

• Room-server messages now show the time each message was actually sent, not when it arrived.
• Room-server messages now show who sent them.
• Sharing your contact QR now produces a valid meshcore://contact/add?… code that the MeshCore phone app can scan and import.
• Unread counts show "99+" instead of an alarming raw number on busy channels.

Map

• The reload button for corrupt tiles now actually clears the cached tiles — including when you're offline — and the missing/blank "twilight zone" tiles re-download on their own.
• Fixed tiles not re-fetching at zoom levels 13–15.

Contacts

• Favourited contacts always appear in the contact list now, even with hundreds of similarly-named contacts (they used to stay hidden until you searched).

App drawer

• New icon-size setting — tap the cog at the top-right of the app drawer to switch between Compact and Large (bigger icons + labels, easier to read).
• Smoother scrolling through the app list and the other scrollable lists.

Assets: *-merged.bin = full image (flash at 0x0 / erase). Plain *.bin = app-only (OTA / Launcher side-load). T-Deck = wadamesh-tdeck*, Heltec V4 TFT = wadamesh-heltec-v4-tft*.

✨ Features

• MeshCore virtual node — connect the MeshCore app over WiFi (#3540, #3535) — expose a managed MeshCore device as a virtual node the MeshCore app connects to over TCP/WiFi (default port 5000, per-source enablement, admin commands blocked by default, private-key export always blocked).
• MeshCore: define a contact's forwarding path by repeater name (#3550) — first-class, name-aware path editor, on by default.
• MeshCore node-type icons + map filtering (#3563, #3546) — role-based markers (repeater / room server / sensor / companion) and a Node Types filter with legend.
• Per-node "Hide from Map" toggle (#3565, #3549) — suppress a node's map marker everywhere while keeping it visible in lists, DMs, and the packet monitor.
• Node list export — CSV / HTML (#3537, #3499) — export the Nodes view (respecting current filters/sort) for mesh upgrade planning.
• Telemetry time-range selector in Node Details (#3530) — 15m–7d range buttons on the Node Details graphs, persisted and shared with Device Info.
• Position-history map: a marker at every fix, points-only mode, hover tooltip (#3495, #3492).
• Newer AirQualityMetrics fields wired up (#3517, #3507) — particles_40um, pm40_standard, formaldehyde trio, and PM-sensor extras now graphed.
• Native OIDC group → role mapping (#3489, #3485) — map IdP groups to admin/login via OIDC_GROUPS_CLAIM / OIDC_ADMIN_GROUPS / OIDC_ALLOWED_GROUPS.
• UI tweaks + map unification pass (#3561, #3557) — "Messages" → "Node Details" nav, clickable map-popup source rows, unified tile/legend/GeoJSON toggles, and more.

🐛 Bug Fixes

• Offline nodes kept appearing "recently heard" from replayed packets (#3569) — new replay guard ignores stale lastHeard refreshes from retained/replayed MQTT frames.
• NodeInfo could overwrite high-precision positions with lower-precision ones (#3516, #3513) — precision-downgrade guard added.
• User-supplied regexes hardened against ReDoS (#3544) — all user/admin regexes now compiled with RE2 (resolves 4 CodeQL alerts).
• Traceroute History mixed in rows from every source (#3566) — history now scoped to the active source.
• Map "Show Neighbor Info" disagreed with the Map Analysis Neighbors view (#3560) — freshness filters aligned.
• Per-node position override ignored on the multi-source dashboard map (#3559, #3551).
• SaveBar only saved the active section (#3558, #3552) — grouped sections now save together via "Save All".
• MeshCore DM contact list nearly empty while node/map view was full (#3554) — in-memory contacts seeded from the durable DB rows on connect.
• MeshCore node list intermittently collapsed to a single node (#3539).
• Link previews failed to load on MeshCore / first page visited (#3541) — swi …

• ci: prune old untagged GHCR package versions by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/256
• Add optional PostgreSQL backend (v0.14.0) by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/243
• Added migrate service to overlay network by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/259
• chore(deps): update postgres docker tag to v18 by @renovate[bot] in https://github.com/ipnet-mesh/meshcore-hub/pull/258
• Reverted to Postgres 17 by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/260
• fix: sink NULL last_seen nodes to bottom of node list by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/263
• fix: normalize date-bucket keys for Postgres dashboard charts by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/264
• fix: normalize packets feature flag check to !== false by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/265
• Added explicit pull policies for core services by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/266
• fix: ensure CI required checks run on all PRs by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/268
• docs: tidy database docs and deprecate SQLite by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/267
• chore(deps): update anomalyco/opencode action to v1.17.8 by @renovate[bot] in https://github.com/ipnet-mesh/meshcore-hub/pull/269
• docs: centralise env vars and split deployment/observer/maintenance docs by @jinglemansweep in https://github.com/ipnet-mesh/meshcore-hub/pull/271

Full Changelog: https://github.com/ipnet-mesh/meshcore-hub/compare/v0.13.4...v0.14.0

• Sprachnotiz-Liste zeigt jetzt Datum + HH:MM (statt HH:MM:SS bzw. generisch „Sprachnotiz").
• Aufnahme-Gain ×6 mit Sättigung: das PDM-Mikro war ~−20 dBFS leise → Wiedergabe kaum hörbar. Neue Aufnahmen sitzen bei ~−7 dBFS (kein Clipping).
• Sauberer I2S0-Handover nach der Aufnahme: kein doppeltes i2s_driver_uninstall mehr (endMic/MicResume macht uninstall+install in einem Schritt).

Karten / GPS

• No-Fix-Fallback zentriert jetzt auf Düsseldorf (51.2277/6.7735); DEFAULT_ZOOM 15 → 13 (NRW-weit bekachelt).
• GPS-Zeit-Diagnose: Einmal-Log [MAPS] GPS-Zeit empfangen … pro Karten-Session.

Enthält außerdem v2.3.0 (GPS-/WAV-Diagnose-Logs, Karten-Fallback, Notizen-Zeitlabel).

Polish + fixes for the touch UI — a faster chat acknowledgement, map readout controls, and an internal-memory trim.

Install / update: flash from flasher.wadamesh.com, grab it in LauncherHub, or use the on-device update check (Settings → About).

Chat

• Quick replies insert at the cursor instead of replacing whatever you'd already typed.
• New one-tap "Ack" — long-press any message and tap Ack. It drops a ready-to-send reply into the composer with that message's signal strength (SNR/RSSI) and the route it took (hop codes), so you can instantly confirm someone's test came through. On a channel it @-mentions the sender. You review and send — it's never auto-sent.
• Fixed the message action menu (Ack / Copy / Info / Mention / Block) running off the bottom of the screen — it now fits, and scrolls if it ever needs to.

Map

• The zoom button now shows a clear "+/-" icon.
• Show or hide each on-map readout independently in Map settings — the coordinates line, the tile x/y/z line, and the contact markers.
• Map settings reorganised: the microSD-tiles switch sits at the top under its own heading, separated from the new visibility toggles.
• New auto-refresh button — turn it on and the map re-centres on you automatically whenever your position changes, with an on-screen Auto-refresh on/off confirmation.
• Fixed the close (X) in Map settings overlapping the switches when the panel was scrolled.

Performance

• Reclaimed ~19 KB of internal RAM (scratch buffers moved to PSRAM), leaving more headroom for Wi-Fi and trimming the idle-memory growth seen in recent betas.

Assets: *-merged.bin = full image (flash at 0x0 / erase). Plain *.bin = app-only (OTA / Launcher side-load). T-Deck = wadamesh-tdeck*, Heltec V4 TFT = wadamesh-heltec-v4-tft*.

(re-re-re-release(last time I swear) with the "smearing fix on eink after the full update" and "automount error on a freshly formatted node")

[!IMPORTANT]

Before you upgrade

Updating from v1.16.2 — clean flash, no re-bond required, bonds survive.

Updating from v1.16.1 or older — flash the firmware; the firmware detects the old installation on first boot and clears the BLE bond storage automatically. Your identity, contacts, channels, and prefs are preserved. You will need to re-bond your phone/desktop once (old pairings were stored in a different location that v1.16.2 moved away from). No formatter tool required.

Coming from Arduino MeshCore — flash the firmware; it detects the incompatible filesystem on first boot and formats automatically. Everything starts fresh (new identity, clean storage). No formatter tool required.

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

This is a GPS-focused release: it stops a battery-killing bug on GPS trackers, puts the GPS duty cycle under your control, and follows up the v1.16.2 ESP32 pairing work with a fix for recent Android phones.

Highlights

Fixed: ThinkNode M1 draining its battery in a day

On the ThinkNode M1, the GPS module was never actually powered down between fixes — the reset line was mislabeled in the board definition and held permanently released, so the receiver kept drawing current even when the firmware thought it was asleep. A full battery could disappear in roughly a day with GPS enabled.

The M1 now asserts the GPS hardware reset on standby, so the GPS genuinely stops between fixes. If you run an M1 with GPS on, this is the fix you want.

New: configurable GPS duty cycle — set gps duty <seconds>

You can now decide how your node handles GPS, instead of it being baked in:

• set gps duty <seconds> — how long the GPS sleeps between fixes. Persists to flash and applies immediately.
• set gps duty 0 — always-on: the GPS never sleeps. It streams fresh fixes (so telemetry is always current) and stays on long enough to download a full almanac.
• set gps duty default — reset to the role default.
• get gps duty — show the now-effective interval.

This unifies repeaters and companions behind one knob. Repeaters default to 48 h (GPS wakes only for periodic time-sync) and companions to 5 minutes — both now adjustable. Existing repeaters are migrated automatically; nothing to do.

Bad input is rejected with a usage hint, and the value is clamped to a sane range (10 s … 1 week, or 0 for always-on).

Fixed: GPS no longer pins itself on waiting for a first fix

Previously, after enabling GPS a companion would keep the receiver powered indefinitely until it got its first fix — so a node left somewhere without sky view (indoors, in a bag) could quietly drain its battery forever. The first cold-start acquisition is now bounded (5 minutes by default, enough for a genuine cold start), after which the node drops into its normal duty cycle whether or not it got a fix.

Fixed: ESP32 Secure Connections pairing (Pixel 7 / recent Android)

Following the v1.16.2 ESP32 pairing fix, SC-capable centrals — notably recent Android phones like the Pixel 7 — still failed to bond: the controller's encryption table was left uninitialized because the relevant code was guarded on an ESP-IDF symbol that never exists in a Zephyr build, so the link dropped with a MIC failure at encryption start. The guard is corrected (carried as a managed hal_espressif patch), and SC pairing now completes. Legacy-pairing devices were unaffected and continue to work. Thanks @seagull9000.

Other fixes and improvements

• Fixed: GPS always-on on a freshly flashed companion — a new install would default gps_interval to 0 (always-on) instead of the intended 5-minute duty cycle, causing the …