Kaj SchittecatandClaude Opus 5
b014865ada
Requested by janmashat: sharing position currently means putting it in the advert, which broadcasts it in the clear to every node in range, forever — poor privacy for something as sensitive as where you are. Almost all of the alternative was already built and unreachable. MeshCore answers telemetry on REQUEST, encrypted to the contact that asked, with three independent permission categories (battery, location, environment) each of which can be denied, allowed for everyone, or allowed only for contacts carrying a permission bit in contact.flags. The GPS emitter exists (EnvironmentSensorManager::querySensors adds LPP GPS when the requester has TELEM_PERM_LOCATION), and the receiving end has worked since #27 — an LPP_GPS field in a response is persisted with uiSetContactGps and the contact appears on the map. The one missing piece was any way to grant it: nothing in the touch UI ever wrote telemetry_mode_loc, so location telemetry was permanently denied, and the per-contact ALLOW_FLAGS mode was unreachable because nothing set those bits. The existing switch is all-or-nothing over battery+environment only, with a comment noting location "keeps its own separate setting" — a setting that was never built. So: Settings > Mesh gains "Share my location when asked" (Never / Chosen contacts only / Anyone who asks, ordered to match TELEM_MODE_*), and a contact's own menu gains "Share my loc", which sets that contact's location bit and flips to the per-contact mode if sharing was off entirely — otherwise the grant would silently do nothing. Revocable from the same place. Two behaviours made explicit rather than left to surprise people: nothing is broadcast (it is sent only when that contact asks, encrypted to them), and MeshCore only answers requests at all when base telemetry is allowed, so enabling location implies answering — the note under the dropdown says so, and the setter turns the master switch on rather than leaving a control that does nothing. No protocol change, so this interoperates with the MeshCore app and other MeshCore nodes rather than forking behaviour. All 8 S3 boards build. 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 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.