Converting a MAX! Cube to CUL/CUN to use with Home Assistant

I dont know the internals of homegear, but i think that /var/lib/homegear contains data that should be backuped like the paired devices…

For the influxdb i think it is used for node blue, but i dont know it exactly.

So i made a version without influxdb and it seems to work, at least for 22 hours, it also survived a restart of the homegear container.

i will start to move all my MAX!-component to homegear.

You happy of the switch? Did the valves report temperature values (with the HASS Max component most of the time not)

I copied the five files in the directory \ubuntu\addons\Homegear when I go to the addon store I do find HOMEGEAR SGR addon, when I click INSTALL, nothing happens.

I run HASSIO on a Ubuntu NUC.

In the log

18-10-25 18:41:56 INFO (SyncWorker_11) [hassio.docker.addon] Start build local/amd64-addon-rpi-homegear:0.2
18-10-25 18:41:56 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 390, in start
    resp = await self._request_handler(request)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 366, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 106, in impl
    return await handler(request)
  File "/usr/local/lib/python3.7/site-packages/hassio/api/security.py", line 137, in token_validation
    return await handler(request)
  File "/usr/local/lib/python3.7/site-packages/hassio/api/utils.py", line 32, in wrap_api
    answer = await method(api, *args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/hassio/addons/addon.py", line 692, in install
    if not await self.instance.install(self.last_version):
  File "/usr/local/lib/python3.7/site-packages/hassio/utils/__init__.py", line 33, in wrap_api
    return await method(api, *args, **kwargs)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/hassio/docker/addon.py", line 307, in _install
    return self._build(tag)
  File "/usr/local/lib/python3.7/site-packages/hassio/docker/addon.py", line 321, in _build
    **build_env.get_docker_args(tag))
  File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 258, in build
    resp = self.client.api.build(**kwargs)
  File "/usr/local/lib/python3.7/site-packages/docker/api/build.py", line 142, in build
    raise TypeError("You must specify a directory to build in path")
TypeError: You must specify a directory to build in path

Yes, you are absolutely right. I made a new version of the HassIO HomeGear addon which mounts this folder out. It is installable from a repository. Node-BLUE is included and working great. So I will leave influxdb inside as well.

If you’d like to share your version of the addon, maybe we can merge the best of both in one addon.

Oh sorry - I misunderstood.

So, I dug the wall stat out of the drawer this evening and paired it with homegear.
Good news - the devices can be linked as per the original MAX functionality, so the wall stat can control multiple radiators, and also reports its value to the radiator valve.

To achieve this, pair the wall stat in homematic manager as per the procedure for the radiator valves.
Then select the ‘Verknupfunger’ tab, and press the ‘+’ button at the bottom.
In the new window under sender, select the serial of your wall stat, then select the valve(s) under ‘Empfanger’ - then press ‘Anlegen’

The devices are now linked :smiley:

4 Likes

Have you verified that other addons install correctly?

I have tested this on a standard HassIO on HassOS install (see https://www.home-assistant.io/hassio/installation/) on a RaspberryPi 3. As this device is ARM based, I’m not quiet sure, if this addon will run on x86 as well.

Yes, those “Verknüpfungen” work well. With those, it’s easy to link Thermostat <-> Thermostat, Wallthermostat -> Thermostat and WindowContact -> Thermostat. Has anyone found out, how to link EcoTaster with Termostats?

Thank you for confirming! Very useful information. I now have a big decision to make about whether I keep my Nest setup or ditch it and use the generic thermostat component with a sonoff or similar.

Such a shame the Nest API doesn’t allow read/write of the “current temperature” or it would be perfect.

yes all addons works, just this not

Adding yours gives this. Sorry I don’t know much about docker

18-10-25 21:46:14 INFO (SyncWorker_15) [hassio.docker.addon] Start build 89330960/amd64-addon-rpi-homegear:0.2 18-10-25 21:46:45 ERROR (SyncWorker_15) [hassio.docker.addon] Can’t build 89330960/amd64-addon-rpi-homegear:0.2: The command ‘/bin/sh -c apt-get update && apt-get -y install apt-transport-https wget ca-certificates apt-utils gnupg’ returned a non-zero code: 1

Hi!

In case of a HASSIO installation, where do you find this file?

Yes, this addon will not work onx86 because of the Docker Base image

FROM resin/rpi-raspbian:stretch

In the official Add-ons hass.io will try to use the right baseimage by using this in the Dockerfile instead:

ARG BUILD_FROM
FROM $BUILD_FROM

Which did not work in my case :frowning:

Would be great to get an x86 build of the addon going since I guess there are a number of people running hassio on VM’s / other tin that are not Rpi.

Anyone up to the challenge ? :grin:

I may have a look myself, but free time is lacking recently!

COPIED FROM ANOTHER POST

There is no official add-on but you can create your own easily.

  1. Install samba addon (for ease)
  2. In the addons dir create a new folder “Homegear”
  3. In the Homegear dir create a file “config.json”, and paste this into in and save:
    {
      "name": "Homegear",
      "version": "latest",
      "slug": "homegear",
      "image": "homegear/homegear",
      "description": "Homegear",
      "url": "https://hub.docker.com/r/homegear/homegear/",
      "startup": "before",
      "boot": "auto",
      "ports": {
        "2001/tcp": 2001,
        "2002/tcp": 2002,
        "2003/tcp": 2003
      },
      "environment": {
      },
      "arch": ["amd64"],
      "options": {
      },
      "schema": {
      }
    }

You may need to change arch if on RPi - I am on x86
Save the file, open hassio store and you should see local addon.
Install it and start it…

Works for me at http://hassio.local:2001

1 Like

I followed this guide and the addon seems installed. I do not know how to test it since I didn’t flash trhe MAX Cube yet.

I can click on NODE-BLUE but it asks for a user and password, which I do not know

Nice find, might check this out when I get the time :wink:

Does this add on store the data outside the container or does it reset on every rebuild?

I have no idea, better ask the creator of the post @hijinx

Worried about this

For the logindata you must take a look at the logfile. The password is dynamicaly generated during first start