**Note:** the 'path.hash.mode' sets the low-level ID/hash encoding size used when the repeater adverts. This setting has no impact on what packet ID/hash size this repeater forwards, all sizes should be forwarded on firmware >= 1.14. This feature was added in firmware 1.14
**Temporary Note:** adverts with ID/hash sizes of 2 or 3 bytes may have limited flood propogation in your network while this feature is new as v1.13.0 firmware and older will drop packets with multibyte path ID/hashes as only 1-byte hashes are suppored. Consider your install base of firmware >=1.14 has reached a criticality for effective network flooding before implementing higher ID/hash sizes.
---
#### View or change this node's loop detection
**Usage:**
- `get loop.detect`
- `set loop.detect <state>`
**Parameters:**
- `state`:
- `off`: no loop detection is performed
- `minimal`: packets are dropped if repeater's ID/hash appears 4 or more times (1-byte), 2 or more (2-byte), 1 or more (3-byte)
- `moderate`: packets are dropped if repeater's ID/hash appears 2 or more times (1-byte), 1 or more (2-byte), 1 or more (3-byte)
- `strict`: packets are dropped if repeater's ID/hash appears 1 or more times (1-byte), 1 or more (2-byte), 1 or more (3-byte)
**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
**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.
---
#### View or change the retransmit delay factor for flood traffic
#### View or change the retransmit delay factor for flood traffic
**Usage:**
**Usage:**
- `get txdelay`
- `get txdelay`
@ -804,6 +862,11 @@ region save
### Bridge (When bridge support is compiled in)
### Bridge (When bridge support is compiled in)
#### View the compiled bridge type
**Usage:** `get bridge.type`
---
#### View or change the bridge enabled flag
#### View or change the bridge enabled flag
**Usage:**
**Usage:**
- `get bridge.enabled`
- `get bridge.enabled`
@ -816,12 +879,6 @@ region save
---
---
#### View the bridge source
**Usage:**
- `get bridge.source`
---
#### Add a delay to packets routed through this bridge
#### Add a delay to packets routed through this bridge
**Usage:**
**Usage:**
- `get bridge.delay`
- `get bridge.delay`
@ -841,10 +898,10 @@ region save
**Parameters:**
**Parameters:**
- `source`:
- `source`:
- `rx`: bridges received packets
- `logRx`: bridges received packets
- `tx`: bridges transmitted packets
- `logTx`: bridges transmitted packets
**Default:** `tx`
**Default:** `logTx`
---
---
@ -876,8 +933,39 @@ region save
- `set bridge.secret <secret>`
- `set bridge.secret <secret>`
**Parameters:**
**Parameters:**
- `secret`: 16-character encryption secret
- `secret`: ESP-NOW bridge secret, up to 15 characters
**Default:** Varies by board
**Default:** Varies by board
---
---
#### View the bootloader version (nRF52 only)
**Usage:** `get bootloader.ver`
---
#### View power management support
**Usage:** `get pwrmgt.support`
---
#### View the current power source
**Usage:** `get pwrmgt.source`
**Note:** Returns an error on boards without power management support.
---
#### View the boot reset and shutdown reasons
**Usage:** `get pwrmgt.bootreason`
**Note:** Returns an error on boards without power management support.
---
#### View the boot voltage
**Usage:** `get pwrmgt.bootmv`
**Note:** Returns an error on boards without power management support.
@ -221,11 +221,11 @@ MeshCore allows you to manually broadcast your name, position and public encrypt
* Zero hop means your advert is broadcasted out to anyone that can hear it, and that's it.
* Zero hop means your advert is broadcasted out to anyone that can hear it, and that's it.
* Flooded means it's broadcasted out and then repeated by all the repeaters that hear it.
* Flooded means it's broadcasted out and then repeated by all the repeaters that hear it.
MeshCore clients only advertise themselves when the user initiates it. A repeater sends a flood advert once every 3 hours by default. This interval can be configured using the following command:
MeshCore clients only advertise themselves when the user initiates it. A repeater sends a flood advert once every 12 hours by default. This interval can be configured using the following command:
`set advert.interval {minutes}`
`set flood.advert.interval {hours}`
As of Aug 20 2025, a pending PR on github will change the flood advert to 12 hours to minimize airtime utilization caused by repeaters' flood adverts.
The separate `set advert.interval {minutes}` command controls the local zero-hop advert timer.
### 2.5. Q: Is there a hop limit?
### 2.5. Q: Is there a hop limit?
@ -260,7 +260,9 @@ Repeater or room server can be administered with one of the options below:
### 3.2. Q: Do I need to set the location for a repeater?
### 3.2. Q: Do I need to set the location for a repeater?
**A:** While not required, with location set for a repeater it will show up on the MeshCore map in the future. Set location with the following command:
**A:** While not required, with location set for a repeater it will show up on the MeshCore map in the future. Set location with the following command:
`set lat <GPS Lat> set long <GPS Lon>`
`set lat <GPS Lat>`
`set lon <GPS Lon>`
You can get the latitude and longitude from Google Maps by right-clicking the location you are at on the map.
You can get the latitude and longitude from Google Maps by right-clicking the location you are at on the map.