I'm getting spurious setpoints which really mess things up for a while. I think what happens is the setpoint is out of range, the plugin detects that, then sets it to the range limit. Eventually the next schedule change hits and it corrects itself, if I don't catch it first. Here is some sample log output:
Let me know if there is some additional data I can gather. The time that the 171 came in is not associated with any schedule change, and no one was messing with the tstat.
David
| 6/15/2022 10:33:25 AM | Information | Tramonto Thermostat Main (5) | System is now Idle |
| 6/15/2022 10:32:43 AM | Information | Tramonto Thermostat BR (4) | Temperature has changed to 77.5 |
| 6/15/2022 10:29:59 AM | Information | Tramonto Thermostat BR (4) | System is now Idle |
| 6/15/2022 10:29:58 AM | Information | Tramonto Thermostat BR (4) | Temperature has changed to 78 |
| 6/15/2022 10:29:58 AM | Action | Tramonto Thermostat BR (4) | Cool Setpoint set to 82 |
| 6/15/2022 10:29:58 AM | Action | Tramonto Thermostat BR (4) | Cool Setpoint set to 82 |
| 6/15/2022 10:29:58 AM | Action | Tramonto Thermostat BR (4) | Cool Setpoint set to 171 |
Let me know if there is some additional data I can gather. The time that the 171 came in is not associated with any schedule change, and no one was messing with the tstat.
David