mirror of
https://github.com/espressif/esp-idf.git
synced 2026-10-02 11:10:54 +03:00
docs(ble): update bridge docs and troubleshooting
This commit is contained in:
@@ -242,14 +242,9 @@ async def main() -> None:
|
||||
asyncio.run(main())
|
||||
```
|
||||
|
||||
For custom service UUID discovery:
|
||||
|
||||
```python
|
||||
devices = await scan_devices(
|
||||
timeout=5.0,
|
||||
service_uuid="00000000-0000-0000-0000-000000000001",
|
||||
)
|
||||
```
|
||||
`scan_devices()` performs an unfiltered BLE scan. If your script needs to
|
||||
restrict results to a specific profile, filter or connect-verify devices in
|
||||
your application code.
|
||||
|
||||
## Error handling guidance
|
||||
|
||||
|
||||
@@ -136,7 +136,7 @@ This affects BLE GATT write behavior only. It does not create an application-lev
|
||||
Use the [BLE UART Service example](../../../../examples/bluetooth/ble_uart_service) when you want a ready-made ESP-IDF Echo Server for testing BLE UART Bridge Console. After building, flashing, and pairing with the example, open Console and type any text; the example should echo the same data back as `[RX]` output.
|
||||
|
||||
```bash
|
||||
# List nearby BLE UART devices and use the printed device ID as DEVICE_ID
|
||||
# List nearby BLE devices and use the printed device ID as DEVICE_ID
|
||||
python main.py list-devices
|
||||
python main.py console AA:BB:CC:DD:EE:FF
|
||||
```
|
||||
@@ -190,6 +190,14 @@ aa 55 01 00
|
||||
- Make sure no other host is already connected to the BLE device.
|
||||
- Restart advertising on the device.
|
||||
- Run `connection-check` before opening the console.
|
||||
- On Linux, reset the system Bluetooth service if connections keep failing,
|
||||
pairing gets stuck, or service discovery cannot find the BLE UART service or
|
||||
characteristics:
|
||||
|
||||
```bash
|
||||
sudo systemctl stop bluetooth
|
||||
sudo systemctl start bluetooth
|
||||
```
|
||||
|
||||
### Text looks broken
|
||||
|
||||
|
||||
@@ -432,6 +432,14 @@ while the daemon waits for a response that never arrives.
|
||||
- The BLE device is disconnected or not advertising.
|
||||
- The daemon tried to reconnect before sending the request or notification, but
|
||||
the reconnect attempt failed.
|
||||
- On Linux, reset the system Bluetooth service if reconnects keep failing,
|
||||
pairing gets stuck, or service discovery cannot find the BLE UART service or
|
||||
characteristics:
|
||||
|
||||
```bash
|
||||
sudo systemctl stop bluetooth
|
||||
sudo systemctl start bluetooth
|
||||
```
|
||||
- Restore the BLE device and retry the same command; the daemon does not replay
|
||||
failed requests automatically.
|
||||
- After three consecutive BLE transport failures, the daemon exits. Restart it
|
||||
|
||||
Reference in New Issue
Block a user