aiobookoov2
aiobookoov2 is an asynchronous Python library for interacting with Bookoo Themis Mini coffee scales over Bluetooth Low Energy (BLE). It is based on the aioacaia library and utilizes asyncio and bleak for its operations.
This library is primarily designed to be used by the Bookoo Home Assistant integration but can also be used as a standalone library for other projects.
Features
- Connect to Bookoo Themis Mini scales.
- Receive real-time weight, timer, and flow rate data.
- Send commands to the scale:
- Tare
- Start Timer
- Stop Timer
- Reset Timer
- Tare & Start Timer
- Handle notifications from the scale, including:
- Weight characteristic updates (0xFF11).
- Command characteristic updates (0xFF12), specifically for 0x0D auto-timer start/stop events.
- Decode BLE messages into a structured format.
- Provides callbacks for characteristic data updates and general state changes.
Requirements
- Python 3.13
bleak>=0.22.3- A Bluetooth adapter compatible with
bleakon your system.
Installation
You can install aiobookoov2 directly from PyPI:
pip install aiobookoov2
To install for development:
git clone https://github.com/taliexo/aiobookoo.git
cd aiobookoo
pip install -e .[dev]
Basic Usage
Here's a simple example of how to connect to a scale and receive updates:
import asyncio
import logging
from bleak import BleakScanner
from aiobookoov2 import BookooScale, UPDATE_SOURCE_WEIGHT_CHAR, UPDATE_SOURCE_COMMAND_CHAR
# Configure logging
logging.basicConfig(level=logging.INFO)
_LOGGER = logging.getLogger(__name__)
# For more detailed bleak/aiobookoov2 logs, set level to DEBUG:
# logging.getLogger("aiobookoov2").setLevel(logging.DEBUG)
# logging.getLogger("bleak").setLevel(logging.DEBUG)
TARGET_SCALE_ADDRESS = "XX:XX:XX:XX:XX:XX" # Replace with your scale's MAC address
# Or discover automatically:
# from aiobookoov2.helpers import find_bookoo_devices
# async def discover():
# devices = await find_bookoo_devices(timeout=10.0)
# if devices:
# return devices[0].address
# return None
# TARGET_SCALE_ADDRESS = asyncio.run(discover())
def my_characteristic_update_handler(source: str, data: bytes | dict | None):
"""Handle characteristic data updates."""
if source == UPDATE_SOURCE_WEIGHT_CHAR:
# Data for weight char is usually None, scale object has updated attributes
_LOGGER.info(
f"Weight update: Weight={scale.weight}g, Timer={scale.timer}s, Flow={scale.flow_rate}g/s, Battery={scale.device_state.battery_level if scale.device_state else 'N/A'}%"
)
elif source == UPDATE_SOURCE_COMMAND_CHAR:
_LOGGER.info(f"Command char update: {data}")
if isinstance(data, dict) and data.get("type") == "auto_timer":
_LOGGER.info(f"Scale auto-timer event: {data.get('event')}")
async def main():
global scale
if not TARGET_SCALE_ADDRESS:
_LOGGER.error("Scale address not set. Please discover or hardcode it.")
return
scale = BookooScale(
address_or_ble_device=TARGET_SCALE_ADDRESS,
characteristic_update_callback=my_characteristic_update_handler,
)
try:
_LOGGER.info(f"Attempting to connect to {TARGET_SCALE_ADDRESS}...")
if await scale.async_connect():
_LOGGER.info("Connected! Waiting for notifications...")
# Keep the script running to receive notifications
# You can send commands here, e.g.:
# await asyncio.sleep(5)
# await scale.async_send_command("tare")
# _LOGGER.info("Tare command sent.")
while scale.connected:
await asyncio.sleep(1)
else:
_LOGGER.error("Failed to connect.")
except Exception as e:
_LOGGER.error(f"An error occurred: {e}")
finally:
if scale.connected:
_LOGGER.info("Disconnecting...")
await scale.async_disconnect()
_LOGGER.info("Disconnected.")
if __name__ == "__main__":
try:
asyncio.run(main())
except KeyboardInterrupt:
_LOGGER.info("Program stopped by user.")
Development
This project uses ruff for linting and formatting, and mypy for static type checking. Pre-commit hooks are configured to run these checks automatically.
To set up for development:
- Install
pre-commit:pipx install pre-commitorbrew install pre-commit. - Install hooks:
pre-commit install.
Run checks manually:
ruff check .ruff format .mypy --config-file=mypy.ini aiobookoov2/pytest tests/
Contributing
Contributions are welcome! Please open an issue or submit a pull request.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for aiobookoov2 0.3.7
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 | |
|---|---|---|---|---|
| aiobookoov2-0.3.7.tar.gz | 29.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiobookoov2-0.3.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 57.3 kB
Release files / aiobookoov2-0.3.7.tar.gz
| Download URL | aiobookoov2-0.3.7.tar.gz |
|---|---|
| Size | 29.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc0f00af553babc920981aa2c850cfbe81a42ffc383823f9b449ab40dcabc2f9
|
|
BLAKE2b-256 checksum How to use checksums |
2664df696805d198d2e003e16bcc6e0ec9eda6875d8e5aa47ecbcc1551183914
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Jun 7, 2025.
Transparency logRelease files / aiobookoov2-0.3.7-py3-none-any.whl
| Download URL | aiobookoov2-0.3.7-py3-none-any.whl |
|---|---|
| Size | 27.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab6a5d74024fdd3b9dd1107427d0afe46be55a0d0c40a73e857c23a5bed05f04
|
|
BLAKE2b-256 checksum How to use checksums |
0ec4017943047d16637c16653b4d8ded9acc7bf0ccfebd1e2d19431b9fd4e26d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Jun 7, 2025.
Transparency logSecurity for aiobookoov2 0.3.7
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 aiobookoov2-0.3.7.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 Jun 7, 2025.
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.