From 9f472cebadd90193ea8298958b1fde87f5be9421 Mon Sep 17 00:00:00 2001 From: James Rich <2199651+jamesarich@users.noreply.github.com> Date: Tue, 23 Jun 2026 10:18:57 -0500 Subject: [PATCH] docs(ble): update MeshtasticBleDevice KDoc for post-#5912 reconnect flow (#5913) Co-authored-by: Claude Sonnet 4.6 --- .../kotlin/org/meshtastic/core/ble/MeshtasticBleDevice.kt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/core/ble/src/commonMain/kotlin/org/meshtastic/core/ble/MeshtasticBleDevice.kt b/core/ble/src/commonMain/kotlin/org/meshtastic/core/ble/MeshtasticBleDevice.kt index 0e2d7e530..177fa95db 100644 --- a/core/ble/src/commonMain/kotlin/org/meshtastic/core/ble/MeshtasticBleDevice.kt +++ b/core/ble/src/commonMain/kotlin/org/meshtastic/core/ble/MeshtasticBleDevice.kt @@ -26,8 +26,11 @@ import kotlinx.coroutines.flow.asStateFlow * Unified [BleDevice] implementation for all BLE devices — scanned, bonded, or both. * * When created from a live BLE scan, [advertisement] is populated and used for optimal peripheral construction via - * `Peripheral(advertisement)`. When created from the OS bonded device list (address only), [advertisement] is `null` - * and the peripheral is constructed via `createPeripheral(address)` with `autoConnect = true`. + * `Peripheral(advertisement)` with a direct (non-autoConnect) connection attempt. + * + * Bonded-only devices (address only, [advertisement] null) can still be constructed — e.g. for display in the device + * list — but [BleRadioTransport.findDevice] requires a fresh advertisement before connecting and will throw + * [RadioNotConnectedException] rather than returning a stale handle. * * @param address The device's MAC address (or platform identifier string). * @param name The device's display name, if known.