-
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
Bluetooth Short UUIDs are not resolving correctly #1498
Comments
This is expected since The "correct" way to do this would be
This looks like it could potentially be a bug/inconsistency in the APIs. Workaround could be to use the |
Ok, no problem. And thanks for writing and sharing this excellent ble client. May I suggest updating the usage example code, so that it works though. It may discourage some people if they can’t get the example to work. Maybe add the function you suggest, or use the full guid. |
This fixes 4-character UUIDs causing BleakCharacteristicNotFoundError instead of being properly resolved. Fixes: #1498
This fixes 4-character UUIDs causing BleakCharacteristicNotFoundError instead of being properly resolved. Fixes: #1498
bluetoothctl -v
) in case of Linux: bluetoothctl: 5.66Description
After installing bleak, I tried the basic 'USAGE' sample from here: https://github.com/hbldh/bleak
...which reads the model number characteristic. Since my device does not have this characteristic, I changed to the Manufacturer Name UUID - "2A29", instead of "2A24". With no other changes, the sample fails with error 'Characteristic with UUID 2A29 could not be found.
What I Did
I experimented with using the characteristic, the characteristic handle, short integer uuid, short string uuid and full uuid. The characteristic, characteristic handle and full uuid all returned the manufacturer name. Both short uuids tests did not.
Test Program
Test Output
The text was updated successfully, but these errors were encountered: