deploy: 44eb8e4ab9

companion_protocol/index.html

@@ -2814,6 +2814,11 @@ catalog; bytes <code>0x2C</code>-<code>0x31</code> are parked and <code>0x35</co
 <td><code>CMD_GET_WIFI_POWER_SAVE</code> / <code>CMD_SET_WIFI_POWER_SAVE</code></td>
 <td>Read or set ESP32 Companion WiFi modem sleep.</td>
 </tr>
+<tr>
+<td><code>0x48</code> / <code>0x49</code></td>
+<td><code>CMD_GET_BLUETOOTH_NAME</code> / <code>CMD_SET_BLUETOOTH_NAME</code></td>
+<td>Read or set the independent Bluetooth device name.</td>
+</tr>
 </tbody>
 </table>
 <p>The sections below detail the most common frames. Refer to the source named
@@ -2865,6 +2870,17 @@ coexistence requires modem sleep. A storage failure also returns
 <code>ERR_CODE_BAD_STATE</code>. If an already-saved mode cannot be applied to the active
 WiFi driver, SET still returns <code>RESP_CODE_OK</code> and the mode is applied on the
 next connection. Device <code>powersaving</code> does not overwrite this setting.</p>
+<p>The Bluetooth-name pair is available on Companion builds regardless of the
+currently selected transport, so a host can configure a BLE-capable image over
+USB or TCP before rebooting into it. <code>CMD_GET_BLUETOOTH_NAME</code> has no body and
+replies with <code>RESP_CODE_OK</code>, a one-byte mode (<code>0</code> for the default name, <code>1</code> for
+a custom name), then the effective UTF-8 device name without a terminator.
+<code>CMD_SET_BLUETOOTH_NAME</code> is followed by zero to 31 UTF-8 bytes. A non-empty
+body stores that exact complete Bluetooth name; a zero-length body clears the
+override and restores <code>MeshCore-&lt;advert name&gt;</code>. A successful SET replies with
+<code>RESP_CODE_OK</code>, and the new label takes effect after reboot. Embedded NULs,
+control characters, malformed UTF-8, or oversized values return
+<code>ERR_CODE_ILLEGAL_ARG</code>; a storage failure returns <code>ERR_CODE_BAD_STATE</code>.</p>
 <h3 id="1-app-start">1. App Start</h3>
 <p><strong>Purpose</strong>: Initialize communication with the device. Must be sent first after connection.</p>
 <p><strong>Command Format</strong>:</p>

companion_radio_full/index.html

@@ -1723,6 +1723,13 @@ Ethernet, and hardware-serial connections do not suppress this screen. With no
 saved BLE PIN, display builds generate a new PIN at boot; builds without a
 physical display use <code>123456</code>. A PIN saved through the Companion protocol takes
 effect after reboot.</p>
+<p>The Bluetooth device name is independently configurable. In the text terminal,
+use <code>get bluetooth.name</code> and <code>set bluetooth.name &lt;name&gt;</code>; use
+<code>set bluetooth.name default</code> to restore <code>MeshCore-&lt;node name&gt;</code>. The WebConfig
+Node card exposes the same optional field on Bluetooth-capable ESP32 builds.
+Custom names replace the complete Bluetooth label rather than inheriting the
+prefix, accept up to 31 valid UTF-8 bytes, and take effect after reboot. This
+does not change the node's mesh advertisement name.</p>
 <p>ESP32 ports 5000, 5001, 5002, and WebConfig have no independent login layer.
 Expose them only on a trusted LAN or temporary setup network. See
 <a href="../WiFi/">WiFi setup</a> for credential setup and reconnect behavior.</p>

terminal_chat_cli/index.html

@@ -1329,6 +1329,13 @@ the radio chip itself.</p>
 <pre><code>set name {name}
 </code></pre>
 <p>Sets your advertisement name.</p>
+<pre><code>get bluetooth.name
+set bluetooth.name {name|default}
+</code></pre>
+<p>Shows or changes the complete Bluetooth device name without changing the mesh
+advertisement identity. A custom name may contain spaces and is limited to 31
+valid UTF-8 bytes. <code>default</code> restores <code>MeshCore-&lt;node name&gt;</code>. The saved change
+takes effect after reboot. <code>get ble.name</code> and <code>set ble.name</code> are short aliases.</p>
 <pre><code>set lat {latitude}
 </code></pre>
 <p>Sets your advertisement map latitude. (decimal degrees)</p>