(Meshcore): runtime companion transport switching (BLE <-> WiFi/TCP) with persisted WiFi config + UI support#1968
Draft
just-stuff-tm wants to merge 22 commits intomeshcore-dev:devfrom
Conversation
Adding the new repeater cli commands introduced in 1.14 Ref: https://buymeacoffee.com/ripplebiz/path-diagnostics-improvements
Co-authored-by: Wessel <wessel@weebl.me>
Co-authored-by: Wessel <wessel@weebl.me>
Co-authored-by: Wessel <wessel@weebl.me>
Small grammar fix
…e switching Implements the core ask from meshcore-dev#1188 by enabling companion transport changes without re-flashing (BLE <-> serial/TCP path), and extends it per follow-up request to include WiFi/TCP network switching and CLI-configurable credentials. - add CompanionTransportInterface for ESP32 all-transports mode - support runtime transport switching: BLE <-> TCP/WiFi - add WiFi config vars: wifi.mode (ap/client), wifi.ssid/pwd, wifi.ap.ssid/pwd - persist new WiFi settings in NodePrefs/DataStore - wire settings into startup path in main.cpp - add MyMesh handlers for protocol + CLI Rescue commands - update Heltec v3 tcp_usb_ble variant flags/build wiring - improve UI: dedicated BLE/WiFi pages, hide inactive page, no overlap - refresh UI immediately on command-driven mode changes - show AP name/password/IP and client SSID/IP status on-device - add docs/wifi_transport_command_examples.md with raw/python/CLI examples
Update cli_commands.md to include path.hash.mode and loop.detect
…sync-release Update docs to align with implementation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feel Free To Fork and add additional board support And Submit PRs To this Branch, Lets get upstream to accept........
This PR adds a unified ESP32 companion transport layer for Heltec v3 that allows switching wireless companion transport at runtime between BLE and WiFi/TCP, without reflashing. It also adds persistent WiFi configuration, UI visibility/controls for active transport, and command documentation.
Base:
upstream/devDiff scope:
upstream/dev...feat/heltec-v3-runtime-transport-devSize: 10 files, +865/-31
What changed
CompanionTransportInterfacefor ESP32 (COMPANION_ALL_TRANSPORTS) that wraps:WIRELESS_MODE_BLEWIRELESS_MODE_TCPNodePrefswith:transport_modewifi_modewifi_ssid,wifi_pwdwifi_ap_ssid,wifi_ap_pwdDataStoreread/write layout to persist these fields.MyMeshcustom-var/CLI paths for:transport(ble/tcporwifi)wifi.mode(ap/client|sta)wifi.ssid,wifi.pwdwifi.ap.ssid,wifi.ap.pwdmain.cppnow initializes unified transport whenCOMPANION_ALL_TRANSPORTSis enabled.Heltec_v3_companion_radio_tcp_usb_bleCOMPANION_ALL_TRANSPORTSand companion radio/UI sources.docs/wifi_transport_command_examples.mdwith:meshcore-cliand CLI rescue command examplesWhy
This implements runtime companion transport switching for Heltec v3 and extends it to include WiFi AP/client configuration and persistence, improving field usability and reducing reflash cycles for transport changes.
Notes / compatibility
Behavior is gated to ESP32 builds with
COMPANION_ALL_TRANSPORTS.AP password validation enforces empty-or-8+ characters.
Existing boards/environments without this flag are unchanged.
Feature Request [Feature wish] Companion device: Connection via bluetooth or serial without re-flashing the firmware. #1188