Any interest in using a shared package for UUIDs? #861
koenvervloesem
started this conversation in
Ideas
Replies: 1 comment
-
Hi @koenvervloesem, this looks great! It's something we could definitely use. It would also be useful if the bluetooth-numbers package provided a reverse lookup. Enums might be a nice way to do this. For the services/characteristics/descriptors, the "identifier" could be used as the enum member. For example "org.bluetooth.service.battery_service" would become: class Service(Enum):
...
ORG_BLUETOOTH_BATTERY_SERVICE = 0x180F
... Company names would be a bit messy though since they don't have an identifier. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For another project (Theengs Explorer) using Bleak I needed an up-to-date list of company IDs. I created the project bluetooth-numbers I intend to keep synchronized with Nordic Semiconductor's Bluetooth Numbers Database, having Company IDs, Service UUIDs, Characteristic UUIDs and Descriptor UUIDs. The goal is to provide a shared resource so various Python projects that deal with Bluetooth don't have to replicate this effort.
Is there any interest from Bleak in using the bluetooth-numbers package so you don't need to keep the UUIDs updated yourselves? Some examples of its usage:
Get the description of a company ID:
Get the description of a service UUID:
Get the description of a characteristic UUID:
Get the description of a descriptor UUID:
The project is brand new with only one other project using it for the moment, so if you have remarks about the API before using it in Bleak, I can definitely change it.
I intend to periodically publish new releases of the package with updated data from the Bluetooth Numbers Database.
Beta Was this translation helpful? Give feedback.
All reactions