NODE ADMIN
REMOTE NODE MANAGEMENT · LOCAL & OVER-MESH CONFIGURATION
LOADING...
SELECT A NODE
Pick a radio slot and target node from the sidebar.
LOCAL NODE — Directly connected. All tabs work now, no setup needed.
YOUR RADIO'S ADMIN KEY Paste this into any remote node you want to manage
To remotely administer other nodes, physically connect to each one and paste this key into Settings → Radio Config → Security → Admin Key. One-time setup — then all tabs work wirelessly.
Reading...
ADMIN KEY REQUIRED One-time physical setup on the remote node
Before you can configure this node remotely, you need to add your local radio's public key to it once via physical access (USB/BLE/WiFi). After that, all tabs work wirelessly — no further access needed.
STEP 1 — YOUR LOCAL RADIO'S KEY (copy this)
Loading...
STEP 2 — PASTE IT INTO THE REMOTE NODE
Physically connect to the remote node, then go to:
Settings → Radio Config → Security → Admin Key
Paste the key above. Save. Reboot. Done — come back here and use the other tabs.
THINGS TO KNOW
Requires firmware 2.5+ on both radios.
Commands are sent — not confirmed. Verify changes after the node reboots.
Most changes need a reboot — use the Reboot button in the Danger tab.
Wrong LoRa settings on a remote node can make it unreachable. Test locally first.
REMOTE NODE — Command sent over the mesh. No direct confirmation. Requires reboot to take effect. Ensure admin key is configured (see Setup Guide tab).
NODE IDENTITY Broadcast to mesh on change · Max 39 / 4 chars
LONG NAME
Full display name shown in node lists and messages. Max 39 characters.
SHORT NAME
4-character abbreviation for compact displays and screen overlays.
REMOTE NODE — Role change sent over mesh. Requires reboot. Role affects relay behaviour and power consumption.
DEVICE ROLE
NODE INFO BROADCAST INTERVAL (seconds, min 3600)
3600 = 1 hour · 86400 = 24 hours
CAUTION — LORA CONFIG CAN MAKE REMOTE NODES UNREACHABLE. Changing region, bandwidth or spread factor to incompatible values on a remote node will prevent it from communicating with your mesh. Test LoRa changes on a local node first. Note the current working settings before making any change.
REMOTE NODE — LoRa config sent over mesh. Requires reboot.
LORA RADIO CONFIGURATION
Use modem preset (recommended — safe defaults per use case)
MODEM PRESET
Long Fast = default for most deployments. Very Long Slow = maximum range, very low throughput.
BANDWIDTH (kHz)
SPREAD FACTOR
CODING RATE

REGION
HOP LIMIT (1-7)
Default 3. Max 7. More hops = more range but more airtime.
TX POWER dBm (0=auto)
REMOTE NODE — Position config sent over mesh. Requires reboot.
POSITION CONFIGURATION
BROADCAST INTERVAL (seconds, min 32)
900 = 15 min · 3600 = 1 hr
How often the node broadcasts its GPS position. Higher = less airtime.
Smart position — reduce broadcasts when the node is stationary
Fixed position — override GPS with a hardcoded location
LATITUDE
LONGITUDE
ALTITUDE (metres)
REMOTE NODE — MQTT config sent over mesh. Requires reboot. This configures MQTT on the node itself, not MeshDash's MQTT connection.
MQTT CONFIGURATION Configures MQTT on the target radio node
This configures the radio node's own MQTT — the node will push packets to your broker directly over WiFi/Internet. This is separate from MeshDash's MQTT connection used for receiving packets.
Enable MQTT on this node
BROKER ADDRESS (host or host:port)
USERNAME
PASSWORD
ROOT TOPIC (optional)
TLS encryption (recommended)
JSON output mode (instead of protobuf)
REMOTE NODE — Sent over mesh. Requires reboot.
DISPLAY SETTINGS
SCREEN ON (seconds, 0 = always on)
UNITS
GPS COORDINATE FORMAT
OLED TYPE
Flip screen 180°
REMOTE NODE — Sent over mesh. Requires reboot.
POWER MANAGEMENT ESP32 sleep settings — not all fields apply to all hardware
LIGHT SLEEP (ls_secs)
Seconds before entering light sleep. 0 = disabled.
SUPER DEEP SLEEP (sds_secs)
Seconds before super deep sleep. 0 = disabled.
MIN WAKE TIME (min_wake_secs)
WAIT FOR BLUETOOTH (secs)
Wait for BT connection before sleeping.
REMOTE NODE — Sent over mesh. Requires reboot. Disabling BT on a remote node may make it harder to manage physically.
BLUETOOTH CONFIG
Bluetooth enabled
PAIRING MODE
FIXED PIN (used when mode = Fixed PIN)
REMOTE NODE — Sent over mesh. Requires reboot.
TELEMETRY CONFIG Environmental/sensor fields only active if hardware present
DEVICE METRICS INTERVAL (seconds)
Battery, voltage, channel utilisation, air util. 0 = default.
ENVIRONMENT METRICS INTERVAL (seconds)
Temperature, humidity, pressure. Requires sensor hardware. 0 = disabled.
AIR QUALITY INTERVAL (seconds)
Requires PM2.5/PM10 sensor. 0 = disabled.
Enable environment measurement
Enable air quality monitoring
REMOTE NODE — Channel data from remote nodes may be stale. Click Load again after 5 seconds. Wrong PSK will break encrypted communication.
CHANNEL MANAGEMENT
Click LOAD CHANNELS to read from the node.
DANGER ZONE — Operations here are destructive and some cannot be undone. All require typed confirmation to prevent accidents. Ensure you know what you are doing before proceeding.
REBOOT Device disconnects and reconnects

Sends a reboot command. Configuration changes that require a reboot will take effect after restart. The device will disconnect briefly then rejoin the mesh. Reboot after saving config changes.

DELAY seconds (0-60)
SHUTDOWN Power off — requires physical restart

Sends a shutdown command. The device will power off completely. It will only restart if physically power-cycled. Only use on devices with a reliable power source reset (e.g. solar nodes).

DELAY seconds
FACTORY RESET⚠ IRREVERSIBLE — All config erased

Permanently erases ALL settings on this device: all channel configurations, owner identity, LoRa settings, position config, MQTT config, security keys. The device must be configured from scratch using physical access. This cannot be undone.

PURGE NODE DATABASE⚠ IRREVERSIBLE — All node history erased

Removes all stored node information from this device's internal database. The device will need to rediscover all nodes through normal mesh operation. Channel settings and device configuration are preserved — only node records are cleared.

OPERATION LOG
No operations yet.
EDIT CHANNEL
CHANNEL NAME
ROLE
PSK (Base64 — leave empty to keep existing key unchanged)
Default LongFast PSK: AQ== · For no encryption: enter a single space then clear it (leave blank)
Uplink (node sends to MQTT)
Downlink (node receives from MQTT)