The MeshTexas broker accepts connections from any Texas-area MeshCore observer. Auth uses the same JWT model as MeshMapper and Waev — your device signs its own token from its keypair. No credentials or registration required.
mqtt.meshtexas.org443WebSocket Secure (WSS)JWT — auto, from device keypairDevices tagged with a region code that isn't in the list below won't be able to connect. Don't see your area? Let us know and we'll add it.
Select the software your observer is running:
For Heltec V3/V4, T-LoRa, Tracker, and any ESP32-based board running the agessaman MeshCore firmware with MQTT bridge support.
Connect via USB serial at 115200 baud using a terminal (PuTTY, screen, minicom) or the MeshCore serial console.
Open the MeshCore companion app, connect to your device over Bluetooth, then navigate to Remote Management → Command Line — all commands below are entered there, no USB cable needed.
SAT San AntonioAUS AustinHOU HoustonDFW Dallas–Fort WorthELP El PasoABI AbileneAMA AmarilloMFE McAllenSJT San AngeloTXK TexarkanaCRP Corpus ChristiACT Wacoset mqtt.iata SATget mqtt1.preset through get mqtt6.preset and use one that shows none.mqtt1 with your chosen slot:set mqtt1.preset custom
set mqtt1.server mqtt.meshtexas.org
set mqtt1.port 443
set mqtt1.audience mqtt.meshtexas.org
save
rebootget mqtt.statusYou should see mqtt1: connected.For RAK4631 and any serial-connected MeshCore device running meshcoretomqtt.
/etc/mctomqtt/config.d/ on Linux.SAT with the Texas city nearest to you, then expand the option that matches your setup:SAT San AntonioAUS AustinHOU HoustonDFW Dallas–Fort WorthELP El PasoABI AbileneAMA AmarilloMFE McAllenSJT San AngeloTXK TexarkanaCRP Corpus ChristiACT WacoSets IATA only for the MeshTexas broker — safe when you're also connected to other regional meshes. Create 30-texasmesh.toml in config.d/:
[[broker]]
name = "meshtexas"
enabled = true
server = "mqtt.meshtexas.org"
port = 443
transport = "websockets"
keepalive = 60
qos = 0
retain = true
[broker.tls]
enabled = true
verify = true
[broker.auth]
method = "token"
audience = "mqtt.meshtexas.org"
[broker.topics]
iata = "SAT"Simpler option — sets IATA globally. Create or edit /etc/mctomqtt/config.d/99-user.toml:
[general]
iata = "SAT"Then create 30-texasmesh.toml in config.d/ without a [broker.topics] block:
[[broker]]
name = "meshtexas"
enabled = true
server = "mqtt.meshtexas.org"
port = 443
transport = "websockets"
keepalive = 60
qos = 0
retain = true
[broker.tls]
enabled = true
verify = true
[broker.auth]
method = "token"
audience = "mqtt.meshtexas.org"sudo systemctl restart meshcoretomqtt
journalctl -u meshcoretomqtt -fRun ls /etc/mctomqtt/config.d/ to see what files already exist before picking a number.
For any MeshCore observer running meshcore-packet-capture.
SAT with the Texas city nearest to you, then expand the option that matches your setup:SAT San AntonioAUS AustinHOU HoustonDFW Dallas–Fort WorthELP El PasoABI AbileneAMA AmarilloMFE McAllenSJT San AngeloTXK TexarkanaCRP Corpus ChristiACT WacoSets IATA only for the MeshTexas broker — safe when you're also connected to other regional meshes. Create meshtexas.toml in your presets directory:
[[broker]]
name = "meshtexas"
enabled = true
server = "mqtt.meshtexas.org"
port = 443
transport = "websockets"
keepalive = 60
qos = 0
retain = true
iata = "SAT"
[broker.tls]
enabled = true
verify = true
[broker.auth]
method = "token"
audience = "mqtt.meshtexas.org"Simpler option — sets IATA globally. Create or edit /etc/meshcore-packet-capture/config.d/99-user.toml:
[general]
iata = "SAT"Then create meshtexas.toml in your presets directory without an iata line:
[[broker]]
name = "meshtexas"
enabled = true
server = "mqtt.meshtexas.org"
port = 443
transport = "websockets"
keepalive = 60
qos = 0
retain = true
[broker.tls]
enabled = true
verify = true
[broker.auth]
method = "token"
audience = "mqtt.meshtexas.org"After connecting, search for your node name on the MeshTexas Analyzer. It should appear within a few minutes of your device sending its first advert packet.
Open Analyzer ↗