dandri/HaloKeymind
1
0
Fork 0
mirror of https://github.com/mikecarper/MeshCore.git synced 2026-08-29 10:48:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: f40615ab56

Browse Source
This commit is contained in:
mikecarper
2026-08-10 23:10:42 +00:00
parent d8fa784c0d
commit 78a3775982
3 changed files with 42 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
companion_radio_full/index.html
+14 -5
View File
@@ -1302,6 +1302,11 @@ exist for the exact board variant:</p>
bash build.sh build-firmware RAK_4631_companion_radio_full \
--firmware-version v1.17.0
</code></pre>
<p>To build every available full Companion target, select the corresponding
interactive menu item or run:</p>
<pre><code class="language-bash">bash build.sh build-full-companion-firmwares \
--firmware-version v1.17.0
</code></pre>
<p>Artifacts are written to <code>out/</code> by default.</p>
<p>On 4 MB ESP32 boards, the full target uses a single 3 MB application
partition so WiFi, BLE, WebConfig, and source-only mOTA fit together. Flash
@@ -1388,15 +1393,19 @@ is active; do not enter the start token again after it appears.</p>
<pre><code class="language-text">channels
channel #rgdata Hello from Eugene 👋
to Hilltop Repeater
path A1B2C3,D4E5F6
login my-admin-password
cmd ver
trace
</code></pre>
<p>The <code>to</code> command selects the remote-administration target. Login passwords are
masked during entry and limited by the radio protocol to 15 UTF-8 bytes. Wait
for the asynchronous login result before using <code>cmd</code>; command replies appear
as <code>CLI -&gt; from &lt;name&gt;</code>. Remote ACL permissions determine which commands the
target accepts.</p>
<p>The <code>to</code> command selects the remote-administration target. <code>path</code> shows its
saved outgoing route; <code>path direct</code>, <code>path clear</code>, or a comma-separated list
such as <code>path A1B2C3,D4E5F6</code> changes the route used by subsequent <code>login</code>,
<code>send</code>, and <code>cmd</code> commands. Every hop must use the same 2-, 4-, or 6-digit
hexadecimal width. Login passwords are masked during entry and limited by the
radio protocol to 15 UTF-8 bytes. Wait for the asynchronous login result before
using <code>cmd</code>; command replies appear as <code>CLI -&gt; from &lt;name&gt;</code>. Remote ACL
permissions determine which commands the target accepts.</p>
<p>With no argument, <code>trace</code> uses the current <code>to</code> recipient. A name-prefix
argument traces that contact directly without changing the current recipient.
The contact must already have a known direct path; results show the SNR at each
search/search_index.json
+1 -1
View File
File diff suppressed because one or more lines are too long
terminal_chat_cli/index.html
+27 -2
View File
@@ -1175,12 +1175,36 @@ opening that port from an app.</p>
<pre><code>to {name-prefix}
</code></pre>
<p>Sets the recipient to the <em>first</em> matching contact (in 'list') by the name prefix. (ie. you don't have to type whole name)</p>
<pre><code>path
</code></pre>
<p>Shows the saved outgoing path for the current <code>to</code> recipient. This command and
all path changes require a recipient to be selected first.</p>
<pre><code>path direct
path clear
path {hop-hash[,hop-hash...]}
</code></pre>
<p>Sets the outgoing path used by subsequent <code>login</code>, <code>send</code>, and <code>cmd</code> commands.
<code>direct</code> selects a zero-hop route. <code>clear</code> forgets the saved route, causing the
next operation to use flood routing and allowing normal path discovery to
learn a replacement.</p>
<p>Explicit paths use comma-separated hop hashes. Each hop must contain exactly
2, 4, or 6 hexadecimal digits, and every hop in one path must use the same
width. Spaces around commas and hexadecimal letter case do not matter. The
setting is saved with the selected contact.</p>
<p>For example:</p>
<pre><code class="language-text">to Hilltop Repeater
path A1B2C3,D4E5F6
path
login my-admin-password
</code></pre>
<pre><code>login {admin-password}
</code></pre>
<p>Sends a remote login request to the current recipient. Select a repeater,
room, or other remotely managed node with <code>to {name-prefix}</code> first. The
password is masked with <code>*</code> while it is entered and must be 1-15 UTF-8 bytes;
longer passwords are rejected instead of truncated.</p>
longer passwords are rejected instead of truncated. Login uses the route shown
by <code>path</code>: a known or explicitly set route is direct, while an unknown route is
flooded.</p>
<p>Login results arrive asynchronously. A successful modern response displays
the remote ACL permissions byte and server protocol level. A wrong password,
an unreachable target, or a server that does not support remote login normally
@@ -1237,7 +1261,8 @@ the mirrored examples above. A route that does not return to this node will
eventually report a timeout.</p>
<pre><code>reset path
</code></pre>
<p>Resets the path to current recipient, for new path discovery.</p>
<p>Resets the path to current recipient, for new path discovery. This is retained
as an alias for <code>path clear</code>.</p>
<pre><code>public {text}
</code></pre>
<p>Sends the text message to the built-in <code>Public</code> group channel.</p>