DutchMeshCore.nl-MQTT

CLI Commands

This document provides an overview of CLI commands that can be sent to MeshCore Repeaters, Room Servers and Sensors.

Navigation

• Operational
• Neighbors
• Statistics
• Logging
• Information
• Configuration
  • Radio
  • System
  • Routing
  • ACL
  • Region Management
    • Region Examples
  • GPS
  • Sensors
  • Bridge
  • MQTT Observer Firmware
  • SNMP

---

Operational

Reboot the node

Usage:

• reboot

---

Reset the clock and reboot

Usage:

• clkreboot

---

Sync the clock with the remote device

Usage:

• clock sync

---

Display current time in UTC

Usage:

• clock

---

Set the time to a specific timestamp

Usage:

• time <epoch_seconds>

Parameters:

• epoch_seconds: Unix epoch time

---

Send a flood advert

Usage:

• advert

---

Send a zero-hop advert

Usage:

• advert.zerohop

---

Start an Over-The-Air (OTA) firmware update

Usage:

• start ota

---

Erase/Factory Reset

Usage:

• erase

Serial Only: Yes

Warning: This is destructive!

---

Neighbors (Repeater Only)

List nearby neighbors

Usage:

• neighbors

Note: The output of this command is limited to the 8 most recent adverts.

Note: Each line is encoded as {pubkey-prefix}:{timestamp}:{snr*4}

---

Remove a neighbor

Usage:

• neighbor.remove <pubkey_prefix>

Parameters:

• pubkey_prefix: The public key of the node to remove from the neighbors list

---

Discover zero hop neighbors

Usage:

• discover.neighbors

---

Statistics

Clear Stats

Usage: clear stats

---

System Stats - Battery, Uptime, Queue Length and Debug Flags

Usage:

• stats-core

Serial Only: Yes

---

Radio Stats - Noise floor, Last RSSI/SNR, Airtime, Receive errors

Usage: stats-radio

Serial Only: Yes

---

Packet stats - Packet counters: Received, Sent

Usage: stats-packets

Serial Only: Yes

---

Logging

Begin capture of rx log to node storage

Usage: log start

---

End capture of rx log to node storage

Usage: log stop

---

Erase captured log

Usage: log erase

---

Print the captured log to the serial terminal

Usage: log

Serial Only: Yes

---

Info

Get the Version

Usage: ver

---

Show the hardware name

Usage: board

---

Configuration

Radio

View or change this node’s radio parameters

Usage:

• get radio
• set radio <freq>,<bw>,<sf>,<cr>

Parameters:

• freq: Frequency in MHz
• bw: Bandwidth in kHz
• sf: Spreading factor (5-12)
• cr: Coding rate (5-8)

Set by build flag: LORA_FREQ, LORA_BW, LORA_SF, LORA_CR

Default: 869.525,250,11,5

Note: Requires reboot to apply

---

View or change this node’s transmit power

Usage:

• get tx
• set tx <dbm>

Parameters:

• dbm: Power level in dBm (1-22)

Set by build flag: LORA_TX_POWER

Default: Varies by board

Notes: This setting only controls the power level of the LoRa chip. Some nodes have an additional power amplifier stage which increases the total output. Refer to the node’s manual for the correct setting to use. Setting a value too high may violate the laws in your country.

---

Change the radio parameters for a set duration

Usage:

• tempradio <freq>,<bw>,<sf>,<cr>,<timeout_mins>

Parameters:

• freq: Frequency in MHz (300-2500)
• bw: Bandwidth in kHz (7.8-500)
• sf: Spreading factor (5-12)
• cr: Coding rate (5-8)
• timeout_mins: Duration in minutes (must be > 0)

Note: This is not saved to preferences and will clear on reboot

---

View or change this node’s frequency

Usage:

• get freq
• set freq <frequency>

Parameters:

• frequency: Frequency in MHz

Default: 869.525

Note: Requires reboot to apply Serial Only: set freq <frequency>

---

View or change this node’s rx boosted gain mode (SX12xx and LR1110, v1.14.1+)

Usage:

• get radio.rxgain
• set radio.rxgain <state>

Parameters:

• state: on

  off

Default: on

Temporary Note: If you upgraded from an older version to 1.14.1 without erasing flash, this setting is off because of #2118

---

View or change the LoRa FEM receive-path gain state on supported boards

Usage:

