deploy: 2ff1166c15

cli_commands/index.html

@@ -5167,8 +5167,13 @@ disabled.</p>
 - <code>set radio.rxgain &lt;state&gt;</code></p>
 <p><strong>Parameters:</strong>
   - <code>state</code>: <code>on</code>|<code>off</code></p>
-<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>
+<p><strong>Default:</strong> Target-specific. Most SX1262 and LR1110 targets default to <code>on</code>;
+Station G2/G3 targets default to <code>off</code>.</p>
+<p><strong>Notes:</strong>
+- The saved setting is applied immediately and persists across reboots.
+- Periodic AGC resets restore the saved runtime setting; they do not replace it
+  with the target's compile-time default.
+- Existing installations retain their previously saved value after an upgrade.</p>
 <hr />
 <h4 id="view-or-change-rx-duty-cycle-power-saving">View or change RX duty-cycle power saving</h4>
 <p><strong>Usage:</strong>

companion_protocol/index.html

@@ -2898,7 +2898,7 @@ Bytes 2+: Variable length based on firmware version
 For firmware version >= 3:
 Byte 2: Max Contacts Raw (uint8, actual = value * 2)
 Byte 3: Max Channels (uint8)
-Bytes 4-7: BLE PIN (32-bit little-endian)
+Bytes 4-7: Active BLE PIN (32-bit little-endian; includes a generated session PIN)
 Bytes 8-19: Firmware Build (12 bytes, UTF-8, null-padded)
 Bytes 20-59: Model (40 bytes, UTF-8, null-padded)
 Bytes 60-79: Version (20 bytes, UTF-8, null-padded)

companion_radio_full/index.html

@@ -1346,7 +1346,7 @@ are requested.</p>
 <tr>
 <td>Both</td>
 <td>BLE</td>
-<td>Binary Companion; default pairing PIN <code>123456</code></td>
+<td>Binary Companion; display builds show a random session PIN, while headless builds default to <code>123456</code></td>
 </tr>
 <tr>
 <td>ESP32</td>
@@ -1378,6 +1378,13 @@ are requested.</p>
 <p>Binary Companion replies are broadcast through the multi-interface manager,
 so use one active Companion application at a time. On nRF52, BLE remains
 available while USB is in terminal or mOTA mode.</p>
+<p>When a BLE client requests pairing, a display-equipped build wakes the screen,
+switches to the first home page, and keeps the active six-digit PIN visible
+until Bluetooth connects or the two-minute pairing window expires. USB, WiFi,
+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>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>

faq/index.html

@@ -3499,7 +3499,10 @@ Below are the instructions to flash firmware onto a supported LoRa device using
 <h3 id="64-q-my-companion-isnt-showing-up-over-bluetooth">6.4. Q: My companion isn't showing up over Bluetooth?</h3>
 <p><strong>A:</strong> Make sure that you flashed the Bluetooth companion firmware and not the USB-only companion firmware.</p>
 <h3 id="65-q-i-cant-connect-via-bluetooth-what-is-the-bluetooth-pairing-code">6.5. Q: I can't connect via Bluetooth, what is the Bluetooth pairing code?</h3>
-<p><strong>A:</strong> The default Bluetooth pairing code is <code>123456</code></p>
+<p><strong>A:</strong> The default Bluetooth pairing code is <code>123456</code> on builds without a
+physical display. Display-equipped Companion builds generate a six-digit PIN
+at boot and show it when a client requests pairing. The display stays awake on
+the PIN page until Bluetooth connects or the two-minute pairing window expires.</p>
 <h3 id="66-q-my-heltec-v3-keeps-disconnecting-from-my-smartphone-it-cant-hold-a-solid-bluetooth-connection">6.6. Q: My Heltec V3 keeps disconnecting from my smartphone. It can't hold a solid Bluetooth connection.</h3>
 <p><strong>A:</strong> Heltec V3 has a very small coil antenna on its PCB for Wi-Fi and Bluetooth connectivity. It has a very short range, only a few feet. It is possible to remove the coil antenna and replace it with a 31mm wire. The BT range is much improved with the modification.</p>
 <h3 id="67-q-my-rakt1000-exiao_nrf52-device-seems-to-be-corrupted-how-do-i-wipe-it-clean-to-start-fresh">6.7. Q: My RAK/T1000-E/xiao_nRF52 device seems to be corrupted, how do I wipe it clean to start fresh?</h3>