EUROTronic CometBlue / Xavax Hama / Sygonix


based on the work of of Xrucka[1] which is based on the work of im-0[2] which is based on the work of Thorsten Traenkner[3], I created a component for controlling the Bluetooth thermostats created/distributed by EUROTronic / Xavax / Sygonix / alike - found here[4].

It’s very basic for now, but you can already reliably track resp. change the current resp. target temperature of multiple devices.

Feedback is welcome. Development is ongoing. Thanks!


1 Like

Great work! I recently bought a Eurotronic CometBlue radiator valve because I wasn’t completely happy with the EQ3 BT version I had before (quite noisy and cheap feel to it). I already like this new one better but haven’t been able to get it to work with Home-Assistant yet.

I found your custom component and added it to the custom components folder. I don’t know how to configure this in the configuration.yaml;
In your GitHub repository I see the following code:

from homeassistant.const import (

Which makes me think I need to add this to the configuration:

- platform: cometblue
  name: Comet Blue Slaapkamer
  mac: !secret comet_blue
  pin: ??

In the error log of Home-Assistant I get this message:

starting version 3.2.4
Testing configuration at /config
Failed config
  General Errors: 
    - Platform not found: climate.cometblue
Successful config (partial)

Therefore I think i forgot something. Do you know what I’m missing? I’m trying to run this on RPi3 with

Thanks in advance and keep up the good work!

I got the same issue.
Logs says
Error loading custom_components.climate.cometblue. Make sure all dependencies are installed

Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/”, line 94, in get_component
module = importlib.import_module(path)
File “/usr/lib/python3.5/importlib/”, line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File “”, line 986, in _gcd_import
File “”, line 969, in _find_and_load
File “”, line 958, in _find_and_load_unlocked
File “”, line 673, in _load_unlocked
File “”, line 673, in exec_module
File “”, line 222, in _call_with_frames_removed
File “/home/homeassistant/.homeassistant/custom_components/climate/”, line 66, in
from cometblue import device as cometblue_dev
ImportError: No module named ‘cometblue’

So i think the cometblue lib is not installed correctly.
Line 38 in the git says

#REQUIREMENTS = [‘cometblue’]

so the requirement is commented out.
Anyway, removing the ‘#’ did not worked also, i think pip3 cannot install cometblue out of the box.

@mirko any ideas?

You need to install cometblue from xrucka.
Afaik this will not work with You wont be able to install custom dependencies on unless these guys makes it official or there is an official addon.

I have tried it on a fresh Raspbian with HA in a venv and I am getting following error:

Introspect error on :1.3:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type=“method_call”, sender=":1.23" (uid=999 pid=349 comm="/srv/homeassistant/bin/python3 /srv/homeassistant/") interface=“org.freedesktop.DBus.Introspectable” member=“Introspect” error name="(unset)" requested_reply=“0” destination=":1.3" (uid=0 pid=485 comm="/usr/lib/bluetooth/bluetoothd ")

Hopefully someone is still working on this component and maybe can provide a step-by-step. winter is coming…


If you are using venv you have to add this settings:

<policy user="homeassistant">
   <allow send_destination="org.bluez"/>

into config file /etc/dbus-1/system.d/bluetooth.conf

But you should add it before default deny section.

  <policy context="default">
    <deny send_destination="org.bluez"/>

I was able to bypass this error but hit another one:

2018-11-27 16:45:22 WARNING (MainThread) [homeassistant.components.climate] Setup of platform cometblue is taking over 10 seconds.
2018-11-27 16:46:12 ERROR (MainThread) [homeassistant.components.climate] Setup of platform cometblue is taking longer than 60 seconds. Startup will proceed without waiting any longer.

I’ll try to debug this.

Hi marko.

I used your great work and made some changes, added some features and tested component. Right now I have a, lets say, funcional custom component.

I decided to make its own repo for it (hope you don’t mind) on Github.

Any feedback or issue report is more than welcome.

@Hy3n4 Looks amazing! Can you maybe create a PR and add this directly to home assistant? So people do not have to do the custom component installation process

@Zoker I believe in this phase it wouldn’t be possible. Those manual steps are required and everyone has to do them. Especially allowing org.bluez destination for homeassistant user. Right now I have no idea how to accomplish all theese steps within HA installation.
Maybe when HA is not running in venv, but this option was not tested yet. Look at Github and feel free to test it :wink:

Interesting. I’m currently using the EQ3 Bluetooth Smart Thermostats which also use BLE and they don’t need any additional config. Why is this additional config necessary anyway? I’m pretty new to python and did not look at the code yet. But maybe we can find a solution to avoid this additional config :slight_smile:

The existing cometblue library is written around a BLE library with complex dependencies. We should do a rewrite with a simpler library, eg. bluepy.

1 Like

@Hy3n4 What do you think about using a different library?
Could that help to get a nativ HA component?

hi , have 3 of these and they are quite popular arround germany and otherEU countries (price arround20usd )sold under different names. it was painfull process to get them working (for me blen ble to mqtt gw solution provide best results) still it is not perfect (mqtt often crash ) but that could be finetuned.
will be great to have Hassio plugin but mean time my solution is :
1, install clean rassbian , and then follow how to install hassio on generic linux - you end up with raspi running hassio in docker but you still going to be able to access fully featured shell of raspbian
2, setup mqqt in hassio (simple plugin install) , configure permissions and account.
3, follow ble to mqtt igw installation manual ( you will do this in raspbian shell not in docker ) target mqtt and user name which you set in hassio
5, upload custom component to hassio config folder
6, simply folow instructions to finish configuration configure

great is you still have hassio with all benefits like plugins

I created a simple component for hassio based on the bluepy library. Just put this file in custom_components/climate/ It currently only supports current and target temperature.


climate cb:
  platform: cometblue
      mac: 11:11:11:11:11:11
      pin: 0
1 Like

Amazing! Will it be hard to support all the other functions?

HassIO has some issues with communication with Pi’s BTLE module. I tried that once but this solution you described is the most reliable solution yet.

This is definitely a right path. Not the easy one I chose :). There will be a lot of work on this. If you want I cloud help you on that in my free time which is kind of rarity lately.

