openble-sonicare
The Philips Sonicare toothbrush GATT map, read from the Sonicare app's bytecode.
openble.sonicare.uuids: the477ea600-…service and characteristic ids, each with the name and value kind the app uses.openble.sonicare.identify: matches advertisements to a Sonicare handle (toothbrush) or the second plugin family (toothbrush-condor).
Pure Python 3.11+ with no dependencies. Most byte layouts, and the SACP writes, are still open. The protocol manual records what is known and what is not.
pip install openble-sonicare
from openble.sonicare.identify import classify
from openble.sonicare.uuids import CBT_CHARS, cbt, cbt_suffix
classify("Philips Sonicare", [cbt("0001")])
# (['toothbrush'], ['service 477ea600-…0001', 'name Philips Sonicare'])
CBT_CHARS[cbt_suffix(cbt("4050"))]
# ('handle time', 'int')
Protocol notes
docs/sonicare-toothbrush-protocol.md: discovery, connect, bonding and the GATT catalog.
Not affiliated with Philips. The names identify the devices this interoperates with.
License
MIT License, copyright 2026 Kadima Tech.
1 maintainer
Metadata
1 maintainer
Release files for openble-sonicare 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| openble_sonicare-0.1.0.tar.gz | 15.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openble_sonicare-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.0 kB
Release files / openble_sonicare-0.1.0.tar.gz
| Download URL | openble_sonicare-0.1.0.tar.gz |
|---|---|
| Size | 15.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b8238fcd9c169f21ddd254681b0d6e6e65c8a7d30621e109eeb2ff74f7ef0558
|
|
BLAKE2b-256 checksum How to use checksums |
e9aab143757bf72ea58a70c322875d1e3ebf64081a4a34d964b8e6b73fb6256e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / openble_sonicare-0.1.0-py3-none-any.whl
| Download URL | openble_sonicare-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
91c53f4a7ec732a86707f92da1cad56b1ab738615b3ebc4b55e27fe50e323a0f
|
|
BLAKE2b-256 checksum How to use checksums |
b5c79b4f837789d7f48beb280d7ce4858a615a85ecc90e311ab0c610040e28e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for openble-sonicare 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for openble_sonicare-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
