## Admin login

Enter this node's admin password (the same one used for remote CLI admin).

Password
In the WiFi sign-in popup? It closes if your phone sleeps. Open in your browser to keep your progress.

## Step 1 · WiFi

Connect this node to your WiFi network so it can reach the MQTT servers.

Network name (SSID)
Password
Leave blank for an open network. 2.4 GHz networks only.
Node name
Shown on the mesh and in MQTT status messages.

## Step 2 · Radio

Nodes only hear each other on identical radio settings. Pick the preset your local mesh uses.

Region preset
TX power (dBm)
Maximum legal power varies by region — check local rules.
Repeat Forward mesh traffic. Off = listen-only (still observes and publishes).
Need settings that aren't listed? Choose Keep current settings, finish setup, then fine-tune in the Advanced editor.

## Step 3 · MQTT

Observer name (origin)
How this observer identifies itself in published status/packet messages. Informational only — not used for topics or authentication. Prefilled with the node name.
IATA region code
Nearest airport code, e.g. DEN. Used in topic paths.
Owner public key
Optional — 64-char hex public key of your companion node. Included in auth JWTs so services that support it can let you claim this node.
Owner email
Optional — also included in auth JWTs for claiming this node on some services.

## Servers

## Step 4 · Review & save

Saving reboots the node into normal operation. To change settings later, run start webconfig from the serial console.

Advanced editor

## Node

Name
Latitude
Longitude

## LoRa radio reboot to apply

Frequency, bandwidth, SF and CR must match your mesh exactly — a wrong value takes this node off the air until fixed over serial.
Frequency (MHz)
Bandwidth (kHz)
Spreading factor
Coding rate
TX power (dBm)

## Advanced

Airtime factor
RX delay base
TX delay factor
CAD (listen before transmit)Channel activity detection
RX boosted gain SX126x receivers only
Repeat Forward mesh traffic. Off = listen-only (still observes and publishes).
Local advert (min)
0 = off
Flood advert (hrs)
0 = off, else 3–168

## Flooding & loops

Hop limits for flood traffic this node forwards. Lower values contain noisy neighbours; too low takes parts of the mesh out of reach.
Max flood hops
0–64. Default 64.
Max advert hops
0–64. Default 8.
Max unscoped flood hops
Applies to packets with no region scope. 0–64.
Loop detection
Drops flood packets that already carry this node's hash. Stricter = fewer repeats tolerated before dropping.

## Identity

Observer name (origin)
How this observer identifies itself in published messages; informational only. Blank = node name.
IATA region code
Owner public key
64-char hex public key of the owner's companion node (optional).
Owner email

## Publishing

This node only ever uploads to MQTT — nothing from a broker is injected into the mesh.
Node status Periodic health/stats to the status topic
Publish packets Master switch for all packet traffic below
Add raw frames Also send the full hex frame to the raw topic
Received packets Report packets heard over the air
Publish neighbors Periodic neighbor table + scopes (PSRAM boards only)
Transmitted packets
Report packets this node sends.
Status interval (min)
Neighbors interval (hours)
How often to publish the neighbor table (12-336, default 24).

## Servers

## Time & SNMP

NTP server
Enter none to clear.
Timezone (POSIX)
UTC offset
SNMP agent Restart required
SNMP community

## WiFi connection

Changing WiFi restarts the connection — this page will drop and the node reappears on the new network. Find its new IP from your router or the serial console.
Network name (SSID)
Password
Power save

## Maintenance

## Device

## Free heap (KB)

## Noise floor (dBm)

## MQTT servers

No data yet.
Nearby networks

# Continue in your browser

1. Tap Done (or Cancel) in the corner of this window.
   If asked, choose Use Without Internet / Stay connected.
2. Open Safari or Chrome on this device.
3. Go to http://192.168.4.1

Stay connected to the MeshCore-Setup WiFi network. Your progress here isn't carried over — the setup restarts in the browser, where it survives the screen locking.

Go back

# Rebooting…