Hey Guys,

I’ve got a running integration of those thermostats based on the code of xrucka.
I did not manage to add the necessary packages to the hass dependencies and therefore have not added a pull request, yet.
Since I’ve not the time to complete this now - does anyone want to take a look at the code and perhaps use some parts of it to complete this component?

Im getting an error adding your component (using hassio). Only added your file and config entry.
Any idea why?

Error while setting up platform cometblue
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/homeassistant/helpers/”, line 128, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.7/asyncio/”, line 416, in wait_for
return fut.result()
File “/usr/local/lib/python3.7/concurrent/futures/”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/cometblue/”, line 62, in setup_platform
dev = CometBlueThermostat(device_cfg[CONF_MAC], name, device_cfg[CONF_PIN])
File “/config/custom_components/cometblue/”, line 83, in init
self._thermostat = CometBlue(_mac, _pin)
File “/config/custom_components/cometblue/”, line 153, in init
File “/config/custom_components/cometblue/”, line 189, in update
data = self._conn.readCharacteristic(TEMPERATURE_HANDLE)
File “/usr/local/lib/python3.7/site-packages/bluepy/”, line 489, in readCharacteristic
resp = self._getResp(‘rd’)
File “/usr/local/lib/python3.7/site-packages/bluepy/”, line 369, in _getResp
resp = self._waitResp(wantType + [‘ntfy’, ‘ind’], timeout)
File “/usr/local/lib/python3.7/site-packages/bluepy/”, line 332, in _waitResp
raise BTLEException(BTLEException.COMM_ERROR, “Error from Bluetooth stack (%s)” % errcode)
bluepy.btle.BTLEException: Error from Bluetooth stack (comerr)

Is there any way, we can install that on a hassio installallation?

@thawizard: Did you modify the config.txt file? Are you sure that bluetooth works on your raspi?You can enable ssh and check with hcitool lescan that bluetooth works.

@stefffen: Have a look at this post.