1
0
forked from ctmesh/web

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
This commit is contained in:
2026-06-08 20:31:45 -04:00
parent ed56ce1098
commit e69537c34c
3 changed files with 340 additions and 22 deletions
+24 -2
View File
@@ -323,6 +323,7 @@
<li><a href="#program-path">Programming with a Companion</a></li>
<li class="toc-sub"><a href="#program-needs">Programming Requirements</a></li>
<li class="toc-sub"><a href="#program-repeater">Program the Repeater</a></li>
<li class="toc-sub"><a href="#repeater-commands">Common Repeater Commands</a></li>
<li><a href="#deploy-path">Deploy the Node</a></li>
<li class="toc-sub"><a href="#choose-site">Choose a Good Site</a></li>
<li class="toc-sub"><a href="#tree-mounting">Tree Mounting</a></li>
@@ -441,7 +442,7 @@
<ul>
<li>You can leave location blank for privacy reasons.</li>
<li>If you change the frequency, bandwidth, or spreading factor, the repeater will no longer communicate with nodes on the public mesh, which is usually not what you want.</li>
<li>For the public mesh, set <strong>Flood advert interval (hours)</strong> to <strong>48</strong>. The UI may default lower, such as <strong>12</strong>, so change it before saving.</li>
<li>For the public mesh, set <strong>Flood advert interval (hours)</strong> to <strong>47</strong>. The UI may default lower, such as <strong>12</strong>, so change it before saving.</li>
</ul>
</div>
@@ -463,7 +464,7 @@
<li>This opens the repeater admin status page. Tap <strong>Request status</strong> if you want to refresh and view the repeater status.</li>
<li>At the bottom of that screen, open <strong>Command Line</strong> and run <code>set path.hash.mode 1</code> to set <strong>2 byte mode</strong>. <a href="repeater-hash-mode-entry-iphone.png" class="inline-shot" data-modal-image="repeater-hash-mode-entry-iphone.png">View screenshot</a> <a href="repeater-hash-mode-confirm-iphone.png" class="inline-shot" data-modal-image="repeater-hash-mode-confirm-iphone.png">View result</a></li>
<li>Tap the <strong>Settings</strong> icon in the bottom right next to <strong>Command Line</strong> to change other node settings such as advert intervals, owner info, position, syncing the device clock, and other access control or telemetry settings.</li>
<li>Set <strong>Flood advert interval (hours)</strong> to <strong>48</strong> for best public mesh performance if you have not already set it during USB configuration.</li>
<li>Set <strong>Flood advert interval (hours)</strong> to <strong>47</strong> for best public mesh performance if you have not already set it during USB configuration.</li>
</ol>
<div class="note"><strong>Notes:</strong>
<ul>
@@ -474,11 +475,32 @@
</ul>
</div>
<h3 id="repeater-commands">Common Repeater Commands</h3>
<p>These are the commands CT Mesh operators most commonly use while setting up or checking a repeater from the MeshCore command line. The full upstream reference is available in the <a href="https://docs.meshcore.io/cli_commands/" target="_blank">MeshCore CLI commands documentation</a>.</p>
<div class="note notes-list">
<ul>
<li><code>set path.hash.mode 1</code> - set 2 byte path hash mode for public mesh use.</li>
<li><code>get path.hash.mode</code> - confirm the current path hash mode.</li>
<li><code>set flood.advert.interval 47</code> - set the flood advert interval to 47 hours.</li>
<li><code>get flood.advert.interval</code> - confirm the current flood advert interval.</li>
<li><code>neighbors</code> - list recently heard nearby repeaters.</li>
<li><code>discover.neighbors</code> - actively discover zero-hop neighbors from a repeater.</li>
<li><code>clock sync</code> - sync the repeater clock with the remote device.</li>
<li><code>advert</code> - send a flood advert after setup or after moving the node.</li>
<li><code>powersaving on</code> / <code>powersaving off</code> - enable or disable repeater power saving.</li>
<li><code>reboot</code> - reboot the node after configuration changes that require it.</li>
</ul>
</div>
<h2 id="deploy-path">Deploy the Node</h2>
<h3 id="choose-site">Choose a Good Site</h3>
<ul>
<li>Choose a stable location with useful height, clear exposure, and enough sun to keep the battery healthy.</li>
<li>If your radio site and panel site differ, remote panel placement is fine if it improves sun exposure.</li>
<li>Use <a href="https://bdl.meshmapper.net/" target="_blank">MeshMapper</a> to look for coverage gaps, likely line-of-sight paths, and candidate sites that would help the existing mesh.</li>
<li>Use MeshCore's neighbor discovery tools, including <strong>Discover Nearby Nodes</strong> in the app and the <code>neighbors</code> / <code>discover.neighbors</code> commands, to compare candidate locations before final mounting.</li>
<li>Before sealing the install, test the repeater at the planned location and confirm it can hear useful neighbors and can be heard by the main mesh.</li>
<li>If MQTT/Discord test monitoring is available, send a test message on a channel such as <code>#test</code> from the new repeater area. A Discord bot mirrors received mesh messages into the <a href="https://discord.com/channels/1359317424301801512/1484659122988126339" target="_blank">Discord #test channel</a>, which helps confirm whether the wider mesh can hear the repeater or companion nodes behind it.</li>
</ul>
<h3 id="tree-mounting">Tree Mounting</h3>
<p>For tree installs, a common approach is to use a slingshot to place a lightweight mason line over a suitable branch, then use that line to pull up a stronger rope for hoisting and securing the node. Choose a healthy branch, avoid power lines, and make sure the enclosure and antenna can hang clear without rubbing through on bark or hardware.</p>