Schedule randomly don't trigger

[RillesM]

Checklist

• [ x] I checked for similar existing issues (both open and closed) before posting.
• [x ] I am running the latest version.

Expected behavior

I have few climate scheduler defined on a scheme setup. All are coordinating one or multiple thermostat (built on Versatile Thermostat driving few Sonoff TRVZB).
The expected behaviour is that all the thermostats are activated based on the scheme defined.
Tasks are configured through the Card component.

Actual behavior

Randomly, some or all of the planned actions are just not executed (thermostat stays on off) while the tasks displays in the card component that the action have been triggered.

My main issue is that I can't find any usable log info that I can use to point a (still probable) configuration issue) or any other error, the whole system acts like everything went fine.
With any guidance on where to look or how to activate more debug info, I'm happy to provide more info.

This morning for example, my bathroom thermostat should have gone from "off" to "heat with preset comfort" at 5am but did not triggered. Once I was aware, I opened the home assistant app and the action was triggered at that exact time.

Steps to Reproduce

It's a random issue so except by using same hardware setup I can't really ensure I can reproduce it in real time.

[jiquem]

I have the same behaviour on a Versatile Thermostat which is managing 2 Sonoff TRVZB.

[puetsch]

I'm experiencing the same. The scheduler is not 100% reliable, unfortunately, when working with the "simple thermostat" in my case.

The schedule is supposed to a) switch to 22C and b) turn the heating ON. I sometimes find it only does 1), so the temperature is set but the thermostat still OFF.

[yachtboy33]

I am also having this issue with schemes for my thermostat. I have 3 mini splits in 3 rooms (areas), each mini split is its own entity. I set them each up with very basic schemes, but I can't get them to work consistently. The logs don't show me anything useful.

For example, since we are in heating season the living room HVAC is set to go down to 63 overnight (11pm-1159pm, and then again from 12am-630am) and then come back up to 69 from 630am to 11pm. Last night it did not go down at 11pm. But the midnight one did. Then at 630 the temp went up as scheduled. But randomly around 11am I noticed it had changed itself back to 63. I hadn't touched HA yet today. The log doesn't show this change.

Similarly, in the bedrooms the heat is set to turn off at 8am and come back on at 7pm. But in both bedrooms the heat went off (according to the logs) at the same random time of about 9:56am.

[Glesa-Gilles]

This linked ticket could probably help. Getting out of our holiday season where family was more present at home I had changed my schedules and had less issues (not sure but I think I had no issue). The changes where in majority:

• reduction of the number of schedule (no diff with wednesday, weekend) so basically divided amount by 3 of active schedulers. Don't think it's the root cause
• avoided any cases where thermostats are turned off and used a preset to "simulate" a off with target temperature as low as possible

Since this monday, I kept the number of scheduler active as low as possible but re-used the switch off for the period of the day when house is empty. Issues started again so I guess this enforce the link with issue 868.
My only addition is that (on my side) the issue is not 100% reproducible.
For example, one scheduler manage 2 heaters in the same way. One was switched on on correct preset, the other one was still turned off.

In order to help I would like to find a way to isolate the issue between scheduler or thermostat (or even communication layer through MQTT and Zigbee). Currently, the thermostat log of the faulty devices do not display a log saying they received the "switch on" command but that doesn't mean it wasn't sent. Is there a way to increase log level of scheduler to see an audit of what was triggered exactly ?

[nielsfaber]

Unfortunately I have been unable to reproduce this issue.
My suspicion is that the issue is related to running HA on a processor with limited resources (such as Raspberry pi) and while the processor is running multiple tasks simultaneously.
My knowledge of multithreading and asynchronous processing is limited. There might be a bad construction in the code, causing the indeterminate behavior.

[yachtboy33]

If it helps, I switched to the Simple Scheduler add on. That resolved some of my issues, but not all. I have still had random temperature resets on just the living room unit, once at 9:56am and a second time the following day at 11:53am, both times setting the temp to the minimum setting. The bedrooms seem to be unaffected so far. So it appears that this is not limited to scheduler card.

Simple Scheduler also struggled with turning the heat off completely and then back on, which I saw in a linked issue. It tried to set the thermostat to "auto" instead of "heat," which seems to have confused the mini split system since that could result in one head unit trying to cool while another one heats. For now, I just have it switching to different heat set points.

I am running HA on the Home Assistant Green using the app interface on my iphone and the browser interface on my Mac.

[zippety-stu]

I have a very similar issue.
Schedule was operating my Tado system correctly until around 2-3 weeks ago.
Some (not all) schedules were not setting the TRV temperature at the specified time, so the temperature remained at the previous setting.
I could correct this by setting the affected schedules off, then turning on again. Occasionally I had to do this twice to get the required schedule correctly operating.

HAOS, fully updated as of 26 January 2025.
Scheduler version 3.3.8 - I'm not sure how to determine when I updated to this version, .
(I use Scheduler in conjunction with Better Thermostat v1.6.1)