If you have the Scheduler integration/device visible the component is properly configured.
For the card, you need to look under āfrontendā in HACS (not āintegrationsā).
Adding it under resources should actually be done automatic nowadays, so you can skip this step (unles HACS tells you to do so).
The next step is indeed to click the + and add the card (it should be somewhere at the bottom).
If the last step fails, please check your browser logs. There should be a little banner āscheduler-cardā with the version number installed (and no errors of course).
The option shows up in the latest version of the card, see here for more info.
Note that there is a bug in the behaviour, I will probably release an update in a few days for that.
On the retry action function: what does it mean entity unavailable? If e.g. my thermostat is set to āoffā is it available or not? Iām trying to implement āaway modeā function where Iām turning my thermostats off and I would like to set the scheduler not to change thermostat temperature while itās off but to retry to set it according to schedule when the thermostat is back on. Is it possible? If not, do you see any workaround? I could create some automation that would be triggered on āaway modeā being turned off and would set all thermostats back to their setpoints, but Iād have to get them from the schedule first. How can I get set value for current timeslot for given entity?
Got it working now! I simply removed the configuration in Lovelace resource tab, added it again and it was solved. Scheduling is working fine now (big thanks for creating this essential feature!)
It should run the weekend ones (scheduler considers weekend as ānot workdayā so holidays are included).
Does the workday sensor say itās āoffā ?
What is shown in the card as next occurrence for the weekend jobs?
Iām wondering whether itās possible to know whether a scheme is currently in a phase where it has turned a device on.
I have schemes set up to schedule my pool filter, sweep, chlorinator and heat pump (via a climate integration). This all works beautifully. But I would also like to, say, set up a function to run the sweep for a configurable about of time (probably using an input_number slider) for those times that I want it to run a bit longer. When the sweep runs, the filter must run too. This ātop-upā could be during a time when a scheme has the filter running. When the ātop-upā timer expires, I would need to turn the filter off, unless it should remain on because a scheme requires it to be on. Is it possible to test for this in some way?
@Sddawson
One thing that might help you is checking the current_slot property of a schedule entity.
It represents the number (starting at 0) of the slot which is currently active.
In case no slot is overlapping, the value is null.
There is currently no way to relate the slot number to certain action, so if you have both slots with āfilter onā and with āfilter offā, they will be hard to identify.
I might be able to make changes to make it possible to identify this, if this would help you please open a feature request.
Perhaps you could change the schedule to only have slots for āfilter onā and use automations to turn off the filter when current_slot becomes null (and your top-up routine is not running of course).
Thanks very much for your thoughts. I have quite a few different schedules that cover day running, night running, summer, winter etc, so the current_slot Idea might not fly - the filter runs arenāt always in the same slot in each schedule.
Iām thinking that I could run a script whenever a slot turns the filter on (instead of controlling it directly), and the script could use an input_boolean to indicate that the filter is running in a schedule, before turning the filter itself on. Then I can use the input_boolean in the ātop-upā sweep run to decide whether or not to turn off the filter when the timer ends. A slot that turns the filter off runs a similar script to turn off the input_boolean before turning the filter off. Should workā¦
May be I am missing some obvious point but I have the following problem : when I modify an existing schedule and I āsaveā it, and then I open it again I see that none modification was made.
I am using the āsaveā button. I just deleted my schedule and recreate itā¦ and now I cannot reproduce the problem (???).
Edit : I had changed the name of my previous schedule (the problematic one) after to have created it, using Config/Entity dialog. May be the cause of the trouble.
I noticed some odd behaviour, I believe, if the next day was a non-workday when I edited the schedule it would work as expected, but the following day nothing would trigger again.
Same thing, if I edited it the current and next days would trigger but again not the following day.
I ended up creating a holiday schedule and just disabled the old ones as I didnāt have time to diagnose.
When I get a bit of time, Iāll create some non workdays and test over a few days to see what happens
