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

tantararin · August 26, 2019, 3:08pm

{
“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”: [
“aarch64”,
“amd64”,
“armhf”,
“armv7”,
“i386”
],
“options”: {
},
“schema”: {
}
}

dewgenenny · August 28, 2019, 9:44am

I converted my Cube to a-culfw, however was quite disappointed how infrequently the thermostat devices would send in a temperature update - not nearly often enough to be able to make reliable automations based on the inputs.

FWIW I don’t have any wall thermostats, which I understand fixes this problem.

To get around it, I have written a small program that connects to HA and gets the devices, then connects to Homegear/MQTT and regularly changes the target temperature by 0.5 degrees +/- , which forces the thermostat to send an actual temperature update.

If anyone’s interested, I’ll be happy to tidy it up and share (even made a docker image for it :))

Klagio · September 8, 2019, 12:57pm

Now my second winter, and second attempt af flashing the Cube. Before flashing wish to install everything on HASSIO on my NUC

I followed the instructions of creating a config.json file in /addon/Homegear

but still I get

This add-on is not available on your system, when I add

.

Blaz_Komat · September 15, 2019, 4:11pm

I have same problem, I can install homegear but newer succed to start it. I use rp3

Blaz_Komat · September 19, 2019, 6:24am

Does anyone success to install homegear in fresh instaled hassio?

ganfoud · September 28, 2019, 5:09pm

hi all
I have trouble with the flashed firmware : it seems the communication b/w the wall thermostat and/or the cube is failing and it has consumed a whole set of batteries in 1 month where the previous ones lasted almost 1 year, and nothing have changed (position or composition)
do you know if there is a forum related to this firmware where I could get specific help?
thanks!

Jaroslaw_Walasztyn · October 2, 2019, 7:27pm

Hi,
I have sucessfully flashed maxcube , i have installed homegear (from deb package)on linux (without docker container) .

Now i try to pair but without any sucess, nothing show up when i try to pair devices(wall radiators thermostat Basic)

Cube reply for a ping,

#######################################
################ CUNX  ################
#######################################

## The device family this interface is for
[CUNX]

## Specify an unique id here to identify this device in Homegear
id = Jarcik

## When default is set to "true" Homegear will assign this device to new peers.
default = true

## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw
deviceType = cunx


## IP address of your CUNX
host = 192.168.2.6

## Port number your CUNX listens on. Normally 2323.
port = 2323

## Default: responseDelay = 95 ;  Should be "40" for CUNX
responseDelay = 40

What I’m doing wrong?

Blaz_Komat · October 3, 2019, 5:14am

From what repost did you install homegear?

Jaroslaw_Walasztyn · October 3, 2019, 12:58pm

I’ve used this tutorial -> https://homegear.eu/downloads.html?version=0.7&system=debian_stretch

Blaz_Komat · October 3, 2019, 1:23pm

So you have installed only homegear on one rpi?

Or you have instelled both to same rpi? (hassio and homegear)?

ganfoud · October 3, 2019, 6:58pm

have you checked the logs of homegear?

Jaroslaw_Walasztyn · October 3, 2019, 7:58pm

I’m not using rpi

Jaroslaw_Walasztyn · October 3, 2019, 8:12pm

Hi Ganfound,

There is nothing in the logs what could be suspicious. logs contains my try of pairing Cube with thermostat

logs from homegear.log i have pasted here -> https://pastebin.com/bx4AFSaj

homegear.err

