Has something changed with Activate Scheduled Setpoints in Thermostat Scheduler?

[wfoley]

Back in early 2.3.4 days I was able to get the Thermostat Scheduler set the Thermostat to the correct temperature for the time period by invoking this rule:

More recently (with 2.3.5.123), this doesn't seem to work. I'm not a coder, but wonder if this error which occurs when I turn the Furnace disabled virtual switch off provides any guidance as to what is no longer working as it did before?

[bravenel]

I would suggest that you remove that one action and then create it again. See if that clears this up. You can just use Run Actions to test it.

[wfoley]

Deleted the action twice and re-entered, then did the Run Actions to no avail. ThermostatSetpoint didn't change from 60 to the 55 which was appropriate for the time of day.

But, I wonder if my adjusting the time periods table such that the temp and the mode change don't occur at the same time (which has been working) puts me in a position where at 5:51PM (in the Leave + period) I am in a time period wherein the Thermostat Scheduler has no target Heat setting?

Might the (hopefully temporary) fix for my CT32 thermostat have caused this problem?

[bravenel]

I forgot you have a CT32. I tried to up the delay between the setThermostatMode command and setting the setpoint, apparently to no avail. So I'm back to not understanding what is going on with that thermostat.

All I can suggest is to not set thermostat mode in Thermostat Scheduler at all, and do it some other way.

Or, replace the thermostat with a good one.

[wfoley]

Still struggling to understand what might have happened back in the 2.3.4.110 era when everything worked with my Radio Thermostat CT-32. But, I've taken Bruce's hint/suggestion and upgraded to a 2GIG-STZ-1. All is well now. Using the Generic Z-wave Plus driver, thermostat is correctly responding to Thermostat Scheduler commands (at least for the past three period changes).