We run a local MQTT server here in Brisbane. It runs in a real datacenter, with real UPS/generator and redundant connectivity… so it will probably, usually work in most SHTF-type scenarios.
It was put to the test during the Cyclone of early 2025 and it made it all the way through. That said, MQTT doesn't work on a per-node basis without internet… so it is of course, secondary to LoRa based connectivity.
If you'd like to connect your node to MQTT - here are the settings you'll need!
Required Settings
| Server | mqtt.mbug.com.au |
| Username | mbug |
| Password | small4dogs |
| Root Topic | msh/ANZ |
Recommended Settings
| Encryption Enabled | Yes |
| JSON Output Enabled | Yes |
| TLS Enabled | (Depends, see below) |
| Map Reporting | Enabled |
TLS Enabled:
Depending on your node hardware, this option may or may not work. The MQTT server does support both TLS and non-TLS connections, but NRF nodes and (surprisingly) Linux MeshtasticD nodes may not support it.
It's ideal to have it on if your node supports it, but if you find it won't work, it's fine to leave it disabled.
Clarification on encryption/TLS:
If your MQTT setting keeps disabling itself, or if you find your messages aren't reaching the MQTT server (or vice-versa) – the best way to debug it is to connect your node to your computer, and use the Meshtastic python client command…
meshtastic --noproto
If you run this while the node boots, you will see it log various things like connecting to WiFi (if applicable), then connecting to the MQTT server. If there are any errors, they will be shown here.