10/03/19 22:01:09.698 Warning: Unknown node in "parameter": logicalFloat
10/03/19 22:01:09.698 Warning: Unknown node in "parameter": logicalFloat
10/03/19 22:01:09.699 Warning: Unknown node in "parameter": logicalFloat
10/03/19 22:01:09.700 Warning: configParameters with id "config" does not exist.
10/03/19 22:01:09.707 RPC Server (Port 2000): Error: For a family RPC server to listen on other addresses than "::1" or "127.0.0.1", SSL and authentication have to be enabled. Not starting server.
10/03/19 22:01:09.714 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.
10/03/19 22:01:09.714 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
10/03/19 22:01:09.721 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
10/03/19 22:03:13.607 UPnP Server: Error in file UPnP/UPnP.cpp line 239 in function void Homegear::UPnP::listen(): Your client is using a HTTP protocol version that this server cannot understand.
10/03/19 22:03:13.607 UPnP Server: Error in file UPnP/UPnP.cpp line 239 in function void Homegear::UPnP::listen(): Your client is using a HTTP protocol version that this server cannot understand.
10/03/19 22:03:13.607 UPnP Server: Error in file UPnP/UPnP.cpp line 239 in function void Homegear::UPnP::listen(): Your client is using a HTTP protocol version that this server cannot understand.
10/03/19 22:03:13.607 UPnP Server: Error in file UPnP/UPnP.cpp line 239 in function void Homegear::UPnP::listen(): Your client is using a HTTP protocol version that this server cannot understand.
10/03/19 22:03:13.608 UPnP Server: Error in file UPnP/UPnP.cpp line 239 in function void Homegear::UPnP::listen(): Your client is using a HTTP protocol version that this server cannot understand.
10/03/19 22:03:13.608 UPnP Server: Error in file UPnP/UPnP.cpp line 239 in function void Homegear::UPnP::listen(): Your client is using a HTTP protocol version that this server cannot understand.
10/03/19 22:03:13.608 UPnP Server: Error in file UPnP/UPnP.cpp line 239 in function void Homegear::UPnP::listen(): Your client is using a HTTP protocol version that this server cannot understand.
10/03/19 22:03:13.608 UPnP Server: Error in file UPnP/UPnP.cpp line 239 in function void Homegear::UPnP::listen(): Your client is using a HTTP protocol version that this server cannot understand.

Jaroslaw_Walasztyn · October 3, 2019, 8:21pm

I have figure out i did not install extension homegear-max , now it’s working and I’am able to pair.

swieprecht · October 5, 2019, 10:20pm

Hi, I’ve just taken the plunge and moved across to a CUN. I’m not good enough for doing it all via MQTT yet I dont think so went the Homematic Route. All showing in HA which is awesome but I have two (just one left) instant issues:

Google Home wont talk to the devices - they show as active in states and report current temperature, but google says device unavailable.

Help greatly appreciated

phipe · November 26, 2019, 8:27pm

Probably me being blind and cannot find it in the postings above, but how do you set a static ip on the flashed EQ-3 Max! Cube ?

ganfoud · December 1, 2019, 1:31pm

in your router settings!

steno · December 4, 2019, 3:12am

Hi guys,
i’m starting this project! Winter is coming
I would like to ask which is the difference between these two Homegear addon:

https://github.com/kreativmonkey/hassio-addons by @kreativmonkey

and this

https://github.com/stefangries/hassio-addons by @stefangries

Anyway, i’ve problems with both.
I’m runnning Hassio on a Raspberry PI
With the first one i’m having this problem:

19-12-04 02:37:57 WARNING (MainThread) [hassio.store.data] Can't read /data/addons/git/441b9bcc/homegear-rpi/config.json: required key not provided @ data['arch']. Got None
19-12-04 02:37:57 WARNING (MainThread) [hassio.store.data] Can't read /data/addons/git/441b9bcc/homegear/config.json: required key not provided @ data['arch']. Got None

So should be easy to be fixed, json only miss arch property.

With the second one, i’m able to install it but when i try to start it i get:

19-12-04 02:19:37 ERROR (SyncWorker_2) [hassio.docker] Can't start addon_69c7aa1d_homegear: 500 Server Error: Internal Server Error ("linux runtime spec devices: error gathering device information while adding custom device "/dev/ttyUSB0": no such file or directory")

phipe · December 8, 2019, 4:53pm

OK, had a hope it was possible on the box and not using dhcp reservation in the router. But thanks

steno · December 8, 2019, 11:09pm

so thanks to @capfirepants and @swifty i’ve been able to set up everything. Now i’ll have to repeat this procedure with others cubes (in different houses).
And i’ll try with the “2 cubes configuration” in one of these.
Anyway i saw that MQTT seem more convenient then homematic integration. Why? Only to avoid to have one more layer or there is some difference within performance?
I’ve around 70 valves to configure and homematic configuration is much faster and i would prefer this.