MQTT
Connect your node to MQTT
MQTT links meshes over the internet. Messages that reach it can travel far beyond radio range, show up on the community map, and appear on MeshMY’s Telegram channel. There are three ways your node can get there: pick yours below.
New to Meshtastic®? Set up your node first → Its one-tap settings already cover the first method.
How does your node reach MQTT?
Through a nearby gatewayMost peopleYour node sends by radio as usual; a gateway in range uploads your messages to MQTT.
Leave the MQTT module off. What matters is OK to MQTT: it tells gateways they may upload your messages. A gateway in radio range, on the same MediumFast channel, then does the rest. The Join page’s one-tap settings already set everything below.
Radio configuration → LoRa
- OK to MQTT
Onlets gateways upload your messages- Ignore MQTT
Offso you receive messages from MQTT
Radio configuration → Channels → primary channel (MediumFast)
- Uplink enabled
Ononly used if your node is a gateway- Downlink enabled
Ononly used if your node is a gateway
This only works within radio range of a gateway. Check-in message for the weekly net: CRF.
Through your phoneBluetoothYour phone’s mobile data or Wi-Fi carries MQTT, while the Meshtastic app is connected to the node.
Good for a handheld you carry with your phone. The node only reaches MQTT while the app is open and connected over Bluetooth, and your phone has internet.
Radio configuration → LoRa
- OK to MQTT
Onlets gateways upload your messages- Ignore MQTT
Offso you receive messages from MQTT
Radio configuration → Channels → primary channel (MediumFast)
- Uplink enabled
On- Downlink enabled
On
Module configuration → MQTT
- MQTT enabled
On- Address
mqtt.lucifernet.com- Username
meshdev- Password
large4cats- Root topic
msh/MY_919msh/MY_433 if you’re on 433 MHz- Encryption enabled
On- JSON output
Off- TLS
Off- Proxy to client
Onthe phone app carries MQTT
Check-in message for the weekly net: CMQTT.
Through Wi-FiESP32 with Wi-FiThe node joins home Wi-Fi or a phone hotspot and connects to MQTT by itself.
Good for a node that stays put. Only ESP32-based radios have Wi-Fi (for example Heltec V3, LilyGO T-Beam, Station G2). nRF52 radios such as the Heltec T114, LilyGO T-Echo, RAK4631 and SenseCAP P1 don’t.
Turning on Wi-Fi turns off Bluetooth on ESP32, so the phone app can’t connect over Bluetooth afterwards. Set everything else first; afterwards, manage the node over USB or the network.
Radio configuration → Network
- Wi-Fi enabled
On- SSID
(your Wi-Fi or hotspot name)- Password
(its password)
Radio configuration → LoRa
- OK to MQTT
Onlets gateways upload your messages- Ignore MQTT
Offso you receive messages from MQTT
Radio configuration → Channels → primary channel (MediumFast)
- Uplink enabled
On- Downlink enabled
On
Module configuration → MQTT
- MQTT enabled
On- Address
mqtt.lucifernet.com- Username
meshdev- Password
large4cats- Root topic
msh/MY_919msh/MY_433 if you’re on 433 MHz- Encryption enabled
On- JSON output
Off- TLS
Off- Proxy to client
Offthe node connects by itself
Check-in message for the weekly net: CMQTT.
LoRa onlyRadio onlyDisables MQTT: your messages stay within radio range.
This cuts you off from everyone beyond radio range, and from the map and Telegram. Only choose it if you deliberately want to stay off the internet.
Radio configuration → LoRa
- OK to MQTT
Off
Radio configuration → Channels → primary channel
- Uplink enabled
Off- Downlink enabled
Off
Leave the MQTT module off. Check-in message for the weekly net: CRF. With OK to MQTT off, gateways won’t upload it, so it only counts if net control hears you directly by radio.
Check it works on Telegram
- Send a short message on the MediumFast channel.
- Open MeshMY’s public Telegram channel, @MalaysiaMeshtastic. It relays messages that reach MQTT.
- If your message shows up there, your MQTT setup works. Give it a minute or two.
Anyone can follow the channel: install Telegram (free on Android, iOS and desktop), open the link and tap Join.
My message didn’t show up
- Every method: OK to MQTT and uplink are on, and you sent on MediumFast (not the net channel or a direct message).
- Through a gateway: no gateway may have heard you. Check your message got a tick, then try from higher ground.
- Through your phone: the app must stay connected to the node, proxy to client on, and the phone online.
- Through Wi-Fi: the node must have joined Wi-Fi (check the network settings or the node’s screen), and proxy to client off.
You can also look for your node on the community mesh map ↗, which is fed from the same server.
Good to know
Map reporting (optional)
In Module configuration → MQTT, map reporting publishes your node, and its position, to the public Meshtastic map. It’s off unless you turn it on and consent to share. If you do, set how precise a position you’re comfortable sharing.
Using settings from an older guide?
Older community guides are written for LongFast. The mesh now uses MediumFast. In particular, don’t copy Frequency slot 16 or Override frequency 922.875 MHz: they pin the radio to LongFast’s frequency, and it won’t hear anyone on MediumFast. Leave both at their defaults (0), and keep hop limit at 3.
Adapted from the community Meshtastic Setup Guide / Panduan Konfigurasi Meshtastic ↗ (v1.1, June 2025), built on Abang Anonymous’ guide, with thanks to Guzman KH16. Updated for MediumFast.