It seems like my Thermostat Scheduler is stuck in "Control Thermostat Manually" and not following my schedule. I look in my log files and see the changes being made by the scheduler, but the thermostat doesn't change.
If I set the mode to away the thermostat turns off as set by the scheduler but when I return it goes back it to manual mode and doesn't follow the schedule.
Look at the logs for the device, or better yet, look at its Events, from the button at the top of the device page. Those logs suggest that Thermostat Scheduler is sending the commands.
Installed a virtual thermostat and that seems to be working.
Changing drivers for my thermostat to generic drives didn't fix it.
All manual functions work fine scheduler does not.
Installing my backup and downgrading to 2.3.1.130 fixed my problem.
Radio Thermostat CT101 doesn't work well with the latest update
Version 2.3.4.139
Just came across this thread after reporting virtually identical experience in other posts with my Radio Thermostat CT32 using either the CT101 driver or the Generic z-wave driver. The difference in my case is that I only began experiencing issues reported above (and in my other threads), when moving up from 2.3.4.138 or 2.3.4.140. Prior to that time (about two weeks ago) all worked as expected when the Thermostat Scheduler transitioned from one time period to the next. Will be anxious to see that the Hubitat team discovers is the cause.
We are still investigating the CT100/CT101 issue. This is a problem that is specific to that thermostat, and involves it failing to respond to two commands sent in quick succession. Specifically, setting a heating setpoint and the thermostat mode in quick succession fails.
There is a work around until we figure out the cause of this: Don't use Thermostat Scheduler to set the thermostat mode. Instead, use a Rule that is triggered either at the same time, or upon whatever event makes sense, and after a 10 second delay, set the thermostat mode. Something along these lines should side step the problem.
We are a bit baffled by what is causing this, but will track it down until it is resolved.
Following up on Bruce's suggestion, I created a RM rule for the morning and evening that sets the desired temperature, delays 10 seconds and then set the mode followed by a 3 hour delay, etc. This works reliably and I plan to use this until the identified issue is resolved in a future update.
I now observe an interesting sidepoint that I'd like to understand a little better. Specifically, it now seems that the Thermostat mode is being set to the setting for the period when the mode changes from night-to-day and day-to-night. What seems strange is that nothing happens when at the transition from evening-to-night around 6:20PM. Actually, with the Thermostat Scheduler in the Hold mode, I wouldn't expect anything to change with the mode transition. Am I missing something, or is the Thermostat Scheduler just injecting a bogus mode setting?
Sure appreciate all thoughts as I come to better understand the household temperature challenges.
Bump for an important function as a new owner of a CT32 thermostat. (was unhappy with the wide 2°F swing of the GoControl GC-TBZ48 I had, and hoping the 0.5° adjust in the CT32 solves the issue).
Any progress on a fix for this? My thermostat still doesn't follow the scheduled time changes. It was working for a bit, now just stuck at my waking temperature
