Our MQTT broker is uplink-only and designed for fixed nodes across the state to serve as gateway nodes. Its purpose is not to bridge gaps or extend mesh coverage, but to report local traffic to our own web-based tools for analytical data and metrics to assess the mesh's performance. This role is best suited for stable, well-placed nodes with reliable coverage.
-MeshCore MQTT uplink uses meshcoretomqtt on a Raspberry Pi or similar Linux computer with the service installed. This configuration stanza goes in your .env.local file after the first two MQTT servers that upload to analyzer.letsmesh.net. This also requires a custom firmware. See custom repeater firmware setup.
MeshCore MQTT uplink uses meshcoretomqtt on a Raspberry Pi or similar Linux computer with the service installed. Configure it with a Toml file at /etc/mctomqtt/config.d/00-user.toml, with region set in your existing [general] section as iata = "BDL", and a custom broker named ctmesh. The block below should be added at the end of the config file. Fill in your own broker credentials. This also requires custom firmware. See custom repeater firmware setup.
# MQTT Broker 3 - CT Mesh -MCTOMQTT_MQTT3_ENABLED=true -MCTOMQTT_MQTT3_SERVER=mqtt.ctmesh.org -MCTOMQTT_MQTT3_PORT=1883 -MCTOMQTT_MQTT3_USE_TLS=false -MCTOMQTT_MQTT3_USERNAME=meshdev -MCTOMQTT_MQTT3_PASSWORD=large4cats+
[[broker]] +name = "ctmesh" +enabled = true +server = "mqtt.ctmesh.org" +port = 1883 +transport = "tcp" +keepalive = 60 +qos = 0 +retain = true + +[broker.auth] +method = "password" +username = "meshdev" +password = "large4cats"
Note: The meshdev/large4cats credentials are intentionally shared secrets for this broker. We recognize the security implications. Specific credentials to this broker can be requested.