Michael A. CojocariandClaude Opus 5
dee32e4c2c
The other half of the request. The previous commit made a scoped message resolvable to a region NAME; this is the list that decides which names are on offer. Until now the registry only filled itself from our own default region and per-channel scope overrides, so a region you can see traffic from but do not participate in could never be named -- which is most of them. Settings -> Radio, under the region-scope field, opens "Known regions": a field plus Add, and a row per region with Remove. Deliberately placed next to the region we SEND under, because the distinction is the confusing part -- that field is the region we transmit in, this list is the regions we can RECOGNISE, and a region only has to be named to be recognised, since its key is SHA256 of that name. You do not need to be in a region to identify its traffic. Remove is a RETIRE, not a delete. The slot and name stay bound; the region simply stops being matched from that point on. Freeing the slot for reuse would hand it to the next region added and silently relabel every message already received under the old one -- the exact failure #271 warned about, and the reason slots were never list indices. Re-adding a retired region revives its original slot, so its old and new messages stay one region rather than splitting in two. The persisted slot file gains an active mask and a magic bump (RGS1 -> RGS2). An RGS1 file still loads, with every assigned slot treated as live, which is what it meant before the mask existed. Two failures are reported rather than silently doing nothing: the list being full (all 14 slot bindings used, retired ones included -- they are permanent), and a name that canonicalises to nothing, like blank or a bare "#". Not board-gated -- the page uses the standard app-page chrome, so it inherits the tall title bar, the back chevron and focus-group navigation on the keyboard-only boards the same way Blocked users does. Laid out and reasoned about on the T-Deck for now; the short-panel boards want a look on real glass before anyone calls it done there. The page title is untranslated, matching every other app page here (Blocked users, Spectrum, Discover). All 8 S3 envs build. Four new strings in 13 .lang files, English both sides per 4709c81; the audit's 3 remaining gaps are pre-existing on main from the beta_68 SDK work. Not hardware-tested: adding a region is verifiable on-device, but whether a message then resolves to it needs real scoped traffic from a second node. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A real touchscreen UI for your mesh radio. · open source · GPL-3.0
Touch-UI MeshCore companion-radio firmware for the LilyGo T-Deck / T-Deck Plus, Heltec V4 + TFT and eight other boards (ESP32-S3).
An LVGL touch UI — map, chat, contacts, channels, settings — split out of
meshcomod. The app depends on a
MeshCore fork via PlatformIO lib_deps.
Boards
See DEVICES.md for the full support matrix, install paths and per-board status.
- LilyGo T-Deck / T-Deck Plus — env
LilyGo_TDeck_companion_radio_touch(stable) - Heltec V4 + TFT + CHSC6x touch — env
heltec_v4_tft_companion_radio_usb_tcp_touch(stable) - Tanmatsu (ESP32-P4) — built from
tanmatsu/(ESP-IDF), ships via the Tanmatsu app store — sideload guide for running your own build - Elecrow ThinkNode M9 — env
ThinkNode_M9_companion_radio_touch(beta) — keyboard & d-pad guide - RAK WisMesh Tap V2 (RAK3312) — env
rak_tap_v2_companion_radio_touch(beta) - LilyGo T-Lora Pager — envs
tlora_pager_lr1121_companion_radio_touch/tlora_pager_sx1262_companion_radio_touch(stable) — keyboard shortcuts - Heltec V4-R8 + Expansion Kit V2 — env
heltec_v4_r8_tft_companion_radio_usb_tcp_touch(stable) - LilyGo T-Display P4 — built from
tdisplay_p4/(ESP-IDF); AMOLED by default,WADA_P4_LCD=1for the TFT-LCD SKU - Attaky Mesh Series — env
attaky_mesh_series_companion_radio_touch(beta)
Architecture
This repo holds only the app: the companion_radio glue, the ui-touch
LVGL UI, each board's glue/variants, and platformio.ini. The MeshCore
core is not vendored here — it's pulled as a library via lib_deps from the
ALLFATHER-BV/meshcomod monorepo
(the same repo as the non-touch firmware), pinned by a lean source-only core-*
git tag. The touch-app files this repo owns (TouchPrefsStore, WifiRuntimeStore,
the transports, …) are dropped from the lib via -DMC_VENDORED_TOUCH_APP so they
aren't compiled twice. The build is byte-identical to the original in-tree
meshcomod firmware.
Build
PlatformIO pulls the core fork and all libraries automatically:
pio run -e heltec_v4_tft_companion_radio_usb_tcp_touch # Heltec V4 TFT
pio run -e LilyGo_TDeck_companion_radio_touch # LilyGo T-Deck
# or just `pio run` to build both
Flash with the NVS-preserving 4-component chain (bootloader / partitions /
boot_app0 / firmware at 0x0 / 0x8000 / 0xe000 / 0x10000) so saved Wi-Fi
credentials survive — not a merged image, which 0xFF-pads and wipes NVS.
Contributing
Contributions are welcome — see CONTRIBUTING.md. One topic per PR; inbound contributions are accepted under the project's GPL-3.0 license.
License
GPL-3.0-or-later — see LICENSE. wadamesh is copyleft: anyone who distributes a build or a fork must also make their source available under the GPL. This keeps the UI open and concentrates community effort instead of fragmenting it into closed forks.
wadamesh incorporates and depends on MeshCore (MIT, © Scott Powell / rippleradios.com) and other third-party components — see NOTICE for the full list and their licenses. MeshCore-derived files keep their MIT notices; the combined work is distributed under the GPL (MIT is GPL-compatible). The MeshCore fork that wadamesh builds against stays MIT on purpose, so its Wi-Fi/BLE hooks remain upstreamable to MeshCore.