diff --git a/README.md b/README.md index d5e9cad8..6d7ac157 100644 --- a/README.md +++ b/README.md @@ -42,9 +42,9 @@ twice a day; everything below is on top of that. Our code is marked * `dfu [uf2|serial|ota]` (deterministic reboot into the bootloader), `blink`, `txpwr` with RadioLib's verdict, `i2c` bus scan, TX-failure counters in the status reply, reset reason printed at boot. -* Text console over BLE next to USB ("dock-quiet": BLE stays dark while USB - holds DTR), `ble on|off` saved across reboots (`RPT_BLE_DEFAULT_OFF`: starts - off), persisted connection TX power (`blepwr`), `bleconn`, a +* Text console over BLE next to USB, `ble on|off` saved across reboots + (`RPT_BLE_DEFAULT_OFF`: starts off), own BLE PIN (`ble pin`), persisted + connection TX power (`blepwr`), `bleconn`, a non-blocking BLE TX pump and connection parameters that hold on a weak link. * `RADIO_DIAG` build flag: `radiostat` / `radiokick` for an SX1262 receiver that stops receiving. @@ -103,8 +103,8 @@ SenseCAP Solar, RAK4631, T1000-E, Heltec T114) add the `nodes` / `rxlog` / USB or BLE ([meshcore-repeater-observer](https://git.rfa.cz/tth-pub/meshcore-repeater-observer)). The BLE console is **off** after flashing (`RPT_BLE_DEFAULT_OFF`). It has no login of its own, only the BLE PIN, and the build's PIN is the public -placeholder `123456`. So first set your own, in the USB console: -`ble pin <6 digits>` (saved, survives a reboot and a reflash; it also drops +placeholder `123456`. So first set your own -- in the USB console, or as +admin over the mesh (remote CLI in the app): `ble pin <6 digits>` (saved, survives a reboot and a reflash; it also drops every existing bond, so paired devices pair again). Only then `ble on` -- these builds refuse it while the PIN is still the placeholder. `ble` shows whether the PIN is `own` or `build default`, never the PIN itself. Releases