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 and Heltec V4 + TFT (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.
A fork of ALLFATHER-BV/wadamesh built on
beta_46 that adds some additional tools on top of the base touch UI. Everything else
(chat, map, contacts, channels, settings) is unchanged from beta_46.
New
- Packets — live per-frame RX list (type, route, hops, size, RSSI/SNR, colour-graded). Tap a frame to decode it: path resolved to contact names, per-type payload (channel plaintext where you hold the key, advert name/type/position/clock-skew, trace hop SNRs), link margin, airtime, raw hex.
- Floods — a Packets/Floods toggle grouping the capture ring by payload, so flood rebroadcasts collapse into one row: copies, hop spread, best signal.
- Heard — one row per node whose advert you've received, with signal, type, hops, age, and distance + bearing.
- Discover — active zero-hop scan; lists who answers with uplink SNR (how they heard you) and downlink RSSI (how you heard them). Answering nodes are auto-added to contacts and named from adverts. Rate-limited to respect repeater discovery budgets.
- Neighbours (repeater sheet) — ask a repeater what it hears at its own antenna.
- Get name (contact sheet) — pull a node's advertised name on demand, so a hex-placeholder contact gets its real name without waiting for its next advert.
Fixed
- Adverts whose path uses multi-byte hashes are no longer dropped:
path_lenis an encoded byte (hop count + hash size), not a length — misreading it silently discarded multi-hop adverts from the recent-heard table and the Discovered list. Now decoded correctly.
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 - Elecrow ThinkNode M9 — env
ThinkNode_M9_companion_radio_touch(beta) - RAK WisMesh Tap V2 (RAK3312) — env
rak_tap_v2_companion_radio_touch(beta)
This repo holds only the app: the companion_radio glue, the ui-touch
LVGL UI, the two boards' 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.
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 bothFlash 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.
Contributions are welcome — see CONTRIBUTING.md. One topic per PR; inbound contributions are accepted under the project's GPL-3.0 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.