Dan Vybiral
96dffaef58
Two bugs in the manual telemetry request path (the Request button in the telemetry window): 1. Usually only the second request succeeded. The guest LOGIN and the telemetry REQ were sent back-to-back, but a repeater drops a REQ from a sender it hasn't added to its ACL yet, and the ACL entry isn't committed by the time the first REQ is processed — so the first request got no reply and the user had to tap twice. Defer the REQ: uiSendRequestAfterGuestLogin() sends only the guest LOGIN and fires the REQ from onContactResponse once the LOGIN-OK arrives, by which point we're in the repeater's ACL and a direct out_path has been learned, so it lands on the first try. Also adds a single-flight guard on telemetryRequestNow(), holds auto-poll while a manual request is pending (so it can't clobber the pending reply tag), and disarms the deferred login on timeout so a late LOGIN-OK can't fire a stale REQ. 2. The status-bar async spinner only blinked for ~1.5s on a telemetry request (the markMeshRequest window) then froze, instead of blinking for the whole pending window like a status ping. Its active predicate watched the ping deadline but not the telemetry timers; OR in the telemetry pending state. Auto-poll's best-effort chained send and the admin-console login path are left unchanged.
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
- LilyGo T-Deck / T-Deck Plus — env
LilyGo_TDeck_companion_radio_touch - Heltec V4 + TFT + CHSC6x touch — env
heltec_v4_tft_companion_radio_usb_tcp_touch
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.