-
Notifications
You must be signed in to change notification settings - Fork 300
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 connection immediately dropped in BlueZ Peripheral to BlueZ Central #1677
Comments
LogsThese are the logs with the BLEAK_LOGS variable enabled
|
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
Hello,
I'm interested in doing a quick proof of concept for a Bluetooth operation and came across BLEAK and BLESS for the Peripheral and Central emulation, respectively. These are identical laptops with bluetooth capability running Ubuntu
22.04
, BlueZ5.64
.What I Did
Currently, the central works fine against a GATT client from something like an Android (nRF Connect) or embedded device. However, if I attempt to connect with a BLEAK Client running on BlueZ, it will instantly disconnect given any of the client examples. My understanding is that I require some sort of configuration on the client for the server to trust the connection, but I'm not aware of how to do this with the BLEAK interface.
Example code, client.py
Vanilla logs
Server code (BLESS 0.2.6)
The text was updated successfully, but these errors were encountered: