David Lechner
David Lechner
Usually when BlueZ disconnects unexpectedly, it is because the device does not follow the Bluetooth spec and does something unexpected. You would need to log Bluetooth packets to see if...
> ```python > scanner = await create_ble_scanner() > ``` FYI, this can be replaced with `scanner = await BleakScanner.find_device_by_name(DEVICE_NAME)` instead of subclassing.
If the device is dual-mode, `bluetoothctl` could be connecting with Bluetooth classic instead of BLE. Again, logging Bluetooth packets is the best way to see the difference between the two...
I don't see anything that jumps out at me. Since the D-bus method call is timing out, you could try making the timeout longer. It could be waiting to pair...
> I propose that Bleak's `connect()` method be modified to allow users to specify the `NO_REPLY_EXPECTED` flag. I consider this a BlueZ bug for having a code path that never...
Does it work if you change the permissions for the app on the Android device?
Should be fixed by #1398
Does the characteristic actually support notifications (i.e. run the service_explorer sample or use nRF Connect app to enumerate everything to see what is there)?
This is the same error as https://github.com/hbldh/bleak/issues/1280. Is it fixed already in the develop branch?
Could you please post more details here on how to reproduce the problem and include as much logs as possible.