Kaj SchittecatandClaude Opus 5
19a7ca85ce
@D-Melhede saw a P4 claim 71% and then die, with Meck-P4 reading 11% on the same pack; a full charge never quite reached 100%; and "calibrate 100% here" made it permanently worse. @wb6zsu watched it read 51%, then 100% the instant USB went in. All of that is one cause. The P4 carries a BQ27220 fuel gauge, which coulomb-counts against its learned pack profile and therefore knows the actual state of charge, but we only ever read its Voltage() register and pushed that through the generic 3.30-4.20 V linear curve. Terminal voltage is charger-driven, so it pins at 100% the moment USB is connected however empty the pack is, sits under 100% on a rested full pack, and calibrating "full" while charging captures a charger rail as the reference and bakes the error in for good. The old comment conceded the limit in as many words: "the real cell % isn't observable here". On this board it is. Now reads StateOfCharge() and uses it directly, falling back to the voltage curve only when the gauge does not answer or reports out of range, so a dead gauge is no worse than today rather than a made-up number. The register is REG 0x2C, taken from LilyGo's own SensorLib (GaugeBQ27220.hpp "StateOfCharge; // % - REG2C") rather than from memory, since guessing a register here would produce confident nonsense. Does NOT address the charging/LED half of that report: whether the pack charges correctly and what drives the red/green LED is the BQ25896 charger, which we still do not talk to. Tracked separately in the issue. P4 builds; T-Deck and V4 unaffected (the gauge path is board-gated). 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.