Scheduler card/custom component

[KTibow (Kendell R)]

standard_configuration:false

[ribbonofblack]

Perfect, thank you for the help

[thorschtn (Thorsten)]

Why can’t I set a schedule in my scheduler card depending on sunrise and sunset?
The Sun.Sun integration is installed and has filled attributes. Nevertheless, the sunset/sunrise symbol remains gray in the scheduler card and cannot be clicked on. What am I doing wrong?

[tonioa (Anthony Séjourné)]

Thanks @neliss it’s now working fine on 0.114 also

Just one point seem the character ‘é’‘è’ are not supported on the group name, when i set “Lumière” for the group name i have the following error

Invalid configuration provided (1 error(s)). In groups/0 ‘name’ should match pattern “^[a-zA-Z0-9_\ ]+$”.

[neliss]

@tonioa I got the same feedback from a russian user. Will make sure to solve this in the next update.
Sorry for it.

[neliss]

@ribbonofblack

Is it possible to remove actions from the card?

I have created a customised action for a script which allows me to set a number. This is the only way I want to be able to run the script - I don’t want the “run, turn off, turn on” options - only my customised one

As far as I know, for script entities you can only call turn_on, turn_off and script.<script name> as services. The last one is renamed to ‘run’ in the standard configuration (to be more clear than repeating the entity name).
Why would these options not be sufficient for your usage?
And for what reason would you like to hide actions?

I’m asking for improving the card

[Cadster]

@thorschtn

Why can’t I set a schedule in my scheduler card depending on sunrise and sunset?
The Sun.Sun integration is installed and has filled attributes. Nevertheless, the sunset/sunrise symbol remains gray in the scheduler card and cannot be clicked on. What am I doing wrong?

Here is your answer.

[thorschtn (Thorsten)]

Thanks a lot. That solves my problem.

But it’s an interesting click path. I first select a time in order to get the button activated, via which I can enter a relative value that overwrites the fixed time that I entered earlier. I would never have guessed that.

[neliss]

@thorschtn

But it’s an interesting click path. I first select a time in order to get the button activated, via which I can enter a relative value that overwrites the fixed time that I entered earlier. I would never have guessed that.

You’re not the first to be confused by it.
It will be replaced (at some point) to simple choice ‘fixed time’ or ‘relative to sun’.
For relative to sun, the offset will become optional (currently it has the emphasis).
Also dawn and dusk will be selectable (I got a request for it).

[ribbonofblack]

I’m using the “run” script option but have a customisation that has an input_number variable.

My use case is for an irrigation controller. I’m able to turn the valve on via the scheduler, it’s just a simple switch entity.
Im using the input_number to set a run time in minutes for the irrigation zone.
Then an automation to turn it off after that time.
The input_number is also used to set a fail safe on the irrigation controller to handle the case if the irrigation controller looses connection the water will still turn off.

I hope this makes sense.

[Canaletto (Lionel)]

The question may have already been asked, but what is the workday rule?

For example, what is the workday rule?
I work on Saturday morning, so it’s not a workday like any other and since it’s just in the morning, I’m going to create a schedule that will apply on Saturday only.

But if this Saturday is a holiday (in workday:), what will happen? Is workday going to be prior to the ordinary Saturday day?

[neliss]

@Canaletto Did you read the documentation on the workday integration?

workdays list (optional)
List of workdays.
Default:
[mon, tue, wed, thu, fri]

And:

add_holidays list (optional)
Add custom holidays (such as company, personal holidays or vacations). Needs to formatted as > YYYY-MM-DD .

As far as I know, this integration only allows you to define the days of which your workweek consists.
I expect the sensor to change state only once per day (right after midnight). And this is info directly used for recalculating timers in the scheduler-component.

My intention is to provide an alternative to people who don’t have a mon-fri workweek.
And to consider national holidays as part of the weekend (if desired), so you don’t have to remember to manually change the thermostat.

If your workweek has days with irregular hours, you will have to find your own creative solution.

