Hello
I have just started to move a few automations over to this scheduler and most work really well. I have one issue I was hoping for some help with please. I have a TV triggered on/off as a condition by a Hue motion sensor. This works but the TV goes off really quickly as soon as motion is clear. I have tried changing - re-evalutate condition and repeat but I can’t make it stay on longer. In normal automations there is a duration condition…
for:
hours: 0
minutes: 5
seconds: 0
I can’t find the yaml to try directly editing it so was hoping if this could be added as an option in the conditions selection or perhaps I’ have just missed it somewhere.
You cannot. A schedule is limited from 00:00 - 23:59.
You cannot. Scheduler doesnt support templates. As workaround you could have scheduler trigger a script, and in that script you set the heat to the desired/templated
You could enable debug logging for scheduler. You will see in the HA logs exactly what scheduler does and when.
From the picture it looks like scheduler did trigger at 2 PM and turned off the pump, but 4 seconds later it was turned on again (by something else?).
Unfortunately it’s not possible to delay the retriggering of a schedule due to changing conditions.
The only workaround I can think of, is to make a template sensor which mimics the state of your Hue motion sensor, but with a delay, and use that in the schedule.
Example code:
template:
- binary_sensor:
- name: "Delayed Hue Sensor"
delay_off:
minutes: 5 # can also be in seconds
state: >
{{ is_state('binary_sensor.<my_hue_sensor>','on') }}
Hi,
Would someone happen to know why my time choosing numbers are placed wrong?
It shows decimals in the hour box and nothing in the minutes box. The arrows however work as they should. I have redownloaded everything and tried with pc and mobile.
Hi @neliss and thanks for this card.
It’s working great, I’ve set it up for the heating of 5 different rooms in my home, where each of them has its own thermostat and scheduling.
Anyway, for this specific case, i find annoying that i cannot have a glance of the 5 timelines of the 5 different scheduling of the thermostats. Since every room has a different one, i have to check each of them by clicking on the scheme and i don’t have a way to see (or even better change) one of them while looking the others.
Do you think there is a trick or something that i’m missing in order to achieve that?
Your second timeslot doesn’t have a stop time, I suppose this causes the problem?
Additionally I would recommend to use full time format, i.e. “08:00:00” (not sure if this is required).
The attributes of the schedule entity in Developer tools → States could be interesting to check, I suppose this is more an issue with the scheduler component than the card.
It was the full time format that was the issue. Thanks so much for your help! And particularly thanks for still working hard to maintain this and still answering questions on it all
If I click on add a new section appears and within the next few seconds it goes away again. Some times it lasts longer and I can press save but when I go back into it the added bit has gone again. If I adjust the time 9 times out of 10 it doesn’t persist. Has the component become corrupt or am I doing something wrong. Doesn’t matter if I use chrome, edge or samsung internet. Restart HA, reload scheduler nothing makes a difference.
No numbers appear in the boxes. I can type in numbers ( they are visible if I highlight the box, but they aren’t retained after saving and going back in.
Please check your browser logs and verify you’re on the latest version of the card (v2.3.7).
If not, update the card or clear your browser cache.
If this doesn’t help, create a bug report in GitHub.
Hi @neliss - loving Scheduler card & component - very useful.
Is this possible?
I want to have a schedule that does the following:
During the daytime, say 09:00 - sunset, turn on and enable an automation (which turns a light on/off according to PIR status).
At sunset, disable the automation and turn on a specific set of lights
At midnight, turn off those lights.
I’m trying to figure out if this could be done in one schedule, which contains different domains/entities and some of which need to be turned on/enabled and others need to be turned off/disabled.
Thanks for your enthusiasm for this project
Unfortunately, you would need 1 schedule for controlling the automation, another for the lights.
I wish it was possible in HA to configure an action to be triggered when turning on/off an automation, it would be a very powerful feature.
Unfortunately you can only trigger on changes in other entities (not itself) in an automation.
As a hack/workaround, you could add a custom action to a light entity (or group) in the card (via customize in yaml), for turning on/off the automation.
Theoretically this way you could create a schedule where in one timeslot the light is controlled, in the other the automation.
But this is definitely not how scheduler is intended to be used.
I am thinking of moving the editor of the scheduler (the pages for picking entities, time, etc) to a dialog rather than keeping it inside the card.
The main advantage is that a dialog is not limited to the column width assigned to cards, so on PC/tablet there will be more space for placing the time bar, perhaps also more guidance text to make things more easy to understand.
Before getting into this I’d like to collect your opinions, since there will be no way back
Moving the scheduler editor to a dialog
Good idea, can’t wait to see this happen!
I prefer the card as it works now, don’t change it.
Good evening, I started exploring this scheduler component a few days back and it seemed a perfect match for scheduling my thermostats.
But I am facing an issue with my Tuya TV02 thermostats: whenever I am switching them with turn_on, they fallback to preset state=auto.
In that state the scheduler conflicts with the devices’ builtin scheduler, i.e. both schedulers fire events. That’s why I tried to configure them preset_state=manual
Next thought was, instead of binding scheduler to climate entities, bind to proxy switches instead and script some automation.
But I can’t see how I could enrich the time slots with temperature values - which is supported for climate entities.
But I am facing an issue with my Tuya TV02 thermostats: whenever I am switching them with turn_on, they fallback to preset state=auto.
Why do you use the ‘turn on’ action, instead of switching the operation mode (to heat) and providing a setpoint?
What do you mean exactly by preset state? A climate device has a state and a preset mode, preset state seems a mix of both terms.
Can you share the properties of the entity as shown in Developer Tools → States?
Why do you use the ‘turn on’ action, instead of switching the operation mode (to heat) and providing a setpoint?
That’s done by another (Node red) automation: turn off thermostat if window is open for a while, turn on when closed. But following your advice, I could modify that to heat/setpoint to a frost protection value, thus permanently remain in reset mode =manual.
What do you mean exactly by preset state?
Preset mode seems better term. Values are “off”, “manual”, “auto”, “holiday”. In auto mode the thermostator runs it’s own schedule.
Meanwhile I built some support for modifying the builtin schedules (per weekday, thermostator) via HA dashboard, but I really like the comfortable user interface of your scheduler component.
Maybe bet on “Better Thermostat”, which integrates with your scheduler and comes with “open window” support. Here, I am missing the option to configure a delay, to avoid battery consumption on every short window open.
