Thermostat scheduler not changing setpoint on schedule

I'm was running 2.3.3.134 and just updated to 2.3.3.140 to see if it fixed it (it doesnt) although i dont see anything in the release notes about this problem.

I've noticed that Thermostat Scheduler isnt changing the setpoint at the selected time. For example, here's my dining room schedule:

if i look at the logs for the device, i see this. i've stripped out many duplicate lines but kept the lines around the times of scheduled changes - you can see that there is no event relating to schedule change:

dev:112022-11-14 12:46:06.338debugRefresh - Temperature is: 19.7 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-14 12:41:06.430debugRefresh - Temperature is: 19.7 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-14 12:36:06.324debugRefresh - Temperature is: 19.8 - Setpoint is: 18.0 - Calling for heat? false
...
dev:112022-11-14 09:11:07.029debugRefresh - Temperature is: 19.3 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-14 09:06:06.427debugRefresh - Temperature is: 19.4 - Setpoint is: 18.0 - Calling for heat? false
...
dev:112022-11-14 06:36:06.634debugRefresh - Temperature is: 20.1 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-14 06:31:06.542debugRefresh - Temperature is: 20.2 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-14 06:26:07.191debugRefresh - Temperature is: 20.2 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-14 06:21:07.148debugRefresh - Temperature is: 20.2 - Setpoint is: 18.0 - Calling for heat? false
...
dev:112022-11-13 23:36:06.739debugRefresh - Temperature is: 20.4 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-13 23:31:07.035debugRefresh - Temperature is: 20.5 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-13 23:26:06.634debugRefresh - Temperature is: 20.5 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-13 23:21:06.684debugRefresh - Temperature is: 20.4 - Setpoint is: 18.0 - Calling for heat? false
...
dev:112022-11-13 20:06:07.135debugRefresh - Temperature is: 20.1 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-13 20:01:07.289debugRefresh - Temperature is: 20.1 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-13 19:56:06.790debugRefresh - Temperature is: 20.1 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-13 19:51:06.837debugRefresh - Temperature is: 20.2 - Setpoint is: 18.0 - Calling for heat? false
...
dev:112022-11-13 10:06:06.334debugRefresh - Temperature is: 19.7 - Setpoint is: 18.0 - Calling for heat? false
dev:112022-11-13 10:01:06.523debugRefresh - Temperature is: 19.8 - Setpoint is: 18.0 - Calling for heat? false

What's interesting is:
a) I dont have an 18 degree temperature set. I did, but i changed it at around 7am this morning, well before the trigger to move to 'daytime'. It shoudl have gone to 16 degrees at 9am.
b) it didnt go to 16 degrees at 9am.

I see a similar thing on other schedulers e.g. lounge, although it did switch last night and this morning:

dev:152022-11-14 12:48:04.325debugRefresh - Temperature is: 19.9 - Setpoint is: 20.0 - Calling for heat? false
dev:152022-11-14 12:43:05.127debugRefresh - Temperature is: 19.9 - Setpoint is: 20.0 - Calling for heat? false
...
dev:152022-11-14 09:08:05.025debugRefresh - Temperature is: 19.9 - Setpoint is: 20.0 - Calling for heat? false
dev:152022-11-14 09:03:04.421debugRefresh - Temperature is: 20.0 - Setpoint is: 20.0 - Calling for heat? false
dev:152022-11-14 08:58:04.422debugRefresh - Temperature is: 20.0 - Setpoint is: 20.0 - Calling for heat? false
dev:152022-11-14 08:53:04.626debugRefresh - Temperature is: 20.1 - Setpoint is: 20.0 - Calling for heat? false
...
dev:152022-11-14 06:38:04.952debugRefresh - Temperature is: 20.5 - Setpoint is: 20.0 - Calling for heat? false
dev:152022-11-14 06:33:04.640debugRefresh - Temperature is: 20.5 - Setpoint is: 20.0 - Calling for heat? false
dev:152022-11-14 06:30:08.063debugRefreshing thermostat data from parent
dev:152022-11-14 06:30:03.582debugsuccess on last command: [result:temperature was set]
dev:152022-11-14 06:30:03.436debugsuccess on last command: [result:temperature was set]
dev:152022-11-14 06:30:03.151debugsuccess on last command: [result:temperature was set]
dev:152022-11-14 06:29:13.348debugRefresh - Temperature is: 20.6 - Setpoint is: 20.5 - Calling for heat? false
dev:152022-11-14 06:24:13.376debugRefresh - Temperature is: 20.7 - Setpoint is: 20.5 - Calling for heat? false
...
dev:152022-11-13 23:39:13.743debugRefresh - Temperature is: 20.3 - Setpoint is: 20.5 - Calling for heat? true
dev:152022-11-13 23:34:14.035debugRefresh - Temperature is: 20.1 - Setpoint is: 20.5 - Calling for heat? true
dev:152022-11-13 23:29:13.528debugRefresh - Temperature is: 20.0 - Setpoint is: 20.5 - Calling for heat? true
dev:152022-11-13 23:24:13.740debugRefresh - Temperature is: 20.0 - Setpoint is: 20.5 - Calling for heat? true
...
dev:152022-11-13 17:04:14.241debugRefresh - Temperature is: 20.1 - Setpoint is: 20.5 - Calling for heat? false
dev:152022-11-13 17:00:06.694debugRefresh - Temperature is: 20.1 - Setpoint is: 20.5 - Calling for heat? false
dev:152022-11-13 17:00:06.282debugRefreshing thermostat data from parent
dev:152022-11-13 17:00:01.428debugsuccess on last command: [result:temperature was set]
dev:152022-11-13 16:55:30.685debugRefresh - Temperature is: 20.1 - Setpoint is: 20.0 - Calling for heat? false
dev:152022-11-13 16:50:30.831debugRefresh - Temperature is: 20.1 - Setpoint is: 20.0 - Calling for heat? false

r

@user734

it's been working fine until today, so not sure it's that as ecoMode hasnt changed.

I have ecoMode linked to my outdoor thermostat and it comes on when the outside temperature exceeds 20c - it's been about 8-10c overnight :cold_face:

@bravenel any ideas? The issue is still occurring

Need to see logs for the app -- use screenshots only.

They should both have switched at 2330 but they didn’t. Some other events did trigger during the day.

Eg this one missed the switch at 0900, 1530 and 2330 but did hit 0630 and 1700

Device logs don't tell anything about the app. If you want help, you have to post the app logs. for a period when it is supposed to do something. Also, post the Scheduled Jobs from the App Status page (gear icon).

Sorry yes I realised that after I posted it and edited the post above to replace with app logs. Here’s the scheduled tasks.

Go into the app itself, turn on debug logging and post those...

there's no "Debug" logging level. The only logging option is already enabled.

Any ideas what I should do? Is there a way to force it to recreate the scheduled tasks?

Just open the app and hit Done. Then look at the Scheduled Jobs at the bottom of the App Status page.

Ok I did that but the events still aren’t scheduled:


I will dig in further....

Download the Hubitat app