If you are on HA 0.68 you get the latest one I made on github. The first one did not work with 0.68 - because 0.68 now support more than one maxcube. (Was release about the same time as i uploaded the first version)
In the next HA version the pull request is merged .so you can get it here if you can’t wait:
Just wanted to update all. I have my interval now set to 10mins on HA and 6Mins on a different project (https://github.com/asantaga/PiHeating) and so far so good no issues…
I dont think HA needs to be kept up to date that often, i might even change HA to be every 15mins. My boiler controller does need to be a little more responsive but every 6mins is fine, and I have a physical/web button which overrides this…
All was working fine, HA polling every 30mins and my Raspberry PI every 15mins and all looked ok. but then oneday I was updating/tweaking HA and after the 10th restart of HA I noticed the MaxCube reset itself again… Im now convinced this is a synchronization issue and we should only have ONE device polling…
For now Ive disabled the HA Polling and are leaving my RaspberryPi Heating controller do the polling every 15mins.
I could go to pure HA, and let HA determine if the boiler needs to be turned on/off (send message via MQTT). The issue here is if you make changes to another part of HA the reboot will cause excessive queries to Max
I will extend my PiHeating to provide a REST API which delivers all the data to HA. The benefit here is the PiHeating will only query the cube at most every 15mins (or at reboot) and therefore wont matter if you constatly restart HA…
The Max Binding in HA could be modified so that it never queries the valves more than once every 15mins (configurable) , regardless of restarts…
What does everyone else ??
My other approach is to sell up the max stuff and move to Tado…they now have an api which looks nice
I’ve 5 max cubes in different houses. Working fine with the android app. I’ve tryied multiple times to set them on Home Assistant but i’ve always had (with different delay) the Cube reset!
So, also reading these posts, i think that the Max Cube component for Home Assistant should be removed waiting for a strong fix (and some angel working on it).
Now it’s not usable. I’ve found some PHP scripts to read all values from valves (also the valve offset which is not given trought Hassio component).
I disagree with removing the component but it can be improved for sure. there are some key values are missing from thermostats. Any developers can pay attention to it?
Reading through all problems with max cube in different smart home solutions, I am almost sure that the basic problem is the connection management in the cube. Using a permanent connection to the cube seems to be the solution. (Setting a higher polling interval just lowers the probability of loosing its configuration.)
The ha maxcube component has at least one another problem: it can’t display temperatures over some value correctly (I don’t remember now, 25.6 °C or something).
I think @cs42 is right about the connection issue. I think remmber openhab had the option to keep the connection open. Since April i have had one reset on the Max Cube.
The current library the Max Cube component in HA is using to connect to the Max Cube does not support keeping the connection open. It does not look like @hackercowboy (the author), is maintaining the library anymore, because he has not answered questions for a long time.
I currently don’t have the time to look at this (making a new library and HA component), but I think that is what is needed to solved the reset issue.
For my project (https://github.com/asantaga/PiHeating), I now poll every 15mins and all is good and I’ve removed the Max! component in HA. Before I had HA Max component AND my PiHeating project running at the same time and Id loose config every couple of weeks…
However I dont have the data in HA, or in InfluxDb/Grafana, which was nice…
I’m currently seeing how this goes, if all goes well (ie no resets) I will expand my PiHeating project so that it exposes the data via a REST call, and/or AutoDiscovery MQTT. I was considering building a HA Max! component for my project but not sure its needed (ie is someone else going to use it?)…
Anyway, waiting to see how this goes before spending more time on it…
Also I DON’T like keeping the connection permanently open as this means you wont be able to use the Native Max! apps… The wife likes the ability to raise/lower temperatures using the nice max apps, the only issue is the boiler controller wont see the change for up to 15/20mins… I have a “check heat” button on the app which she can press immediately but its not usually an issue (yet)
I managed to get everything up and going this weekend and it seems to work nicely.
I’ll be posting a bit of a setup guide when I get time, but the big plus is there should be no more issues with forgotten cube config!
Hi, do any of you using max cube on Hassio and it wokrking fine?
I am trying now for several months but problem is that after a while cube lose configuration.
Same to me, have to reconfigure it with 10 actuators (thermostats) in 8 rooms. But went well for a few month. Now (after several month) back again with the Cube empty… No news about this (ore somebody that has solved the problem?
To “solve” this problem, the maxcube interface needs to keep the communication open! Polling will trigger configuration loss, for some cubes sooner, for others later. Increasing the polling interval will trigger the problem just a bit later (if your’re lucky). If you’re in bad luck, it won’t help. I’m using http://www.dmitry-kazakov.de/ada/max_home_automation.htm now for a year or so and as it keeps open the connection, I do not have any problem anymore. Before when using FHEM or HA I head a configuration loss quite often (every few months)…