• get radio.fem.rxgain
• set radio.fem.rxgain <state>

Parameters:

• state: on

  off

Notes:

• This controls the external LoRa FEM receive-path LNA where the board supports it.
• This is separate from radio.rxgain, which controls the radio chip receive gain mode.

---

System

View or change this node’s name

Usage:

• get name
• set name <name>

Parameters:

• name: Node name

Set by build flag: ADVERT_NAME

Default: Varies by board

Note: Max length varies. If a location is set, the max length is 24 bytes; 32 otherwise. Emoji and unicode characters may take more than one byte.

---

View or change this node’s latitude

Usage:

• get lat
• set lat <degrees>

Set by build flag: ADVERT_LAT

Default: 0

Parameters:

• degrees: Latitude in degrees

---

View or change this node’s longitude

Usage:

• get lon
• set lon <degrees>

Set by build flag: ADVERT_LON

Default: 0

Parameters:

• degrees: Longitude in degrees

---

View or change this node’s identity (Private Key)

Usage:

• get prv.key
• set prv.key <private_key>

Parameters:

• private_key: Private key in hex format (64 hex characters)

Serial Only:

• get prv.key: Yes
• set prv.key: No

Note: Requires reboot to take effect after setting

---

Change this node’s admin password

Usage:

• password <new_password>

Parameters:

• new_password: New admin password

Set by build flag: ADMIN_PASSWORD

Default: password

Note: Command reply echoes the updated password for confirmation.

Note: Any node using this password will be added to the admin ACL list.

---

View or change this node’s guest password

Usage:

• get guest.password
• set guest.password <password>

Parameters:

• password: Guest password

Set by build flag: ROOM_PASSWORD (Room Server only)

Default: <blank>

---

View or change this node’s owner info

Usage:

• get owner.info
• set owner.info <text>

Parameters:

• text: Owner information text

Default: <blank>

Note: | characters are translated to newlines

Note: Requires firmware 1.12+

---

Fine-tune the battery reading

Usage:

• get adc.multiplier
• set adc.multiplier <value>

Parameters:

• value: ADC multiplier (0.0-10.0)

Default: 0.0 (value defined by board)

Note: Returns “Error: unsupported by this board” if hardware doesn’t support it

---

View this node’s public key

Usage: get public.key

---

View this node’s firmware version

Usage: ver

---

View this node’s configured role

Usage: get role

---

View or change this node’s power saving flag (Repeater Only)

Usage:

• powersaving
• powersaving on
• powersaving off

Parameters:

• on: enable power saving
• off: disable power saving

Default: off

Note: When enabled, device enters sleep mode between radio transmissions

---

Routing

View or change this node’s repeat flag

Usage:

• get repeat
• set repeat <state>

Parameters:

• state: on

  off

Default: on

---

View or change this node’s advert path hash size

Usage:

• get path.hash.mode
• set path.hash.mode <value>

Parameters:

• value: Path hash size (0-2)
  • 0: 1 Byte hash size (256 unique ids)[64 max flood]
  • 1: 2 Byte hash size (65,536 unique ids)[32 max flood]
  • 2: 3 Byte hash size (16,777,216 unique ids)[21 max flood]
  • 3: DO NOT USE (Reserved)

