Kaj SchittecatandClaude Opus 4.8
cac3a44074
'Remove channel' was built by mk_full(), a local row helper my scanner did not know about. Listing the functions that take UI text has the same blind spot as grepping for the strings themselves: the one helper nobody wrote down keeps its labels English forever. So the scanner gained a --wide mode that inverts the question — every prose literal in the file is suspect unless it is consumed by a known NON-UI sink (logging, strcmp, paths, Lua glue, format-only args). That surfaced the whole family of local builders: mk_full, mk_btn, mk_label, mk_ta, mk_switch, setupHeader, setupBtn, fmActionBtn, ccToggle, make_launcher, setAddChannelError. --fix now wraps prose in ANY argument of those helpers rather than a hardcoded index, so their differing signatures don't matter. 103 calls wrapped: the channel sheet (Remove channel, Delete chat), every contact action (Open chat, Ping, Message, Telemetry, Trace SNR, Admin, Range test, Sightline, Block, Favorite, Reset path), the Profile/Radio settings rows, auto-add and experimental switches, the add/join channel menu and its errors, file-manager actions, control-center chips, the launcher tiles and the whole first-boot wizard. 40 new keys translated in all 13 languages; units and protocol tokens (MHz, SF, CR, TX, AF, BT, GPS, DND, Wi-Fi) map to themselves. Files at ver 7, both tools green. Co-Authored-By: Claude Opus 4.8 <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 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.
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 - Elecrow ThinkNode M9 — env
ThinkNode_M9_companion_radio_touch(beta) - RAK WisMesh Tap V2 (RAK3312) — env
rak_tap_v2_companion_radio_touch(beta)
Architecture
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.
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.