Merge upstream/dev into mqtt-bridge-implementation-flex

Pick up 97 commits from upstream/dev, resolving conflicts in
CommonCLI prefs layout, board definitions, docs, and T-Beam Supreme
platformio config.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
agessamanandCursor committed 2026-06-06 09:29:16 -07:00
commit dcc8f826db
78 files changed
+1220 -828

No files matched your search

+20 -19
View File
@@ -217,20 +217,6 @@ This document provides an overview of CLI commands that can be sent to MeshCore
---
#### View or change the boosted receive gain mode
**Usage:**
- `get radio.rxgain`
- `set radio.rxgain <state>`
**Parameters:**
- `state`: `on`|`off`
**Default:** `off`
**Note:** Only available on SX1262 and SX1268 based boards.
---
#### Change the radio parameters for a set duration
**Usage:**
- `tempradio <freq>,<bw>,<sf>,<cr>,<timeout_mins>`
@@ -261,7 +247,7 @@ This document provides an overview of CLI commands that can be sent to MeshCore
---
#### View or change this node's rx boosted gain mode (SX12xx only, v1.14.1+)
#### View or change this node's rx boosted gain mode (SX12xx and LR1110, v1.14.1+)
**Usage:**
- `get radio.rxgain`
- `set radio.rxgain <state>`
@@ -380,7 +366,7 @@ This document provides an overview of CLI commands that can be sent to MeshCore
**Note:** `|` characters are translated to newlines
**Note:** Requires firmware 1.12.+
**Note:** Requires firmware 1.12+
---
@@ -418,7 +404,7 @@ This document provides an overview of CLI commands that can be sent to MeshCore
- `on`: enable power saving
- `off`: disable power saving
**Default:** `on`
**Default:** `off`
**Note:** When enabled, device enters sleep mode between radio transmissions
@@ -472,7 +458,7 @@ This document provides an overview of CLI commands that can be sent to MeshCore
**Default:** `off`
**Note:** When it is enabled, repeaters will now reject flood packets which look like they are in a loop. This has been happening recently in some meshes when there is just a single 'bad' repeater firmware out there (prob some forked or custom firmware). If the payload is messed with, then forwarded, the same packet ends up causing a packet storm, repeated up to the max 64 hops. This feature was added in firmware 1.14
**Note:** When it is enabled, repeaters will now reject flood packets which look like they are in a loop. This has been happening recently in some meshes when there is just a single 'bad' repeater firmware out there (probably some forked or custom firmware). If the payload is messed with, then forwarded, the same packet ends up causing a packet storm, repeated up to the max 64 hops. This feature was added in firmware 1.14
**Example:** If preference is `loop.detect minimal`, and a 1-byte path size packet is received, the repeater will see if its own ID/hash is already in the path. If it's already encoded 4 times, it will reject the packet. If the packet uses 2-byte path size, and repeater's own ID/hash is already encoded 2 times, it rejects. If the packet uses 3-byte path size, and the repeater's own ID/hash is already encoded 1 time, it rejects.
@@ -643,6 +629,21 @@ This document provides an overview of CLI commands that can be sent to MeshCore
**Default:** `64`
---
#### Limit the number of hops for an unscoped flood message
**Usage:**
- `get flood.max.unscoped`
- `set flood.max.unscoped <value>`
**Parameters:**
- `value`: Maximum flood hop count (0-64) for a packet without a scope (no region set)
**Default:** `0xFF` - indicates it hasn't been set, will track flood.max until it is.
**Note:** An alternative to `region denyf *`, setting `flood.max.unscoped` to a lower value such as `3` would allow for local unscoped messages to propagate, while preventing noisy neighbors from flooding a local region.
---
### ACL
@@ -831,7 +832,7 @@ region save
**Parameters:**
- `filter`: `allowed`|`denied`
**Note:** Requires firmware 1.12.+
**Note:** Requires firmware 1.12+
---