jared/web
1
0
Fork 0
forked from ctmesh/web
Code Pull Requests Activity

Refine MeshCore repeater setup guidance

Browse Source 
* 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
This commit is contained in:
Jared Dunbar
2026-06-08 20:31:45 -04:00
parent ed56ce1098
commit e69537c34c
3 changed files with 340 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
meshcore-resources.html
+3 -20
View File
@@ -261,31 +261,14 @@
<h2>Official Links</h2>
<p><a href="https://meshcore.io/" target="_blank">meshcore.io</a></p>
<p><a href="https://flasher.meshcore.io/" target="_blank">flasher.meshcore.io</a></p>
<p><a href="https://docs.meshcore.io/cli_commands/" target="_blank">MeshCore CLI commands reference</a></p>
<p><a href="repeater-setup.html">CT Mesh repeater setup guide</a></p>
<div class="note"><strong>Note:</strong> the flasher requires WebSerial or Web Bluetooth support in your browser</div>
<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. 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">[[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>
<p>For setup steps, see <a href="meshcore-mqtt-upload.html">How to configure your repeater to upload to the CT Mesh MQTT system</a>.</p>
<p class="note"><strong>Testing note:</strong> MQTT messages sent to channels such as <code>#test</code> are mirrored into the <a href="https://discord.com/channels/1359317424301801512/1484659122988126339" target="_blank">Discord #test channel</a> 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.</p>
<a class="btn back-link" href="index.html">Back to CT Mesh</a>
<footer class="site-footer">