A node shows up on meshmap.net when it publishes its position to Meshtastic’s public MQTT server through the default channel, with “OK to MQTT” on and an imprecise (blurred) location. The map refreshes every minute and drops nodes that haven’t sent a position for 8 hours.
MQTT is a lightweight publish/subscribe messaging protocol. A Meshtastic node with internet access can copy (“uplink”) the packets it sees to an MQTT server, where maps and other tools pick them up. Meshtastic runs a public server:
| Setting | Default |
|---|---|
| Server | mqtt.meshtastic.org |
| Username / password | meshdev / large4cats (public, shared by everyone) |
| Root topic | msh/NP_865 in Nepal (msh/<REGION>) |
| Topic for a node’s packets | msh/NP_865/2/e/LongFast/!<nodeid> |
Docs: MQTT module settings · MQTT integration.
From the meshmap.net README:
AQ==)lora.config_ok_to_mqtt)meshtastic --set network.wifi_enabled true --set network.wifi_ssid "YourWiFi" --set network.wifi_psk "YourPassword"
meshtastic --set bluetooth.enabled false --set paxcounter.enabled false
meshtastic --set mqtt.enabled true --set mqtt.map_reporting_enabled true --set lora.config_ok_to_mqtt true
meshtastic --ch-index 0 --ch-set uplink_enabled true --ch-set module_settings.position_precision 13
meshtastic --setlat 27.70 --setlon 85.32 # a fixed position (example: central Kathmandu)
Or click Map reporter in the control panel. It never touches your WiFi name or password, so set those once with the CLI or the web client.
mqtt.proxy_to_client_enabled). This is less tested.Next: The control panel →