-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bleak.exc.BleakError: failed to discover services, device disconnected #1489
Comments
Can you run the same program with debug logging enabled? If that doesn't provide enough info you may need to log Bluetooth packets as well. |
arthur-proglove
added a commit
to arthur-proglove/bleak
that referenced
this issue
Apr 25, 2024
The _wait_removed method registers the "InterfacesRemoved" callback on the adapter path of the device without checking which object was removed when called. This means that any removed interface while a connection is being established can cause the _wait_removed to complete and cancel the connection[1]. This commit simply checks that the callback is for the proper device object path. [1] hbldh#1489
arthur-proglove
added a commit
to arthur-proglove/bleak
that referenced
this issue
Apr 25, 2024
The _wait_removed method registers the "InterfacesRemoved" callback on the adapter path of the device without checking which object was removed when called. This means that any removed interface while a connection is being established can cause the _wait_removed to complete and cancel the connection[1]. This commit simply checks that the callback is for the proper device object path. [1] hbldh#1489
arthur-proglove
added a commit
to arthur-proglove/bleak
that referenced
this issue
Apr 25, 2024
The _wait_removed method registers the "InterfacesRemoved" callback on the adapter path of the device without checking which object was removed when called. This means that any removed interface while a connection is being established can cause the _wait_removed to complete and cancel the connection. This commit simply checks that the callback is for the proper device object path. Fixes hbldh#1489
arthur-proglove
added a commit
to arthur-proglove/bleak
that referenced
this issue
Apr 25, 2024
The _wait_removed method registers the "InterfacesRemoved" callback on the adapter path of the device without checking which object was removed when called. This means that any removed interface while a connection is being established can cause the _wait_removed to complete and cancel the connection. This commit simply checks that the callback is for the proper device object path. Fixes hbldh#1489
arthur-proglove
added a commit
to arthur-proglove/bleak
that referenced
this issue
Apr 25, 2024
The _wait_removed method registers the "InterfacesRemoved" callback on the adapter path of the device without checking which object was removed when called. This means that any removed interface while a connection is being established can cause the _wait_removed to complete and cancel the connection. This commit simply checks that the callback is for the proper device object path. Fixes hbldh#1489
arthur-proglove
added a commit
to workaroundgmbh/bleak
that referenced
this issue
Apr 25, 2024
The _wait_removed method registers the "InterfacesRemoved" callback on the adapter path of the device without checking which object was removed when called. This means that any removed interface while a connection is being established can cause the _wait_removed to complete and cancel the connection. This commit simply checks that the callback is for the proper device object path. Fixes hbldh#1489
dlech
pushed a commit
that referenced
this issue
Apr 28, 2024
* Fix _wait_removed completion on invalid object path The _wait_removed method registers the "InterfacesRemoved" callback on the adapter path of the device without checking which object was removed when called. This means that any removed interface while a connection is being established can cause the _wait_removed to complete and cancel the connection. This commit simply checks that the callback is for the proper device object path. Fixes #1489
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bluetoothctl -v
) in case of Linux: 5.64Description
I have a Vernier Caliper from TESA which has a BLE module and it gives data from that BLE Module. I am trying to read the data from the BLE Module. I am ble to read it in My Phone using LightBlue App (a ble scanner app).
What I Did
When I am rnning the Service_Explorer I am able to discover the device and the advertised service UUID is also visible. Its the same service UUID that i get in my phone app.
It looks like this:
But when I am trying to connect to the same BLE device I am getting error which says:
here is the code which I am using to trying to connect:
Logs
The text was updated successfully, but these errors were encountered: