Guys, I've found a fairly huge bug with this plug-in in when using any thermostat or zone controller that had dual setpoints. The 'feature' occurs when you use the web interface and set the setpoints via a script or event. The scenario is this, if you set the heatpoint, BUT your thermostat is currently in the 'cool' mode, you'll actually set the cool setpoint. If your thermostat is currently heating, and you set the cool setpoint, you'll set the heat setpoint. Thus, you can imagine what happened when I set my heat setpoint to 65, but had the thermostat set to cool, we ended up with a very cold house. You can easily duplicate this with the web interface. Just set the setpoint of the opposite of whatever your HVAC is currently calling for, running or not, you'll find the wrong set point gets set.
Now, if your scripts or events set both the heating and cooling setpoints at at the same time, this bug would go un-noticed. However, I recently commented out a line of code in one of my scripts that set a cool setpoint, and presto, the bug showed up.
If anyone wants the technical details I can add the info. I have submitted a help desk ticket for this and it should be a quick and simple fix.
Now, if your scripts or events set both the heating and cooling setpoints at at the same time, this bug would go un-noticed. However, I recently commented out a line of code in one of my scripts that set a cool setpoint, and presto, the bug showed up.
If anyone wants the technical details I can add the info. I have submitted a help desk ticket for this and it should be a quick and simple fix.
Comment