Möhlenhoff Alpha 2 - climate controller

Is anyone aware of an integration of the Möhlenhoff Alpha 2 climate controller? It’s OEM so it’s known under different brands within Western Europe.

It has an XML-API available.

I can’t find it …

Many thanks.

Hi, did you manage your Alpha 2 somehow into the HA? I’ve got also one here and wan’t to include (at least) the temperature values into HA.
Ther’s an xml interface (https://community-openhab-org.s3-eu-central-1.amazonaws.com/original/3X/d/e/de188570aeb25c1c18e988ab3dcd7c88b837132b.pdf) but parsing this with the scraper sensor seems not the best way for me.

Do you guys use Hassio? I have created a plugin for these controllers, will need some modification as i have multiple contollers. Currenly only temperatures are retrieved, send to mqtt so mosquitto is required

Hi @posixx
That would be great! I use hassio indeed (running on docker on my synology nas). I already have mqtt running to integrate something else. So that would be fine.
I have 3 alpha2 controllers connected through ethernet (2 x 4-zone, 1 x 8-zone).
Do you detect if the zone is in heating or cooling mode? And is it possible to send a temperature change request?

No only temperature in Celcius…

You can download here: https://saasgui.yodacloud.net/sharing/2oEWqkOaf

Unzip in the addons folder of hassio and go to supervisor, do a refrest and install. You then need to insert all Alpha2 IPs as string separated with “;”

Good luck

The installation is OK, however I see an error in the log:

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[‘’, ‘’, ‘’]
Traceback (most recent call last):
File “/usr/lib/python3.8/urllib/request.py”, line 1319, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File “/usr/lib/python3.8/http/client.py”, line 1230, in request
self._send_request(method, url, body, headers, encode_chunked)
File “/usr/lib/python3.8/http/client.py”, line 1276, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File “/usr/lib/python3.8/http/client.py”, line 1225, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File “/usr/lib/python3.8/http/client.py”, line 1004, in _send_output
File “/usr/lib/python3.8/http/client.py”, line 944, in send
File “/usr/lib/python3.8/http/client.py”, line 915, in connect
self.sock = self._create_connection(
File “/usr/lib/python3.8/socket.py”, line 808, in create_connection
raise err
File “/usr/lib/python3.8/socket.py”, line 796, in create_connection
TimeoutError: [Errno 110] Operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “./alpha2.py”, line 25, in
tree = ET.parse(opener.open(“http://%s/data/static.xml” % alpha))
File “/usr/lib/python3.8/urllib/request.py”, line 525, in open
response = self._open(req, data)
File “/usr/lib/python3.8/urllib/request.py”, line 542, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
File “/usr/lib/python3.8/urllib/request.py”, line 502, in _call_chain
result = func(*args)
File “/usr/lib/python3.8/urllib/request.py”, line 1348, in http_open
return self.do_open(http.client.HTTPConnection, req)
File “/usr/lib/python3.8/urllib/request.py”, line 1322, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [Errno 110] Operation timed out>
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

The thermostats should show off as an mqtt entity automatically?

because you have a typo in the last IP

Indeed :see_no_evil:. Thanks. Working now!
I have the mosquitto add-on running. Do the aplha2 mqtt entity show up automatically in mqtt? Or do I need to configure something (Mosquitto user en pw?) to get the themostat values into mqtt? Many thanks!

The plugin uses MQTT discovery. So all zones you have on the Alpha2 controllers are added to home assistant as sensors. You don’t have to configure anything. Go into development tools and search for the name of a zone you will find it there

hi, thanks for sharing this addon, i’d definitely like to use/try it.
i’m using hassio on my rpi2 and i have one Alpha2. The local Mosquitto broker is installed but the installation of the addon fails:
Failed to install addon, Unknown Error, see logs
I can’t find further error info. Any ideas where to start troubleshooting?

Something has changed within the base images in the latest versions starting from 0.111, which prevent the plugin from building the docker image. See Local addon; suddenly build errors since HassOS 4.10 / 0.111

Fixed it. I peeked at some other addons and changed the base image. You can download the package again and copy it over the existing addon. After refreshing the store it will detect an update.

many thanks for the update. i can now see the actual temperature of my thermostats.
Any plans to extend the addon for target temperature of the termostats?

I have the same Mohlenhoff alpha 2 device as well. Where can I get the add-on? It would help me a lot.

Hi, there seems to be an Alpha2 adaptor for iobroker …

I got in touch with Eisbaeeer en we’re free to convert it to home assistant. Anyone? :slight_smile:

Hi @posixx
First of all many thanks for your work!

Do you have any plans to add target temperature of the termostats?

hi, is there a way to install you addon without hass.io on home assistant? Additional sidenote - download link is not working

Hi. Not a current owner of an Alpha 2 system right now, but will be soon - if I can verify that it fits our requirements. Our current system is based on ancient Honeywell floor controllers and the age is starting to show.

I’ve got a question that hopefully can be answered by people visiting this thread. The Alpha 2 floor controllers can be paired in a master/slave configuration. We’ll need that because we have two floors to control. For the integration in a domotica setting, does it suffice to have only the master equipped with an Ethernet port? In essence, does that relay information about state & control to and from the slave controller?

No this is based on hassio comtainer. But you can make a docker version if you have the skills…

Sorry about the download link: https://saasgui.yodacloud.net/sharing/QyAPfnZqM

I would not recomment master / slave mode. You cannot control slaves using the master. Response from Moehlenhoff support some time ago:

The master / slave connection is only for the pump, boiler and the co-signal. When you want to control all base stations over the Ethernet, then you must also connect the slaves to the Ethernet.

So make sure all your base stations have ethernet connection.