-
Notifications
You must be signed in to change notification settings - Fork 283
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
connection bleak timeout error from central device #377
Comments
Have you tried the recommendation in the exception? To increase the |
I think I have found the problem. For some types of devices (something to do with random address maybe?), the device is removed from BlueZ as soon as scanning is stopped. So if you try to connect to that device after scanning is stopped, it will fail. As a workaround, try connecting before stopping scanning. |
Also see #363 |
It also looks like there is a new experimental BlueZ adapter API that could be for just such an issue: https://github.com/bluez/bluez/blob/98f5da02ce148a61efdfb2557152448f04bab51f/doc/adapter-api.txt#L170-L206 |
bleak version: 0.10.0 now I'm using bleak 0.10.0 and it is giving me a different error
|
If you run |
Also, please try the See #398 (comment) for more info |
closing since this error happened in the txdbus library that is no longer used |
bluetoothctl -v
) in case of Linux: 5.50Description
I was simply trying to connect a peripheral device with a central device using bleak nordic service
What I Did
first I ran a peripheral device with an advertisement that can be seen in my android scanning ble app
then in central deivce I just ran client code in the below link https://github.com/adafruit/Adafruit_CircuitPython_BLE/blob/master/examples/ble_uart_echo_client.py
it start scanning and then scanning stop after trying to make a connection with the bellow error
The text was updated successfully, but these errors were encountered: