mirror of
https://github.com/meshcore-dev/MeshCore.git
synced 2026-08-14 09:29:49 +00:00
deploy: 727fc0512c
This commit is contained in:
ripplebiz
+136
-1
@@ -738,6 +738,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#view-or-change-the-lora-fem-receive-path-gain-state-on-supported-boards" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
View or change the LoRa FEM receive-path gain state on supported boards
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -1003,6 +1014,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#enable-or-disable-hardware-channel-activity-detection-cad" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Enable or disable hardware Channel Activity Detection (CAD)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1544,6 +1566,34 @@
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#ethernet-when-ethernet-support-is-compiled-in" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Ethernet (when Ethernet support is compiled in)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Ethernet (when Ethernet support is compiled in)">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#view-ethernet-connection-status" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
View Ethernet connection status
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -2308,6 +2358,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#view-or-change-the-lora-fem-receive-path-gain-state-on-supported-boards" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
View or change the LoRa FEM receive-path gain state on supported boards
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -2573,6 +2634,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#enable-or-disable-hardware-channel-activity-detection-cad" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Enable or disable hardware Channel Activity Detection (CAD)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -3114,6 +3186,34 @@
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#ethernet-when-ethernet-support-is-compiled-in" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Ethernet (when Ethernet support is compiled in)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Ethernet (when Ethernet support is compiled in)">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#view-ethernet-connection-status" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
View Ethernet connection status
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -3167,6 +3267,7 @@
|
||||
<li><a href="#gps-when-gps-support-is-compiled-in">GPS</a></li>
|
||||
<li><a href="#sensors-when-sensor-support-is-compiled-in">Sensors</a></li>
|
||||
<li><a href="#bridge-when-bridge-support-is-compiled-in">Bridge</a></li>
|
||||
<li><a href="#ethernet-when-ethernet-support-is-compiled-in">Ethernet</a></li>
|
||||
</ul>
|
||||
<hr />
|
||||
<h2 id="operational">Operational</h2>
|
||||
@@ -3329,6 +3430,16 @@
|
||||
<p><strong>Default:</strong> <code>on</code></p>
|
||||
<p><strong>Temporary Note:</strong> If you upgraded from an older version to 1.14.1 without erasing flash, this setting is <code>off</code> because of <a href="https://github.com/meshcore-dev/MeshCore/issues/2118">#2118</a></p>
|
||||
<hr />
|
||||
<h4 id="view-or-change-the-lora-fem-receive-path-gain-state-on-supported-boards">View or change the LoRa FEM receive-path gain state on supported boards</h4>
|
||||
<p><strong>Usage:</strong>
|
||||
- <code>get radio.fem.rxgain</code>
|
||||
- <code>set radio.fem.rxgain <state></code></p>
|
||||
<p><strong>Parameters:</strong>
|
||||
- <code>state</code>: <code>on</code>|<code>off</code></p>
|
||||
<p><strong>Notes:</strong>
|
||||
- This controls the external LoRa FEM receive-path LNA where the board supports it.
|
||||
- This is separate from <code>radio.rxgain</code>, which controls the radio chip receive gain mode.</p>
|
||||
<hr />
|
||||
<h3 id="system">System</h3>
|
||||
<h4 id="view-or-change-this-nodes-name">View or change this node's name</h4>
|
||||
<p><strong>Usage:</strong>
|
||||
@@ -3338,7 +3449,7 @@
|
||||
- <code>name</code>: Node name</p>
|
||||
<p><strong>Set by build flag:</strong> <code>ADVERT_NAME</code></p>
|
||||
<p><strong>Default:</strong> Varies by board</p>
|
||||
<p><strong>Note:</strong> Max length varies. If a location is set, the max length is 24 bytes; 32 otherwise. Emoji and unicode characters may take more than one byte.</p>
|
||||
<p><strong>Note:</strong> Advertised names can use up to 23 bytes when location is included and 31 bytes otherwise. Emoji and Unicode characters may take more than one byte. Names that exceed the available advert space are truncated at a valid UTF-8 code point boundary.</p>
|
||||
<hr />
|
||||
<h4 id="view-or-change-this-nodes-latitude">View or change this node's latitude</h4>
|
||||
<p><strong>Usage:</strong>
|
||||
@@ -3531,6 +3642,15 @@
|
||||
- <code>value</code>: Interference threshold value</p>
|
||||
<p><strong>Default:</strong> <code>0.0</code></p>
|
||||
<hr />
|
||||
<h4 id="enable-or-disable-hardware-channel-activity-detection-cad">Enable or disable hardware Channel Activity Detection (CAD)</h4>
|
||||
<p><strong>Usage:</strong>
|
||||
- <code>get cad</code>
|
||||
- <code>set cad <on|off></code></p>
|
||||
<p><strong>Description:</strong> When enabled, the radio performs a hardware Channel Activity Detection scan before transmitting and defers if the channel is busy. Runs independently of <code>int.thresh</code> — either, both, or none may be active.</p>
|
||||
<p><strong>Parameters:</strong>
|
||||
- <code>on|off</code>: Enable or disable hardware CAD</p>
|
||||
<p><strong>Default:</strong> <code>off</code></p>
|
||||
<hr />
|
||||
<h4 id="view-or-change-the-agc-reset-interval">View or change the AGC Reset Interval</h4>
|
||||
<p><strong>Usage:</strong>
|
||||
- <code>get agc.reset.interval</code>
|
||||
@@ -3904,6 +4024,21 @@ region save
|
||||
<p><strong>Usage:</strong> <code>get pwrmgt.bootmv</code></p>
|
||||
<p><strong>Note:</strong> Returns an error on boards without power management support.</p>
|
||||
<hr />
|
||||
<h3 id="ethernet-when-ethernet-support-is-compiled-in">Ethernet (when Ethernet support is compiled in)</h3>
|
||||
<p>Ethernet support is available on RAK4631 boards with a RAK13800 (W5100S) Ethernet module. Use the <code>_ethernet</code> firmware variants (e.g. <code>RAK_4631_repeater_ethernet</code>) to enable this feature.</p>
|
||||
<hr />
|
||||
<h4 id="view-ethernet-connection-status">View Ethernet connection status</h4>
|
||||
<p><strong>Usage:</strong>
|
||||
- <code>eth.status</code></p>
|
||||
<p><strong>Output:</strong>
|
||||
- <code>ETH: <ip>:<port></code> when connected (e.g. <code>ETH: 192.168.1.50:23</code>)
|
||||
- <code>ETH: not connected</code> when Ethernet is not active</p>
|
||||
<p><strong>Notes:</strong>
|
||||
- Available on repeater and room server firmware only. Companion radio ethernet firmware does not expose a CLI.
|
||||
- The Ethernet interface obtains an IP address via DHCP automatically on boot.
|
||||
- A TCP server listens on port 23 (default) for CLI connections.
|
||||
- Connect with any TCP client (e.g. <code>nc</code>, PuTTY) to access the same CLI available over serial.</p>
|
||||
<hr />
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1320,6 +1320,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#78-q-how-do-i-use-ethernet-with-a-rak4631" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
7.8. Q: How do I use Ethernet with a RAK4631?
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -2504,6 +2515,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#78-q-how-do-i-use-ethernet-with-a-rak4631" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
7.8. Q: How do I use Ethernet with a RAK4631?
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -2636,6 +2658,7 @@
|
||||
<li><a href="#75-q-what-is-the-format-of-a-contact-or-channel-qr-code">7.5. Q: What is the format of a contact or channel QR code?</a></li>
|
||||
<li><a href="#76-q-how-do-i-connect-to-the-companion-via-wi-fi-eg-using-a-heltec-v3">7.6. Q: How do I connect to the companion via Wi-Fi, e.g. using a Heltec V3?</a></li>
|
||||
<li><a href="#77-q-i-have-a-station-g2-or-a-heltec-v4-or-an-ikoka-stick-or-a-radio-with-an-ebyte-e22-900m30s-or-an-ebyte-e22-900m33s-module-what-should-their-transmit-power-be-set-to">7.7. Q: I have a Station G2, or a Heltec V4, or an Ikoka Stick, or a radio with an EByte E22-900M30S or an EByte E22-900M33S module, what should their transmit power be set to?</a></li>
|
||||
<li><a href="#78-q-how-do-i-use-ethernet-with-a-rak4631">7.8. Q: How do I use Ethernet with a RAK4631?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
@@ -3277,6 +3300,26 @@ For companion radios, you can set these radios' transmit power in the smartphone
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<hr />
|
||||
<h3 id="78-q-how-do-i-use-ethernet-with-a-rak4631">7.8. Q: How do I use Ethernet with a RAK4631?</h3>
|
||||
<p><strong>A:</strong>
|
||||
MeshCore supports Ethernet on RAK4631 boards using the <a href="https://docs.rakwireless.com/product-categories/wisblock/rak13800/datasheet/">RAK13800</a> WisBlock Ethernet module (based on the W5100S chip).</p>
|
||||
<p><strong>Hardware required:</strong>
|
||||
- RAK4631 WisBlock Core
|
||||
- RAK19007 or RAK19018 WisBlock Base Board (with an available IO slot)
|
||||
- RAK13800 WisBlock Ethernet module
|
||||
- Ethernet cable connected to a network with a DHCP server</p>
|
||||
<p><strong>Firmware:</strong>
|
||||
Flash one of the Ethernet-enabled firmware variants:
|
||||
- <code>RAK_4631_repeater_ethernet</code> - Repeater with Ethernet CLI access
|
||||
- <code>RAK_4631_room_server_ethernet</code> - Room server with Ethernet CLI access
|
||||
- <code>RAK_4631_companion_radio_ethernet</code> - Companion radio over Ethernet (replaces BLE)</p>
|
||||
<p><strong>Connecting:</strong>
|
||||
- The device obtains an IP address via DHCP automatically on boot.
|
||||
- For repeaters and room servers, connect to the device on TCP port 23 using any TCP client (e.g. <code>nc <ip> 23</code> or PuTTY in raw mode). This gives you the same CLI available over serial/USB.
|
||||
- For companion radio firmware, the Ethernet interface replaces BLE as the transport to companion apps. Connect on TCP port 5000 (same as the WiFi companion radio).
|
||||
- Use the <code>eth.status</code> CLI command to check connection status and see the assigned IP address.</p>
|
||||
<hr />
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -491,6 +491,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#host-output-backpressure" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Host Output Backpressure
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1046,6 +1057,17 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#host-output-backpressure" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Host Output Backpressure
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1414,7 +1436,7 @@
|
||||
<td>Data</td>
|
||||
<td><code>0x00</code></td>
|
||||
<td>Raw packet</td>
|
||||
<td>Queue packet for transmission</td>
|
||||
<td>Queue packet for transmission (one pending at a time)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>TXDELAY</td>
|
||||
@@ -1480,6 +1502,9 @@
|
||||
</tbody>
|
||||
</table>
|
||||
<p>Data frames carry raw packet data only, with no metadata prepended. The Data command payload is limited to 255 bytes to match the MeshCore maximum transmission unit (MAX_TRANS_UNIT); frames larger than 255 bytes are silently dropped. The KISS specification recommends at least 1024 bytes for general-purpose TNCs; this modem is intended for MeshCore packets only, whose protocol MTU is 255 bytes.</p>
|
||||
<p>Only one packet may be pending for radio transmission at a time. If the host sends a second Data frame before the first has completed, the modem responds with Error (0xF1) and TxBusy (0x07).</p>
|
||||
<h3 id="host-output-backpressure">Host Output Backpressure</h3>
|
||||
<p>Outbound frames are encoded into a 2-slot queue and flushed when serial output space is available; <code>loop()</code> never blocks on writes. Radio TX state advances independently of host read speed. TxDone is retained until it can be queued. If the outbound queue is full, the modem responds with Error (0xF1) and TxBusy (0x07). Hosts should read serial promptly to avoid delayed responses.</p>
|
||||
<h3 id="csma-behavior">CSMA Behavior</h3>
|
||||
<p>The TNC implements p-persistent CSMA for half-duplex operation:</p>
|
||||
<ol>
|
||||
@@ -1825,14 +1850,14 @@
|
||||
<tr>
|
||||
<td>TxBusy</td>
|
||||
<td><code>0x07</code></td>
|
||||
<td>Transmit busy</td>
|
||||
<td>Radio TX busy, or host output queue full</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="unsolicited-events">Unsolicited Events</h3>
|
||||
<p>The TNC sends these SetHardware frames without a preceding request:</p>
|
||||
<p><strong>TxDone (0xF8)</strong>: Sent after a packet has been transmitted. Contains a single byte: 0x01 for success, 0x00 for failure.</p>
|
||||
<p><strong>RxMeta (0xF9)</strong>: Sent immediately after each standard data frame (type 0x00) with metadata for the received packet. Contains SNR (1 byte, signed, value x4 for 0.25 dB precision) followed by RSSI (1 byte, signed, dBm). Enabled by default; can be toggled with SetSignalReport. Standard KISS clients ignore this frame.</p>
|
||||
<p><strong>TxDone (0xF8)</strong>: Sent after radio transmission completes. Contains a single byte: 0x01 for success, 0x00 for failure. Delivery to the host may be delayed under serial backpressure but is not dropped.</p>
|
||||
<p><strong>RxMeta (0xF9)</strong>: Sent after each standard data frame (type 0x00) with SNR (1 byte, signed, value x4) and RSSI (1 byte, signed, dBm). Queued with the data frame; omitted if the data frame cannot be queued. Enabled by default; toggle with SetSignalReport. Standard KISS clients ignore this frame.</p>
|
||||
<h2 id="data-formats">Data Formats</h2>
|
||||
<h3 id="radio-parameters-setradio-radio-response">Radio Parameters (SetRadio / Radio response)</h3>
|
||||
<p>All values little-endian.</p>
|
||||
|
||||
@@ -655,6 +655,16 @@
|
||||
<td>ripple_biz@protonmail.com — https://buymeacoffee.com/ripplebiz</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>0120</td>
|
||||
<td>MCO Advanced</td>
|
||||
<td>most.original.address@gmail.com — https://hdden.ru/MCOa/</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>0130 - 013F</td>
|
||||
<td>StreamSensor</td>
|
||||
<td>william@housedillon.com - https://housedillon.com/blog/lora-e5-with-seeed-fusion</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>FF00 - FFFF</td>
|
||||
<td>-reserved for testing/dev-</td>
|
||||
<td></td>
|
||||
|
||||
+646
-26
@@ -537,6 +537,316 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#node-advertisement" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Node advertisement
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#acknowledgement" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Acknowledgement
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#returned-path-request-response-and-plain-text-message" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Returned path, request, response, and plain text message
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Returned path, request, response, and plain text message">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#returned-path" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Returned path
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Request">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-stats" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get stats
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-telemetry-data" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get telemetry data
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-telemetry" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Telemetry
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-minmaxave-sensor-nodes" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Min/Max/Ave (Sensor nodes)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-access-list" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Access List
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-neighbors" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Neighbors
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-owner-info" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Owner Info
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#response" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Response
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#plain-text-message" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Plain text message
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#anonymous-request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Anonymous request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Anonymous request">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#room-server-login" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Room server login
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#repeatersensor-login" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Repeater/Sensor login
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#repeater-regions-request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Repeater - Regions request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#repeater-owner-info-request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Repeater - Owner info request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#repeater-clock-and-status-request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Repeater - Clock and status request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#group-text-message" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Group text message
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#group-datagram" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Group datagram
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#control-data" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Control data
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Control data">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#discover_req-sub_type" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
DISCOVER_REQ (sub_type)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#discover_resp-sub_type" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
DISCOVER_RESP (sub_type)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#custom-packet" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Custom packet
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -663,6 +973,316 @@
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#node-advertisement" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Node advertisement
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#acknowledgement" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Acknowledgement
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#returned-path-request-response-and-plain-text-message" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Returned path, request, response, and plain text message
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Returned path, request, response, and plain text message">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#returned-path" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Returned path
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Request">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-stats" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get stats
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-telemetry-data" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get telemetry data
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-telemetry" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Telemetry
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-minmaxave-sensor-nodes" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Min/Max/Ave (Sensor nodes)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-access-list" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Access List
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-neighbors" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Neighbors
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#get-owner-info" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Get Owner Info
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#response" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Response
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#plain-text-message" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Plain text message
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#anonymous-request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Anonymous request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Anonymous request">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#room-server-login" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Room server login
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#repeatersensor-login" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Repeater/Sensor login
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#repeater-regions-request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Repeater - Regions request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#repeater-owner-info-request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Repeater - Owner info request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#repeater-clock-and-status-request" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Repeater - Clock and status request
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#group-text-message" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Group text message
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#group-datagram" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Group datagram
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#control-data" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Control data
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Control data">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#discover_req-sub_type" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
DISCOVER_REQ (sub_type)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#discover_resp-sub_type" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
DISCOVER_RESP (sub_type)
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#custom-packet" class="md-nav__link">
|
||||
<span class="md-ellipsis">
|
||||
|
||||
Custom packet
|
||||
|
||||
</span>
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -712,7 +1332,7 @@
|
||||
<ul>
|
||||
<li>Node hash: the first byte of the node's public key</li>
|
||||
</ul>
|
||||
<h1 id="node-advertisement">Node advertisement</h1>
|
||||
<h2 id="node-advertisement">Node advertisement</h2>
|
||||
<p>This kind of payload notifies receivers that a node exists, and gives information about the node</p>
|
||||
<table>
|
||||
<thead>
|
||||
@@ -839,7 +1459,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h1 id="acknowledgement">Acknowledgement</h1>
|
||||
<h2 id="acknowledgement">Acknowledgement</h2>
|
||||
<p>An acknowledgement that a message was received. Note that for returned path messages, an acknowledgement can be sent in the "extra" payload (see <a href="#returned-path">Returned Path</a>) instead of as a separate acknowledgement packet. CLI commands do not cause acknowledgement responses, neither discrete nor extra.</p>
|
||||
<table>
|
||||
<thead>
|
||||
@@ -857,7 +1477,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h1 id="returned-path-request-response-and-plain-text-message">Returned path, request, response, and plain text message</h1>
|
||||
<h2 id="returned-path-request-response-and-plain-text-message">Returned path, request, response, and plain text message</h2>
|
||||
<p>Returned path, request, response, and plain text messages are all formatted in the same way. See the subsection for more details about the ciphertext's associated plaintext representation.</p>
|
||||
<table>
|
||||
<thead>
|
||||
@@ -890,7 +1510,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="returned-path">Returned path</h2>
|
||||
<h3 id="returned-path">Returned path</h3>
|
||||
<p>Returned path messages provide a description of the route a packet took from the original author. Receivers will send returned path messages to the author of the original message.</p>
|
||||
<table>
|
||||
<thead>
|
||||
@@ -923,7 +1543,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="request">Request</h2>
|
||||
<h3 id="request">Request</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -967,7 +1587,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="get-stats">Get stats</h3>
|
||||
<h4 id="get-stats">Get stats</h4>
|
||||
<p>Gets information about the node, possibly including the following:</p>
|
||||
<ul>
|
||||
<li>Battery level (millivolts)</li>
|
||||
@@ -989,19 +1609,19 @@
|
||||
<li>Number posted (?)</li>
|
||||
<li>Number of post pushes (?)</li>
|
||||
</ul>
|
||||
<h3 id="get-telemetry-data">Get telemetry data</h3>
|
||||
<h4 id="get-telemetry-data">Get telemetry data</h4>
|
||||
<p>Not defined in <code>BaseChatMesh</code>. Sensor- and application-specific request payloads may be implemented by higher-level firmware.</p>
|
||||
<h3 id="get-telemetry">Get Telemetry</h3>
|
||||
<h4 id="get-telemetry">Get Telemetry</h4>
|
||||
<p>Not defined in <code>BaseChatMesh</code>.</p>
|
||||
<h3 id="get-minmaxave-sensor-nodes">Get Min/Max/Ave (Sensor nodes)</h3>
|
||||
<h4 id="get-minmaxave-sensor-nodes">Get Min/Max/Ave (Sensor nodes)</h4>
|
||||
<p>Not defined in <code>BaseChatMesh</code>.</p>
|
||||
<h3 id="get-access-list">Get Access List</h3>
|
||||
<h4 id="get-access-list">Get Access List</h4>
|
||||
<p>Not defined in <code>BaseChatMesh</code>.</p>
|
||||
<h3 id="get-neighbors">Get Neighbors</h3>
|
||||
<h4 id="get-neighbors">Get Neighbors</h4>
|
||||
<p>Not defined in <code>BaseChatMesh</code>.</p>
|
||||
<h3 id="get-owner-info">Get Owner Info</h3>
|
||||
<h4 id="get-owner-info">Get Owner Info</h4>
|
||||
<p>Not defined in <code>BaseChatMesh</code>.</p>
|
||||
<h2 id="response">Response</h2>
|
||||
<h3 id="response">Response</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1019,7 +1639,7 @@
|
||||
</tbody>
|
||||
</table>
|
||||
<p>Response contents are opaque application data. There is no single generic response envelope beyond the encrypted payload wrapper shown above.</p>
|
||||
<h2 id="plain-text-message">Plain text message</h2>
|
||||
<h3 id="plain-text-message">Plain text message</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1073,7 +1693,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h1 id="anonymous-request">Anonymous request</h1>
|
||||
<h2 id="anonymous-request">Anonymous request</h2>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1105,7 +1725,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="room-server-login">Room server login</h2>
|
||||
<h3 id="room-server-login">Room server login</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1132,7 +1752,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="repeatersensor-login">Repeater/Sensor login</h2>
|
||||
<h3 id="repeatersensor-login">Repeater/Sensor login</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1154,7 +1774,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="repeater-regions-request">Repeater - Regions request</h2>
|
||||
<h3 id="repeater-regions-request">Repeater - Regions request</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1186,7 +1806,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="repeater-owner-info-request">Repeater - Owner info request</h2>
|
||||
<h3 id="repeater-owner-info-request">Repeater - Owner info request</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1218,7 +1838,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="repeater-clock-and-status-request">Repeater - Clock and status request</h2>
|
||||
<h3 id="repeater-clock-and-status-request">Repeater - Clock and status request</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1250,7 +1870,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h1 id="group-text-message">Group text message</h1>
|
||||
<h2 id="group-text-message">Group text message</h2>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1280,7 +1900,7 @@
|
||||
<p>The plaintext contained in the ciphertext matches the format described in <a href="#plain-text-message">plain text message</a>. Specifically, it consists of a four byte timestamp, a flags byte, and the message. The flags byte will generally be <code>0x00</code> because it is a "plain text message". The message will be of the form <code><sender name>: <message body></code> (eg., <code>user123: I'm on my way</code>).</p>
|
||||
<p>The sender name is unverified message text. Group messages contain no sender
|
||||
signature, so any channel-key holder can choose any sender name.</p>
|
||||
<h1 id="group-datagram">Group datagram</h1>
|
||||
<h2 id="group-datagram">Group datagram</h2>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1334,7 +1954,7 @@ signature, so any channel-key holder can choose any sender name.</p>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h1 id="control-data">Control data</h1>
|
||||
<h2 id="control-data">Control data</h2>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1356,7 +1976,7 @@ signature, so any channel-key holder can choose any sender name.</p>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="discover_req-sub_type">DISCOVER_REQ (sub_type)</h2>
|
||||
<h3 id="discover_req-sub_type">DISCOVER_REQ (sub_type)</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1388,7 +2008,7 @@ signature, so any channel-key holder can choose any sender name.</p>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="discover_resp-sub_type">DISCOVER_RESP (sub_type)</h2>
|
||||
<h3 id="discover_resp-sub_type">DISCOVER_RESP (sub_type)</h3>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -1420,7 +2040,7 @@ signature, so any channel-key holder can choose any sender name.</p>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h1 id="custom-packet">Custom packet</h1>
|
||||
<h2 id="custom-packet">Custom packet</h2>
|
||||
<p>Custom packets have no defined format.</p>
|
||||
|
||||
|
||||
|
||||
File diff suppressed because one or more lines are too long
+13
-13
@@ -2,54 +2,54 @@
|
||||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/cli_commands/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/companion_protocol/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/docs/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/faq/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/kiss_modem_protocol/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/nrf52_power_management/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/number_allocations/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/packet_format/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/payloads/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/qr_codes/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/stats_binary_frames/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://meshcore-dev.github.io/meshcore/terminal_chat_cli/</loc>
|
||||
<lastmod>2026-07-28</lastmod>
|
||||
<lastmod>2026-08-09</lastmod>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
Reference in New Issue
Block a user