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 ? 
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.
- Install samba addon (for ease)
- In the addons dir create a new folder “Homegear”
- 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 
Does this add on store the data outside the container or does it reset on every rebuild?
Worried about this
For the logindata you must take a look at the logfile. The password is dynamicaly generated during first start
Have you managed to get config writing outside of the docker container for your addon ?
I have cloned the setup from your github but tweaked a few parts as mentioned above so that it works on x86.
However I’m not seeing any of the folders get created in my Hassio /config or /share… looking at start.sh it should at least be creating the directories on startup…
Yes, my linked addon from GitHub stores all data outside the container. It is rebuild and restart safe. As I don’t know what you changed, I cannot say what the reason is, that it does not work for you. Maybe the container doesn’t even start Correctly?
The addon seems to be starting OK - I can access the webserver on port 2001 and the log output looks good.
It just doesn’t seem to map the directories for some reason.
I’ve uploaded the addon files here : https://drive.google.com/file/d/10oPj8Uv-DDWnsJ5Id1W5eSu3J0z_yp3a/view?usp=sharing
But the change was basically to remove the rpi qemu reference and point at debian:stretch as the source on the dockerfile.
I can´t see the max cube in homegear. I can see the max cuns ip adresse and put it in the max.conf but i can´t see it in homegear and i can´t pair my thermostats
@swifty, that is a realy greate tutorial to flash the MAX! cube to CUL. I use MAX! devices for 3 years and for two years i flashed my MAX! Cube. Scince this, the system runs realy create and solid!
This summer i changed my setup from homegear with installed homeassistant and deconz to hass.io on my raspberrypi. The homegear addon for hass.io is no longer supported and can’t be installed. This week i worked on the old Plugin to get it run on the new setup. I Changed the homegear version to the nightly 0.8 and use debian instead of raspbian. Now it works great for me.
1 Like
@kreativmonkey Very nice - would be great if we could have a homegear addon that supports all platforms.
I’m not so familiar with the internals of addon creation, do you know is it possible to have some logic in the dockerfile & start script that handles different platforms? or is the only option to have separate addons per platform?
@weber114 Sorry for the delay… was busy and meant to come back to your message but forgot! - Have you solved your issue?
No sadly i can’t connect to any of my devices.
They are not showing up in homegear.
Ok - please give us some detail on where you have got to in the guide, and what exactly you are seeing.
- Does homematic manager connect to homegear correctly?
- Can you get through the pairing process successfully using homematic manager?
It’s connecting to the homegear server. And i am able to start pairing mode. But nothing shows up.
I’m not sure i am setting the configuration file up correctly. I sit possible to see if homegear detects the CUL?
11/14/18 11:20:23.269 Could not connect to socket. Error: No such file or directory
11/14/18 11:51:09.970 Could not connect to socket. Error: No such file or directory
11/14/18 11:51:12.001 Could not connect to socket. Error: No such file or directory
11/14/18 11:59:48.588 Could not connect to socket. Error: No such file or directory
11/14/18 11:59:50.612 Could not connect to socket. Error: No such file or directory
11/14/18 12:58:01.006 Could not connect to socket. Error: No such file or directory
11/14/18 12:58:03.142 Could not connect to socket. Error: No such file or directory
This is from the homegear-management.err
How are you running homegear ? - docker, local install, hassio etc…?
And what platform are you running.
I would guess from that log that the homegear instance cannot talk to the cube, so you’ll need to give us some information on your setup (IPs, config file entries etc…)