From e69537c34c12cce153c38000d11cb8fe418f1b16 Mon Sep 17 00:00:00 2001 From: Jared Dunbar Date: Mon, 8 Jun 2026 20:31:45 -0400 Subject: [PATCH] Refine MeshCore repeater setup guidance * Add a dedicated CT Mesh MQTT upload configuration page * Link the resources page to the MQTT upload guide and MeshCore CLI command reference * Add common repeater commands, MeshMapper, neighbor discovery, and Discord #test validation guidance * Update the recommended flood advert interval to 47 hours --- meshcore-mqtt-upload.html | 313 ++++++++++++++++++++++++++++++++++++++ meshcore-resources.html | 23 +-- repeater-setup.html | 26 +++- 3 files changed, 340 insertions(+), 22 deletions(-) create mode 100644 meshcore-mqtt-upload.html diff --git a/meshcore-mqtt-upload.html b/meshcore-mqtt-upload.html new file mode 100644 index 0000000..bcc5062 --- /dev/null +++ b/meshcore-mqtt-upload.html @@ -0,0 +1,313 @@ + + + + + + Configure MeshCore MQTT Upload | CT Mesh + + + + + + + + + +
+
+
+ + CT Mesh + +
+

How to Configure Your Repeater to Upload to the CT Mesh MQTT System

+

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 also requires custom observer firmware on the radio. See custom repeater firmware setup before configuring the broker.

+ +

Configuration

+

Configure meshcoretomqtt with a Toml file at /etc/mctomqtt/config.d/00-user.toml. In your existing [general] section, set the region to iata = "BDL". Then add the custom broker block below at the end of the config file. Fill in your own broker credentials if you were issued dedicated credentials.

+ +
+ + 
[[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.

+ +

Testing

+

After the service is running, check the MeshCore Map, MeshMapper, and MeshCore Analyzer to confirm that traffic from the repeater is being reported.

+

MQTT messages sent to channels such as #test are also mirrored into the Discord #test channel by a bot. This gives you a quick way to test whether the main areas of the mesh can hear your new repeater, and whether companion nodes behind the repeater are making it through.

+ +

Related Guides

+

CT Mesh repeater setup guide

+

MeshCore resources

+ + Back to CT Mesh + +
+ + + diff --git a/meshcore-resources.html b/meshcore-resources.html index d40c210..d76a633 100644 --- a/meshcore-resources.html +++ b/meshcore-resources.html @@ -261,31 +261,14 @@

Official Links

meshcore.io

flasher.meshcore.io

+

MeshCore CLI commands reference

CT Mesh repeater setup guide

Note: the flasher requires WebSerial or Web Bluetooth support in your browser

MQTT

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. 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.

- -
- - 
[[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.

+

For setup steps, see How to configure your repeater to upload to the CT Mesh MQTT system.

+

Testing note: MQTT messages sent to channels such as #test are mirrored into the Discord #test channel by a bot. This is useful for checking whether the main mesh can hear a new repeater, or whether companion nodes behind that repeater are making it back to the wider mesh.

Back to CT Mesh