Möhlenhoff Alpha 2 - climate controller

Third party integrations
6

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.
[‘192.168.1.133’, ‘192.168.1.201’, ‘192.18.1.202’]
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
self.send(msg)
File “/usr/lib/python3.8/http/client.py”, line 944, in send
self.connect()
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
sock.connect(sa)
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?

7

because you have a typo in the last IP

8

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!

9

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

10

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?

11

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

12

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.

13

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?

14

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

15

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:

16

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

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

17

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

18

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?

19

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

20

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.

21

skills is what I lack. guess I will have to blow off dust from raspbery pi and install hass.io

22

Thanks for the info. That’s going to make things a bit harder as the upstairs controller has no straightforward IP connection nearby.

I also read somewhat contradictory statements regarding master/slave. In my system only the boiler signal would need to have system character, and the pump signals would need to be controller specific. This is because (obviously?) there is only one boiler providing heat, but I have two circulation pumps, one per floor.

I read in one installation manual that configuring a base station to slave will prevent local control of the signals on the controller, however, it seems that PAr 130 (parameter 130) can be used to choose between a local or a global circulation pump. It seems daft to have such an option only to have that not being relevant for a controller that’s configured as a slave. Any thoughts on this?

23

If i’m reading the response from Moehlenhoff:

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.

The slave can indeed control the pump. But you are not able to control the Alpha2…

EDIT: oh and you still need to connect the 2 devices so why not a CAT5 cable…

24

Ah, well the situation is that I have two floors to control. Each has a number of valves on a manifold with a local circulation pump. Currently, both are controlled with an HCE60 from Honeywell. Whenever there is a heat demand, the HCE60 opens the corresponding valves and activates the local pump. Unfortunately, the installer didn’t add a wired link between the two HCE60. One is located on the 1st floor, the other one is at ground level. In the current situation, our boiler is always activated, and it keeps heating the water until the return temperature is above a certain value (there is a bypass circuit that runs all the way up to the attic). It is certainly not the most economical.

We’ve coped with this for years, but as we are preparing to replace the boiler (we want to move to a full water/air heat pump solution, with storage vessel), we want to replace this old stuff with something a little more open, and sensible. So the solution we hope is offered by Alpha 2 controllers is to pair them wirelessly and have the master control the boiler (on/off) and the local circulation pump while the slave would only control the local pump upstairs and relay the boiler activation to the master.

25

I have solved this with two Mikrotik PWR-Line adapters - they create ethernet via your electrical line, good enough for small amount of data Alpha needs.