CometBlue
eurotronic-cometblue-ha is a library to communicate with your Eurotronic GmbH Comet Blue radiator controllers.
The device supports up to four programmable schedules for each weekday. Longer periods can be set as holidays. There are 8 holiday slots available. It depends on bleak and bleak-retry-connector and runs therefore on Linux, Windows and macOS in addition to the Home Assistant component.
Compatible devices
Comet Blue radiator controllers are sold under different names:
| "Manufacturer" | Model | Tested |
|---|---|---|
| Eurotronic | Comet Blue | ✔️ |
| Sygonix | HT100 BT | ✔️ |
| Xavax | Hama | ❔ |
| Silvercrest | RT2000BT | ❔ |
This library should work with all listed radiator controllers, but is only tested with a Eurotronic Comet Blue which is the only one I own.
If your device is not listed here but looks similar (or you know it is a rebranded Comet Blue), or if you are able to test this library with another device - let me know your results.
Just
pip install eurotronic-cometblue-ha
Usage
The client is async-only. Use AsyncCometBlue with a BLEDevice returned by Bleak
discovery and an optional pin (default 0). Discovery timeouts belong to the scan,
not the client constructor.
An address string is resolved during connect_async() using the existing BLE timeout;
a supplied BLEDevice is used directly without scanning.
All device operations must be awaited. Use async with to connect and disconnect
automatically, or explicitly await connect_async() and disconnect_async().
Connection contexts on the same instance are serialized. Callers using explicit connect/disconnect calls must serialize their own sessions. Retry delays and refresh scheduling remain the caller's responsibility.
| Method | Parameters | Return Value |
|---|---|---|
get_device_info_async |
None | dict with model, version, manufacturer |
get_temperature_async |
None | dict with currentTemp, manualTemp, targetTempLow, targetTempHigh, tempOffset, windowOpen, windowOpenMinutes |
set_temperature_async |
dict containing any of manualTemp, targetTempLow, targetTempHigh, tempOffset |
None |
get_battery_async |
None | Battery percentage as int |
get_datetime_async |
None | Device-local datetime, used for schedules |
set_datetime_async |
Optional datetime, defaults to now |
None |
get_weekday_async |
Weekday, e.g. Weekday.MONDAY |
dict with start# and end# keys (# = 1-4), times as HH:mm strings |
set_weekday_async |
Weekday and schedule dict |
None |
set_weekdays_async |
dict mapping weekday names (e.g. "monday") to schedule dictionaries |
None |
get_holiday_async |
Slot number (1-8) | dict with start, end, temperature; empty for an inactive slot |
set_holiday_async |
Slot number (1-8) and dict with start, end, temperature |
None |
get_manual_mode_async |
None | True for manual mode, False for scheduled mode |
set_manual_mode_async |
bool selecting manual mode |
None |
get_multiple_async |
List of names: temperature, battery, datetime, holiday1-holiday8, holidays, monday-sunday, weekdays, manual |
dict of results from the corresponding getters |
discover_async |
Optional scan timeout, defaults to 5 seconds |
List of matching BLEDevice objects |
⚠️ the device applies set values when the connection is closed, not directly after setting them.
Last-known state
AsyncCometBlue.raw returns a dictionary mapping characteristic UUIDs to their latest
immutable bytes, without BLE I/O or decoding. Unread characteristics are
absent. Malformed responses remain available even when the getter raises
Migrating from the synchronous client
The synchronous CometBlue class has been removed. Replace it with AsyncCometBlue,
use async with instead of with, and await the existing *_async methods.
Replace CometBlue.discover() with await AsyncCometBlue.discover_async(); discovery
returns BLEDevice objects, whose .address attribute provides the address.
The library no longer creates or runs event loops. In an async application, use its
existing loop; a standalone script can call asyncio.run(main()) as shown below.
Examples
Instantiating and retrieving the current temperature
import asyncio
from bleak import BleakScanner
from eurotronic_cometblue_ha import AsyncCometBlue
async def main():
device = await BleakScanner.find_device_by_address("00:00:00:00:00:00", timeout=10)
if device is None:
raise RuntimeError("Comet Blue device not found")
async with AsyncCometBlue(device=device, pin=123456) as blue:
temp = await blue.get_temperature_async()
print(temp)
asyncio.run(main())
results in
{
"currentTemp": 24.5,
"manualTemp": 16.0,
"targetTempLow": 16.0,
"targetTempHigh": 20.0,
"tempOffset": 0.0,
"windowOpen": True,
"windowOpenMinutes": 10,
}
Setting a new schedule
Setting a new schedule for Mondays with two heating periods:
-
Period 1 from 06:00 to 08:00
-
Period 2 from 16:00 to 22:00
All unmentioned periods (periods 3 and 4) will be disabled (start and end set to 00:00).
Set periods will be consolidated, meaning setting only period 3 via this method will write period 1 and disable the others.
To use this schedule, make sure to disable manual mode. Run the following inside
an async function while blue is connected (for example, inside the async with
block above).
from eurotronic_cometblue_ha import Weekday
await blue.set_weekday_async(Weekday.MONDAY, {"start1": "06:00", "end1": "08:00", "start2": "16:00", "end2": "22:00"})
await blue.set_manual_mode_async(False)
Setting a holiday
Setting a holiday (slot 2) from 26th December 2020 18:00 till 5th January 2021 14:00 and keep the temperature at 16.5 °C
from datetime import datetime
await blue.set_holiday_async(
2, {"start": datetime(2020, 12, 26, 18), "end": datetime(2021, 1, 5, 14), "temperature": 16.5}
)
Development and tests
See tests/README.md for setup, running tests in the project's default virtual environment, and using the shared BLE mocks.
Credits:
- Thorsten Tränker for his reverse engineering work done here
- @zero-udo for the initial library zero-udo/eurotronic-cometblue
- @FloSchmidt for checking the Eurotronic Comet Blue
- @rikroe for the switch to bleak
Metadata
Release files for eurotronic-cometblue-ha 2.0.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 | Actions |
|---|---|---|---|---|
| eurotronic_cometblue_ha-2.0.0.tar.gz | 27.8 kB | With provenance | Details for eurotronic_cometblue_ha-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| eurotronic_cometblue_ha-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for eurotronic_cometblue_ha-2.0.0-py3-none-any.whl |
Total release size: 41.4 kB
Release files / eurotronic_cometblue_ha-2.0.0.tar.gz
| Download URL | eurotronic_cometblue_ha-2.0.0.tar.gz |
|---|---|
| Size | 27.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cfcbe365926b8af3ef55face0de8c4982b430dc8dd6536335d4450ccc953b7d8
|
|
BLAKE2b-256 checksum How to use checksums |
2a04bb130138359caebabc1972bbf3fcb9c9c411acf0b0ef716e53e0b9ce2bf1
|
| 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 11, 2026.
Transparency logRelease files / eurotronic_cometblue_ha-2.0.0-py3-none-any.whl
| Download URL | eurotronic_cometblue_ha-2.0.0-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f60da53ad3ef2e91149ebff3e7d1f4d7ac17860fbc782440505503515a65535
|
|
BLAKE2b-256 checksum How to use checksums |
dc6d12297f3e8040cfde6a9f84be85078eaf0b72506cf70fa9b65fa6d5f6ff24
|
| 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 11, 2026.
Transparency logSecurity for eurotronic-cometblue-ha 2.0.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
Both files in this release have been uploaded with provenance metadata.
Attestation for eurotronic_cometblue_ha-2.0.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 11, 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.