[neliss]

@ribbonofblack

I’m using the “run” script option but have a customisation that has an input_number variable.
…
I hope this makes sense.

Not sure if I can follow tbh.
What do you mean with ‘input_number variable’ (it seems contradictive)?

If your script uses extra variables that you have to provide when calling the service, then a customised action is the only way.
But if your script uses the state of an input_number entity for setting the time, then the run action would be sufficient (since you can use a template in the script to refer to the state of that entity).

I guess both ways would get the same result.
Prettiest way is ofcourse to customise the card and define an action using a numeric action variable, giving you a slider in the scheduler for defining the runtime.

[Canaletto (Lionel)]

@neliss

As far as I know, this integration only allows you to define the days of which your workweek consists.
I expect the sensor to change state only once per day (right after midnight). And this is info directly used for recalculating timers in the scheduler-component.

My intention is to provide an alternative to people who don’t have a mon-fri workweek.
And to consider national holidays as part of the weekend (if desired), so you don’t have to remember to manually change the thermostat.

If your workweek has days with irregular hours, you will have to find your own creative solution.

We didn’t understand each other.

My question is whether a “workday:holiday” is, or can be, a priority on a custom day?

[neliss]

I would like to revise the overview page, since it can become rather messy (I heard it a lot).
My plan so far was to:

• Sort schedules based on which one fires first.
• Reduce the amount of info shown on the list (you can always click on it to see all the data)

So I puzzled a bit with the layout, now it looks like this (rough sketch, and the tasks are fictive):

My first impression is that showing the remaining time is quite practical. Gives a good overview of upcoming events. Would like to introduce it in a next update.

But, adding the column with remaining time basically means there is no space left for the flip switch (at least not on mobile devices).

Perhaps it could be replaced with a clickable icon.
Ideally I would like to combine this with some popup menu (like HA uses) behind this icon, since I want to introduce an extra option to ‘skip’ a schedule for x time / steps. However, it looks like the HA popup menu is not that generic that I can re-use it without issues.

Also its kinda weird to see an item moving all the way to the bottom of the list when you disable it. But this is a normal result, since the remaining time will of course be not applicable (hence infinite)

I’m wondering which kind of info you consider essential, and which details.
I would say for time schemes, its sufficient to only show the upcoming first task (and perhaps mention that there are X more for the day).
But I’m not sure if everyone would agree with this.

I got some ideas from you to group schedules by entity.
I think it is a bad idea. I tried it, it looks more messy than it is now.
I’d say its good to keep an icon on the left for each entry, with the entity name in bold next to it. Gives a good overview.

Would like to get your feedback on these ideas. Shoot!

[tom_l]

I like it but you’re probably not going to be able to please everyone, unless…

Add a (global) boolean option for sort by time, and a boolean option to show the time remaining?

[guims78 (guims)]

Hello,
for me, an important thing is the friendly name option, in order to identify, at first sight, what schedule to modify, for example.
When you defined a time scheme, what would be the remaining time ? the one to the next time slot’s end ?

[ribbonofblack]

I have done both. I’ve got the input_number which allows me to set the time for a one off/manual watering. Then from the card/script I change the value of that input_number when running it via schedule.

I don’t think it’s anything that needs changing from the card. With customisation I’m able to set the slider through the card and everything works well.

[TheBisk]

Hi,
i’am tring to do the same, with no result…can you show your config? pls

Thanks.

[tmchow]

I was a few versions behind and recently updated. Prior to this I had nothing scheduled, as I was figuring out my plan on what to add and migrate from Node Red.

I just tried to add a simple automation for my outside porch light, and keep getting the error that means the Scheduler Component isn’t installed:

Failed to call service scheduler/add. Service not found.

However, I do have it installed and I’ve tried removing it and re-installing with no luck. I’ve also completely removed the scheduler card and scheduler component, rebooted and re-installed both and rebooted. Also get the same error message.

Anyone else have any tips?