Default: 0

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 propagation 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 supported. 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 (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.

---

View or change the retransmit delay factor for flood traffic

Usage:

• get txdelay
• set txdelay <value>

Parameters:

• value: Transmit delay factor (0-2)

Default: 0.5

Note: When multiple nearby repeaters all hear the same flood packet, each waits a random amount of time before retransmitting to avoid simultaneous collisions. This factor scales the size of that random window. Higher values reduce collision risk at the cost of added latency. 0 disables the window entirely.

---

View or change the retransmit delay factor for direct traffic

Usage:

• get direct.txdelay
• set direct.txdelay <value>

Parameters:

• value: Direct transmit delay factor (0-2)

Default: 0.2

Note: Same collision-avoidance random window as txdelay, but applied to direct (non-flood, routed) traffic. The default is lower because direct packets are addressed to a specific next hop, so far fewer nodes compete to retransmit them.

---

[Experimental] View or change the processing delay for received traffic

Usage:

• get rxdelay
• set rxdelay <value>

Parameters:

• value: Receive delay base (0-20)

Default: 0.0

Note: When enabled, repeaters that received a flood packet with a weak signal are held in a delay queue before processing, while those that received it with a strong signal process it immediately. This gives strong-signal paths forwarding priority. By the time weak-signal nodes process their copy, the packet may have already propagated and will be suppressed as a duplicate, reducing redundant retransmissions.

---

View or change the duty cycle limit

Usage:

• get dutycycle
• set dutycycle <value>

Parameters:

• value: Duty cycle percentage (1-100)

Default: 50% (equivalent to airtime factor 1.0)

Examples:

• set dutycycle 100 — no duty cycle limit
• set dutycycle 50 — 50% duty cycle (default)
• set dutycycle 10 — 10% duty cycle
• set dutycycle 1 — 1% duty cycle (strictest EU requirement)

Note: Added in firmware v1.15.0

---

View or change the airtime factor (duty cycle limit)

Deprecated as of firmware v1.15.0. Use get/set dutycycle instead.

Usage:

• get af
• set af <value>

Parameters:

• value: Airtime factor (0-9). After each transmission, the repeater enforces a silent period of approximately the on-air transmission time multiplied by the value. This results in a long-term duty cycle of roughly 1 divided by (1 plus the value). For example:
  • af = 1 → ~50% duty
  • af = 2 → ~33% duty
  • af = 3 → ~25% duty
  • af = 9 → ~10% duty You are responsible for choosing a value that is appropriate for your jurisdiction and channel plan (for example EU 868 Mhz 10% duty cycle regulation).

Default: 1.0

---

View or change the local interference threshold

Usage:

• get int.thresh
• set int.thresh <value>

Parameters:

• value: Interference threshold value

Default: 0.0

---

Enable or disable hardware Channel Activity Detection (CAD)

Usage:

• get cad
• set cad <on|off>

Description: When enabled, the radio performs a hardware Channel Activity Detection scan before transmitting and defers if the channel is busy. Runs independently of int.thresh — either, both, or none may be active.

Parameters:

• on|off: Enable or disable hardware CAD

Default: off

---

View or change the AGC Reset Interval

Usage:

• get agc.reset.interval
• set agc.reset.interval <value>

Parameters:

• value: Interval in seconds rounded down to a multiple of 4 (17 becomes 16). 0 to disable.

Default: 0.0

---

View or change the radio watchdog interval

Usage:

• get radio.watchdog
• set radio.watchdog <minutes>

Parameters:

• minutes: 0 to disable, or 1-120 minutes

Default: 5

Note: On quiet meshes, increasing this can reduce false recoveries when no traffic is expected.

---

Enable or disable Multi-Acks support

Usage:

• get multi.acks
• set multi.acks <state>

Parameters:

• state: 0 (disable) or 1 (enable)

Default: 0

---

View or change the flood advert interval

Usage:

• get flood.advert.interval
• set flood.advert.interval <hours>

Parameters:

• hours: Interval in hours (3-168)

Default: 12 (Repeater) - 0 (Sensor)

---

View or change the zero-hop advert interval

Usage:

• get advert.interval
• set advert.interval <minutes>

Parameters:

• minutes: Interval in minutes rounded down to the nearest multiple of 2 (61 becomes 60) (60-240)

Default: 0

---

Limit the number of hops for a flood message

Usage:

• get flood.max
• set flood.max <value>

Parameters:

• value: Maximum flood hop count (0-64)

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

Add, update or remove permissions for a companion

Usage:

• setperm <pubkey> <permissions>

Parameters:

• pubkey: Companion public key
• permissions:
  • 0: Guest
  • 1: Read-only
  • 2: Read-write
  • 3: Admin

Note: Removes the entry when permissions is omitted

---

View the current ACL

Usage:

• get acl

Serial Only: Yes

---

View or change this room server’s ‘read-only’ flag

Usage:

• get allow.read.only
• set allow.read.only <state>

Parameters:

• state: on (enable) or off (disable)

Default: off

---

Region Management (v1.10.+)

Bulk-load region lists

Usage:

• region load
• region load <name> [flood_flag]

Parameters:

• name: A name of a region. * represents the wildcard region

Note: flood_flag: Optional F to allow flooding

Note: Indentation creates parent-child relationships (max 8 levels)

Note: region load with an empty name will not work remotely (it’s interactive)

---

Save any changes to regions made since reboot

Usage:

• region save

---

Allow a region

Usage:

• region allowf <name>

Parameters:

• name: Region name (or * for wildcard)

Note: Setting on wildcard * allows packets without region transport codes

---

Block a region

Usage:

• region denyf <name>

Parameters:

• name: Region name (or * for wildcard)

Note: Setting on wildcard * drops packets without region transport codes

---

Show information for a region

Usage:

• region get <name>

Parameters:

• name: Region name (or * for wildcard)

---

View or change the home region for this node

Usage:

• region home
• region home <name>

Parameters:

• name: Region name

---

View or change the default scope region for this node

Usage:

• region default
• region default {name|<null>}

Parameters:

• name: Region name, or to reset/clear

---

Create a new region

Usage:

• region put <name> [parent_name]

Parameters:

• name: Region name
• parent_name: Parent region name (optional, defaults to wildcard)

Note: In firmware v1.15.0 and later, region put enables flooding for that region by default (you do not need a separate region allowf <name> after each put). On v1.14.0 and earlier, new regions may still require region allowf for flooding—see region allowf.

---

Define region hierarchy (single line)

Usage:

• region def <token> [<token> ...]

Parameters (tokens): Space-separated. A logical cursor starts at the wildcard *.

• name — Create name as a child of the current cursor (equivalent to region put name with the cursor as parent). Cursor moves to name.
• name|jump (or name,jump) — Create name as a child of the current cursor, then move the cursor to jump (must already exist on the node, or have been created earlier in this command). jump is not the parent of name; use this form to pop back up and start another branch.

Behavior: Each created region defaults to flood-allowed (same as region put). The reply is the resulting region tree (same format as bare region); review it before running region save to persist. On error, the reply is Err - ... and any regions placed before the failure remain on the node, just like a partial chain of region put.

Existing regions: region def does not clear the existing tree — if a name already exists, its parent is updated to the current cursor; otherwise a new region is created. To start from scratch, region remove the unwanted regions first.

Limits: Repeater serial accepts one line up to 160 characters. For larger trees, split across multiple region def commands; the cursor resets to * between commands, so lead the next command with child|ancestor to reposition. Each token splits at most once on | — region def a|b|c|d is not a flat-list shorthand; see the flat-list example below.

Example — linear chain (each token becomes a child of the previous):

region def a b c d e
region save

Example — branched tree (equivalent to region put a, region put b a, region put c b, region put d c, region put e b, region put f e):

region def a b c d|b e f
region save

Example — error and partial state:

region def a b c|nope d

The reply is Err - unknown jump: nope. a, b, and c were placed before the failure; d was not. Run region to inspect, then re-run with a corrected jump or repair with region remove / region put.

Example — flat list (each region a child of *). Use |* after each token to pop the cursor back to the root before the next token:

region def a|* b|* c|* d|* e|* f
region save

---

Remove a region

Usage:

• region remove <name>

Parameters:

• name: Region name

Note: Must remove all child regions before the region can be removed

---

View all regions

Usage:

• region list <filter>

Serial Only: Yes

Parameters:

• filter: allowed

  denied

Note: Requires firmware 1.12+

---

Dump all defined regions and flood permissions

Usage:

• region

Serial Only: For firmware older than 1.12.0

---

Region Examples

Example 1: Using F Flag with Named Public Region

region load
#Europe F
<blank line to end region load>
region save

Explanation:

• Creates a region named #Europe with flooding enabled
• Packets from this region will be flooded to other nodes

---

Example 2: Using Wildcard with F Flag

region load 
* F
<blank line to end region load>
region save

Explanation:

• Creates a wildcard region * with flooding enabled
• Enables flooding for all regions automatically
• Applies only to packets without transport codes

---

Example 3: Using Wildcard Without F Flag

region load 
*
<blank line to end region load>
region save

Explanation:

• Creates a wildcard region * without flooding
• This region exists but doesn’t affect packet distribution
• Used as a default/empty region

---

Example 4: Nested Public Region with F Flag

region load 
#Europe F
  #UK
    #London
    #Manchester
  #France
    #Paris
    #Lyon
<blank line to end region load>
region save

Explanation:

• Creates #Europe region with flooding enabled
• Adds nested child regions (#UK, #France)
• All nested regions inherit the flooding flag from parent

---

Example 5: Wildcard with Nested Public Regions

region load 
* F
  #NorthAmerica
    #USA
      #NewYork
      #California
    #Canada
      #Ontario
      #Quebec
<blank line to end region load>
region save

Explanation:

• Creates wildcard region * with flooding enabled
• Adds nested #NorthAmerica hierarchy
• Enables flooding for all child regions automatically
• Useful for global networks with specific regional rules

---

GPS (When GPS support is compiled in)

View or change GPS state

Usage:

• gps
• gps <state>

Parameters:

• state: on

  off

Default: off

Note: Output format:

• off when the GPS hardware is disabled
• on, {active|deactivated}, {fix|no fix}, {sat count} sats when the GPS hardware is enabled

---

Sync this node’s clock with GPS time

Usage:

• gps sync

---

Set this node’s location based on the GPS coordinates

Usage:

• gps setloc

---

View or change the GPS advert policy

Usage:

• gps advert
• gps advert <policy>

Parameters:

• policy: none

  share

  prefs

  • none: don’t include location in adverts
  • share: share gps location (from SensorManager)
  • prefs: location stored in node’s lat and lon settings

Default: prefs

---

Sensors (When sensor support is compiled in)

View the list of sensors on this node

Usage: sensor list [start]

Parameters:

• start: Optional starting index (defaults to 0)

Note: Output format: <var_name>=<value>\n

---

View or change the value of a sensor

Usage:

• sensor get <key>
• sensor set <key> <value>

Parameters:

• key: Sensor setting name
• value: The value to set the sensor to

---

Bridge (When bridge support is compiled in)

View the compiled bridge type

Usage: get bridge.type

---

View or change the bridge enabled flag

Usage:

• get bridge.enabled
• set bridge.enabled <state>

Parameters:

• state: on

  off

Default: off

---

Add a delay to packets routed through this bridge

Usage:

• get bridge.delay
• set bridge.delay <ms>

Parameters:

• ms: Delay in milliseconds (0-10000)

Default: 500

---

View or change the source of packets bridged to the external interface

Usage:

• get bridge.source
• set bridge.source <source>

Parameters:

• source:
  • logRx: bridges received packets
  • logTx: bridges transmitted packets

Default: logTx

Note: For MQTT bridges, use mqtt.rx and mqtt.tx instead of bridge.source. These provide independent per-direction control and support both RX and TX simultaneously. bridge.source still works as a convenience alias for MQTT (setting bridge.source rx sets mqtt.rx on + mqtt.tx off, and vice versa), but mqtt.rx/mqtt.tx are preferred.

---

View or change MQTT RX packet uplinking

Usage:

• get mqtt.rx
• set mqtt.rx <on|off>

Parameters:

• on: uplink received (RX) packets to MQTT brokers
• off: disable RX packet uplinking

Default: on

---

View or change MQTT TX packet uplinking

Usage:

• get mqtt.tx
• set mqtt.tx <on|off|advert>

Parameters:

• on: uplink all transmitted (TX) packets to MQTT brokers
• advert: uplink only this node’s own advert packets (self-originated advertisements only — forwarded adverts from other nodes are filtered out)
• off: disable TX packet uplinking

Default: advert

Note: mqtt.rx and mqtt.tx take effect immediately — no restart required. Both can be enabled simultaneously.

---

MQTT Observer Firmware (When MQTT bridge support is compiled in)

MQTT observer builds add WiFi connectivity and MQTT packet uplinking to repeater and room server firmware.

Quick first-time setup

Usage:

set radio 910.525,62.5,7,5
set tx 22
set name MyObserver
set mqtt.iata SEA
set wifi.ssid YourWiFiNetwork
set wifi.pwd YourWiFiPassword
reboot

Optional receive-only observer:

set repeat off

Verify:

get bridge.enabled
get mqtt.rx
get mqtt.tx
get mqtt.origin
get mqtt.iata
get mqtt1.preset
get mqtt2.preset
get mqtt.status
get wifi.status

---

View available MQTT presets

Usage:

• get mqtt.presets
• get mqtt.presets <start>

Parameters:

• start: Optional index returned as next:<idx> when the preset list is paginated

Available presets include: analyzer-us, analyzer-eu, meshmapper, meshrank, waev, meshomatic, cascadiamesh, tennmesh, nashmesh, chimesh, meshat.se, eastidahomesh, dutchmeshcore-1, dutchmeshcore-2, coloradomesh, custom, none

---

View or change an MQTT slot preset

Usage:

• get mqttN.preset
• set mqttN.preset <preset>

Parameters:

• N: Slot number (1-6)
• preset: Preset name, such as dutchmeshcore-1, dutchmeshcore-2, meshmapper, meshrank, custom, or none

DutchMeshCore presets:

• set mqttN.preset dutchmeshcore-1: Use wss://collector1.dutchmeshcore.nl:443/mqtt
• set mqttN.preset dutchmeshcore-2: Use wss://collector2.dutchmeshcore.nl:443/mqtt

Default for this firmware: Slot 1 and slot 2 are DutchMeshCore presets. Slot 1 is dutchmeshcore-1, slot 2 is dutchmeshcore-2, and slots 3-6 are none.

---

View or change custom MQTT slot settings

Usage:

• get mqttN.server
• set mqttN.server <hostname-or-url>
• get mqttN.port
• set mqttN.port <port>
• get mqttN.username
• set mqttN.username <username>
• get mqttN.password
• set mqttN.password <password>
• get mqttN.token
• set mqttN.token <token>
• get mqttN.topic
• set mqttN.topic <template>
• get mqttN.audience
• set mqttN.audience <audience>
• set mqttN.audience

Parameters:

• N: Slot number (1-6)
• port: Port number (1-65535)
• token: Per-slot token, used by presets such as meshrank
• template: Custom topic template; only applies when the slot preset is custom
• audience: JWT audience for custom broker Ed25519 JWT authentication

Notes:

• Custom server, port, username, password, topic, and audience settings only apply when the slot preset is custom.
• set mqttN.audience without a value clears the audience and returns the slot to username/password authentication.

---

Configure MeshRank on a slot

Usage:

set mqtt3.preset meshrank
set mqtt3.token <meshrank_token>

Note: MeshRank requires a token and receives packet data only.

---

Configure a custom broker

Usage:

set mqtt3.preset custom
set mqtt3.server your-broker.example.com
set mqtt3.port 1883
set mqtt3.username your-username
set mqtt3.password your-password

JWT custom broker example:

set mqtt3.preset custom
set mqtt3.server wss://my-broker.example.com:443/mqtt
set mqtt3.port 443
set mqtt3.audience my-broker.example.com

Custom topic example:

set mqtt3.preset custom
set mqtt3.server my-broker.local
set mqtt3.port 1883
set mqtt3.topic mynetwork/{device}/{type}

Topic placeholders:

• {iata}: IATA airport code configured by set mqtt.iata
• {device}: Device public key
• {token}: Per-slot token from mqttN.token
• {type}: Message type: status, packets, or raw

Default custom topic: meshcore/{iata}/{device}/{type}

---

View or change MQTT shared settings

Usage:

• get mqtt.origin
• set mqtt.origin <name>
• get mqtt.iata
• set mqtt.iata <code>
• get mqtt.status
• set mqtt.status <on|off>
• get mqtt.packets
• set mqtt.packets <on|off>
• get mqtt.raw
• set mqtt.raw <on|off>
• get mqtt.interval
• set mqtt.interval <minutes>
• get mqtt.owner
• set mqtt.owner <64-hex-char-public-key>
• get mqtt.email
• set mqtt.email <email>

Parameters:

• code: IATA airport code; auto-uppercased
• minutes: Status publish interval (1-60)

Serial Only:

• get mqtt.owner: Yes
• get mqtt.email: Yes

Defaults:

• mqtt.status: on
• mqtt.packets: on
• mqtt.raw: off
• mqtt.interval: 5 minutes

---

View or change WiFi settings

Usage:

• get wifi.ssid
• set wifi.ssid <ssid>
• get wifi.pwd
• set wifi.pwd <password>
• get wifi.status
• get wifi.powersave
• set wifi.powersave <none|min|max>

Parameters:

• none: No WiFi power saving
• min: Minimum WiFi power saving
• max: Maximum WiFi power saving

Default: none

---

View or change timezone settings

Usage:

• get timezone
• set timezone <string>
• get timezone.offset
• set timezone.offset <offset>

Parameters:

• string: IANA timezone (Europe/Amsterdam), abbreviation (CET), or UTC offset (UTC+1)
• offset: Fallback offset in hours (-12 to +14)

---

MQTT observer build targets

Usage:

pio run -e Heltec_v3_repeater_observer_mqtt
pio run -e heltec_v4_repeater_observer_mqtt
pio run -e Station_G2_repeater_observer_mqtt
pio run -e LilyGo_TLora_V2_1_1_6_repeater_observer_mqtt
pio run -e LilyGo_TLora_V2_1_1_6_room_server_observer_mqtt

Build flags:

• WITH_MQTT_BRIDGE=1: Enable MQTT bridge support
• WITH_SNMP=1: Enable optional SNMP monitoring on supported observer builds

---

MQTT observer flashing notes

Some MQTT observer builds use larger app partitions for MQTT, TLS, and certificate bundle support. When a board’s partition table changes, flash the merged firmware (*-merged.bin) the first time so the bootloader and partition table are written together.

Environment	Partition table	Flash size	App slot size	Notes
LilyGo_T3S3_sx1262_repeater_observer_mqtt	min_spiffs.csv	4 MB	1.875 MB	Changed from default
LilyGo_T3S3_sx1262_room_server_observer_mqtt	min_spiffs.csv	4 MB	1.875 MB	Changed from default
LilyGo_TLora_V2_1_1_6_repeater_observer_mqtt	min_spiffs.csv	4 MB	1.875 MB	TTGO LoRa32 V1.0; observer env omits sensor_base
LilyGo_TLora_V2_1_1_6_room_server_observer_mqtt	min_spiffs.csv	4 MB	1.875 MB	Same as repeater observer
Station_G2_repeater_observer_mqtt	default_16MB.csv	16 MB	6.25 MB	16 MB flash board
Station_G2_room_server_observer_mqtt	default_16MB.csv	16 MB	6.25 MB	16 MB flash board

Merged firmware example:

pio run -t mergebin -e LilyGo_T3S3_sx1262_repeater_observer_mqtt
esptool.py write_flash 0x0 .pio/build/LilyGo_T3S3_sx1262_repeater_observer_mqtt/firmware-merged.bin

Note: If the partition layout changes, stored settings in NVS are typically wiped or invalidated. Expect to reconfigure admin preferences, WiFi, MQTT slots, device name, and related settings.

---

MQTT topics

Type	Topic
Status	meshcore/{IATA}/{DEVICE_PUBLIC_KEY}/status
Packets	meshcore/{IATA}/{DEVICE_PUBLIC_KEY}/packets
Raw	meshcore/{IATA}/{DEVICE_PUBLIC_KEY}/raw

Note: {DEVICE_PUBLIC_KEY} is the device public key as 64 hexadecimal characters.

---

MQTT troubleshooting

WiFi issues:

get wifi.ssid
get wifi.pwd
get wifi.status
set wifi.powersave none
reboot

No MQTT messages appearing:

get bridge.enabled
set bridge.enabled on
get mqtt.rx
set mqtt.rx on
get mqtt.tx
get mqtt.status
get mqtt1.preset
get mqtt2.preset
get mqtt.iata

Timezone issues:

get timezone
set timezone Europe/Amsterdam
set timezone.offset 1

---

View or change the speed of the bridge (RS-232 only)

Usage:

• get bridge.baud
• set bridge.baud <rate>

Parameters:

• rate: Baud rate (9600, 19200, 38400, 57600, or 115200)

Default: 115200

---

View or change the channel used for bridging (ESPNow only)

Usage:

• get bridge.channel
• set bridge.channel <channel>

Parameters:

• channel: Channel number (1-14)

---

Set the ESP-Now secret

Usage:

• get bridge.secret
• set bridge.secret <secret>

Parameters:

• secret: ESP-NOW bridge secret, up to 15 characters

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.

---

SNMP (When SNMP support is compiled in)

SNMP observer builds expose read-only SNMP v2c monitoring for radio statistics, MQTT connectivity, memory usage, and WiFi RSSI.

View or change SNMP state

Usage:

• get snmp
• set snmp <on|off>

Default: off

Note: Restart required after changing.

---

View or change SNMP community string

Usage:

• get snmp.community
• set snmp.community <string>

Default: public

Note: Restart required after changing.

---

Poll SNMP from a host on the same network

Usage:

snmpwalk -v2c -c public <device-ip> 1.3.6.1.4.1.99999

Note: The SNMP agent listens on UDP port 161 and uses the private enterprise subtree 1.3.6.1.4.1.99999.

---

This site is open source. Improve this page.