From 4ac6b2d7ab86e66627d7e64688b10e8bb0480184 Mon Sep 17 00:00:00 2001
From: Jared Dunbar <jrddunbr@ja4.org>
Date: Sat, 7 Mar 2026 11:12:09 -0500
Subject: [PATCH] Updated MQTT configuration information

---
 meshcore-resources.html | 24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)

diff --git a/meshcore-resources.html b/meshcore-resources.html
index 5046a28..aff561e 100644
--- a/meshcore-resources.html
+++ b/meshcore-resources.html
@@ -233,18 +233,26 @@
 
     <h2>MQTT</h2>
     <p>Our MQTT broker is <em>uplink-only</em> 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. <strong>This role is best suited for stable, well-placed nodes with reliable coverage.</strong></p>
-    <p>MeshCore MQTT uplink uses <a href="https://github.com/Cisien/meshcoretomqtt" target="_blank">meshcoretomqtt</a> on a Raspberry Pi or similar Linux computer with the service installed. This configuration stanza goes in your <code>.env.local</code> file after the first two MQTT servers that upload to analyzer.letsmesh.net. <strong>This also requires a custom firmware.</strong> See <a href="https://analyzer.letsmesh.net/observer/onboard" target="_blank">custom repeater firmware setup</a>.</p>
+    <p>MeshCore MQTT uplink uses <a href="https://github.com/Cisien/meshcoretomqtt" target="_blank">meshcoretomqtt</a> on a Raspberry Pi or similar Linux computer with the service installed. Configure it with a <a href="https://github.com/Cisien/meshcoretomqtt" target="_blank">Toml file</a> at <code>/etc/mctomqtt/config.d/00-user.toml</code>, with region set in your existing <code>[general]</code> section as <code>iata = "BDL"</code>, and a custom broker named <code>ctmesh</code>. The block below should be added at the end of the config file. Fill in your own broker credentials. <strong>This also requires custom firmware.</strong> See <a href="https://analyzer.letsmesh.net/observer/onboard" target="_blank">custom repeater firmware setup</a>.</p>
 
     <div class="code-block">
       <button class="copy-btn" type="button" data-copy-target="meshcore-mqtt">Copy all</button>
-      <pre id="meshcore-mqtt"># 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</pre>
+      <pre id="meshcore-mqtt">[[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"</pre>
     </div>
+    <p class="note"><strong>Note:</strong> The <code>meshdev</code>/<code>large4cats</code> credentials are intentionally shared secrets for this broker. We recognize the security implications. Specific credentials to this broker can be requested.</p>
 
     <a class="btn back-link" href="index.html">Back to CT Mesh</a>
     <footer class="site-footer">