Hello everyone, I’m new to the world of home automation and I’ve been experimenting with openHAB for a few weeks now. I’ve set up my system using configuration files instead of the PaperUI, and while I’ve managed to get most things working, I’ve encountered a persistent issue with my Max! thermostats.
My Issue: My Max! thermostats frequently lose their connection to the Max! Cube. I’ve been using these thermostats with the Max! environment for over a year without any problems. However, since integrating them into openHAB, the connection issues have started occurring regularly. Restarting the Cube resolves the issue temporarily, so I don’t believe it’s related to low battery levels.
I’ve noticed that the Cube receives a lot of requests every 30 seconds to verify the temperature, which might be causing the instability. Here’s a snippet from my log file:
2019-11-10 10:26:44.134 [DEBUG] [nternal.handler.MaxCubeBridgeHandler] - Sending request #100 to MAX! Cube
2019-11-10 10:26:44.191 [DEBUG] [b.binding.max.internal.device.Device] - Device 0d3386 (Thermostat): Actual Temperature : 23.7
2019-11-10 10:26:44.195 [DEBUG] [b.binding.max.internal.device.Device] - Device 137b66 (Thermostat): Actual Temperature : 0.0
2019-11-10 10:26:44.197 [DEBUG] [b.binding.max.internal.device.Device] - Device 0d323a (Thermostat): Actual Temperature : 0.0
2019-11-10 10:26:44.201 [DEBUG] [b.binding.max.internal.device.Device] - Device 0d345e (Thermostat): Actual Temperature : 22.8
At times, I also see discovery requests like this:
2019-11-10 10:28:23.339 [DEBUG] [nal.discovery.MaxCubeBridgeDiscovery] - Run MAX! Cube discovery
2019-11-10 10:28:24.180 [DEBUG] [nal.discovery.MaxCubeBridgeDiscovery] - MAX! Cube found on network
2019-11-10 10:28:24.182 [DEBUG] [nal.discovery.MaxCubeBridgeDiscovery] - Found at : 192.168.178.20
2019-11-10 10:28:24.184 [DEBUG] [nal.discovery.MaxCubeBridgeDiscovery] - Serial : KEQ0537546
2019-11-10 10:28:24.187 [DEBUG] [nal.discovery.MaxCubeBridgeDiscovery] - RF Address: 0b9715
2019-11-10 10:28:24.189 [DEBUG] [nal.discovery.MaxCubeBridgeDiscovery] - Firmware : 01.13
It’s also worth noting that not all thermostats lose their connection simultaneously. Sometimes it’s just one, other times two. The rest of the devices, including the Cube itself, continue to function properly during these issues.
I found a similar topic on another forum eQ-3 MAX! connection error, but in my case, no other software is connected to the Cube since openHAB takes over the connection as soon as it’s online.
Has anyone else experienced this issue with Max! thermostats in openHAB? I’m curious if the increased traffic from openHAB compared to the native Max! environment could be causing this behavior. Any insights or suggestions would be greatly appreciated!
Thanks in advance for your help!