shade/MeshCoreTel-firmware
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

Removed EastMesh MQTT broker support.

Browse Source 
It's intended for Eastern Australia repeaters only.  Using original EastMesh
firmware is prefered in this case.
This commit is contained in:
Valentin V. Bartenev
2026-04-28 00:52:26 +03:00
parent 64cebbc750
commit 46b0df7a4b
8 changed files with 64 additions and 413 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/custom-cli.md
+3 -7
View File
@@ -1,6 +1,6 @@
# Custom CLI Commands
This page covers the EastMesh-specific CLI commands added in this repository.
This page covers the MeshCoreTel-specific CLI commands added in this repository.
It does not try to repeat the full upstream MeshCore CLI surface.
@@ -38,11 +38,8 @@ These commands are available on `*_repeater_mqtt` firmware targets.
### MQTT Endpoints
- `set mqtt.meshcoretel on|off`
- `get mqtt.meshcoretel`
- `set mqtt.letsmesh-us on|off`
- `get mqtt.eastmesh-au`
- `set mqtt.eastmesh-au on|off`
- `set mqtt.meshcoretel on|off`
- `get mqtt.letsmesh-eu`
- `set mqtt.letsmesh-eu on|off`
- `get mqtt.letsmesh-us`
@@ -52,11 +49,10 @@ Notes:
- new repeater MQTT installs default `mqtt.iata` to `UNSET`
- `letsmesh-eu` and `letsmesh-us` remain off by default unless already configured in saved prefs
- if `mqtt.iata` is `UNSET`, `meshcoretel`, `eastmesh-au`, `letsmesh-eu`, and `letsmesh-us` will not connect even if they are toggled on
- if `mqtt.iata` is `UNSET`, `meshcoretel`, `letsmesh-eu`, and `letsmesh-us` will not connect even if they are toggled on
Legacy dotted aliases are also accepted:
- `mqtt.eastmesh.au`
- `mqtt.letsmesh.eu`
- `mqtt.letsmesh.us`