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 KEYPaste 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 REQUIREDOne-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.
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 IDENTITYBroadcast to mesh on change · Max 39 / 4 chars
Full display name shown in node lists and messages. Max 39 characters.
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
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)
Long Fast = default for most deployments. Very Long Slow = maximum range, very low throughput.
Default 3. Max 7. More hops = more range but more airtime.
REMOTE NODE — Position config sent over mesh. Requires reboot.
POSITION CONFIGURATION
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
REMOTE NODE — MQTT config sent over mesh. Requires reboot. This configures MQTT on the node itself, not MeshDash's MQTT connection.
MQTT CONFIGURATIONConfigures 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
TLS encryption (recommended)
JSON output mode (instead of protobuf)
REMOTE NODE — Sent over mesh. Requires reboot.
DISPLAY SETTINGS
Flip screen 180°
REMOTE NODE — Sent over mesh. Requires reboot.
POWER MANAGEMENTESP32 sleep settings — not all fields apply to all hardware
Seconds before entering light sleep. 0 = disabled.
Seconds before super deep sleep. 0 = disabled.
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
REMOTE NODE — Sent over mesh. Requires reboot.
TELEMETRY CONFIGEnvironmental/sensor fields only active if hardware present
Battery, voltage, channel utilisation, air util. 0 = default.
Temperature, humidity, pressure. Requires sensor hardware. 0 = disabled.
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.
REBOOTDevice 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.
seconds (0-60)
SHUTDOWNPower 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).
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.