Hey everyone! I wanted to share my experience with the Max! Cube and how I managed to resolve the weird behavior I was encountering. It’s been a bit of a rollercoaster, but I’m happy to say I found a solution!
For those who haven’t heard, I’ve been using the Max! Cube with 15 Thermostat+ units for over a year now. It’s been a reliable setup, but recently, I noticed some odd commands being sent to my thermostats. The logs showed that the Cube was setting temperatures to 17.5°C, which I never programmed myself. At first, I was a bit puzzled—was it a bug, or was there something wrong with my setup?
After some digging, I realized the issue might be with my max.things configuration file. I had set up each thermostat with a refreshActualRate of 60 seconds, which I thought was a good balance between responsiveness and resource usage. But it turns out this setting was causing the Cube to send unnecessary commands, especially when the duty cycle was high. The duty cycle was hitting 80%, which made the Cube wait before sending more commands, but this delay led to the unexpected temperature changes.
I decided to tweak the refreshActualRate values. Lowering them to 30 seconds for most thermostats and 60 seconds for others seemed to help. This adjustment reduced the number of commands being sent and stabilized the system. I also made sure to back up my configuration using the telnet method mentioned in the forums, just in case I needed to reset the Cube in the future.
Another thing I did was check the Cube’s firmware. Updating it to the latest version (01.13) ensured that any bugs from previous versions were patched. The Cube now runs smoothly, and I haven’t seen those mysterious 17.5°C commands anymore.
This experience taught me the importance of configuration settings and how even small tweaks can make a big difference. I’m relieved to have my thermostats working as intended, and I hope this story helps someone else facing similar issues. Happy automating! 