Scheduler card/custom component

[neliss]

Yes sir!
I think for person entities you only have to add them to the include: list, and they should show up.
If not, then check here.
Note that this is currently a YAML only feature. Not available in the UI editor.

[glorifiedg]

Did it with ease! I was adding person.* to costumize: but not on include. Thank you!

[neliss]

I will make something that will automatically include stuff you have in customize already (why would you customize stuff that is not in the card )

Lots of things to do

[Canaletto (Lionel)]

Idea:
Currently I log all my calender actions (Google) in Slack. It would be interesting to propose a login option based on a notify: dedicated…

[KTibow (Kendell R)]

Did you post in the wrong thread? I don’t quite understand what you’re saying…

[Canaletto (Lionel)]

Ironic
What I mean is that currently in my automations I create a log that I send as a notification (Slack currently) and that a notification option at the start of a schedule could be an interesting option.

[neliss]

@Canaletto

What I mean is that currently in my automations I create a log that I send as a notification (Slack currently) and that a notification option at the start of a schedule could be an interesting option.

Seems a bit specific functionality.
It is not in-scope for this component.

There is a plan for adding a textfield-option (instead of slider) at some point.
Maybe it could be used for scheduling a task for the notify platform, with a message you can enter.
BUT: a problem is that notify platform does not use entities. This card is limited to tasks related to entities.
Maybe you it could be done through a script which accepts message as variable and calls the notify function.

However, the message will be a ‘static’ text. It will not support templates or anything.
If you want to print details (like entity attributes), better keep things as you have them now.

[Canaletto (Lionel)]

@neliss

Seems a bit specific functionality.
It is not in-scope for this component.

There is a plan for adding a textfield-option (instead of slider) at some point.
Maybe it could be used for scheduling a task for the notify platform, with a message you can enter.
BUT: a problem is that notify platform does not use entities. This card is limited to tasks related to entities.
Maybe you it could be done through a script which accepts message as variable and calls the notify function.

However, the message will be a ‘static’ text. It will not support templates or anything.
If you want to print details (like entity attributes), better keep things as you have them now.

Juste an idea, not a request

[neliss]

@Canaletto

Juste an idea, not a request

Well, since I’m the maintainer of this component, it’s more or less the same thing right?
But feel free to make a PR if you want to make this functionality
For me the priorities are bit different as you can imagine…

[Canaletto (Lionel)]

@neliss

Well, since I’m the maintainer of this component, it’s more or less the same thing right?
But feel free to make a PR if you want to make this functionality
For me the priorities are bit different as you can imagine…

My English is bad…

My idea was just to send out a notification when a scheduled action occurs. But I should be able to do it differently, for example if a swiche goes from “off” to “on” I create a notification…

[dyfcom (Tetra)]

Updated today the card and component. Great job with the Scheduler Scheme!

I want to switch my current climate scheduler from automations to this, but under condition I can only select switches/lights, it would be nice when there is group of binary_sensors for a window contact as example!

The design is great too

[tom_l]

@dyfcom

I want to switch my current climate scheduler from automations to this, but under condition I can only select switches/lights, it would be nice when there is group of binary_sensors for a window contact as example!

Not what this is for. This is not an alternate automation engine.

Keep the conditions in a script or automation. Enable the script or automation with the scheduler.

[neliss]

@dyfcom

I want to switch my current climate scheduler from automations to this, but under condition I can only select switches/lights, it would be nice when there is group of binary_sensors for a window contact as example!

Just add binary_sensor (or specific entity_id’s ) in the include: section (YAML mode, not UI mode).
It should automatically create a group which is only visible under conditions (since binary_sensors have no services).
Be aware that conditions are only used to control whether an action should be blocked or not.
If you are using timeslots, this is only at the start of the timeslot (so closing a window in the middle of a timeslot, will not re-trigger the action for the heater to go back on).
Not yet, at least

@tom_l

Not what this is for. This is not an alternate automation engine.

Well… Starting to become one
Wasn’t really my plan though.

[tom_l]

Yeah, honestly, I’ve held off installing this until the dust settles and the config solidifies a bit (nothing to do with it being a mad time of year work-wise, no not at all). But… it’s already becoming far more than I needed and I’m beginning to look at the other two options again, just for simplicity.

[Foxxy (Reps)]

Yes, that was discussed some weeks ago (around posts 595+)- and I IMO still need a SCHEDULER component not another AUTOMATION / SCRIPT engine in HA
Best, JR

[neliss]

Don’t worry, I’m well aware of how things are escalating.
There are not really any extra features left to be added. This is it
The next updates are focused on cutting down code, simplifying GUI, making the user experience more pleasant.

Still puzzling a bit about what to do with the ‘discovered schedules’ vs multiple cards issue.
It’s kind of a unique situation, with the card auto-generating entities that you may later ‘get lost in HA’ due to changes in your card config.
That, and the fact that the schedules refer to other entities + services, which might get removed as well.
Any good idea is welcome

[tom_l]

Disable them and have something like the “show disabled entities” filter from the configuration / entities menu perhaps?

[dyfcom (Tetra)]

@tom_l

Keep the conditions in a script or automation. Enable the script or automation with the scheduler.

That is what I need. When the window is open, the heater turn off, when the window is closed, it’s going back to the temperature. And this is working with the scheduler like charm.

Only need 2 Automations (Window Open/Close) instead of 9 …for one room

[neliss]

Release v1.9.0

I have listened to you guys
I collected some feature requests and made a big update for them.
Let me summarize the changes.

Localization
The localization of the card has been completely redone.
All texts in the card now support translations. Well… except for the UI editor.
A lot of translations have been re-used from HA, to reduce the mainteannce (and size!) of the localization files.
The remainder has been restructurized for making things more maintainable.

A big request to those who have helped translating:
Could you please take a look at the new localization files, and help me with the migration?

Furthermore, the card should now detect automatically:

• The time format in your country (24 hours vs 12 hours format). The am_pm setting is dropped.
• The first day of the week. The first_weekday setting is dropped.
• The names of the weekdays.

Hope it works fluently for all, let me know if there are troubles!

Group entities

@Isablend

Is it possible to define groups of entities you want to schedule the same activity for? For example closing a set of blinds or putting on a set of lights?

@tmchow

Is it possible to use this with a group of switches ? I’ve got 3 smart switches controlling exterior lights that I want on the same schedule. I’ve defined a group for them, but they don’t show up as options in the scheduler card.

It is now finally possible to create schedules for group entities.
And by group, I mean group (not the ones that categorize the entities).
It was a bit of a puzzle, because you can place virtually any mix of entities in a group, and the group will allow you to call almost every service for them.

The card will check which entities are contained by the group, see if they have any actions in common, and make those available for you.

It wyou try anything fancy (like combining climate + cover + light) entities in a group, there’s a good change that the card doesn’t know what you want to do with them.
Ofcourse you can customize your own action, but don’t expect that set_temperature will make your lamps become more orange (use at your own risk).

As with every new addition: suggestions are very welcome!

Display options

@Canaletto

The friendly name is also what can tell us what a schedule contains. Why not make it appear on the card?

@ASNNetworks

The schedule card now shows the icon of the action instead of the entity.
…
I liked having the icon of the entity

I heard you In HA everything should be possible. That’s what makes HA so awesome.
Since it will be very hard to combine everyone’s preferences, I decided to make things configurable.
Check out the new display options configuration.
I hope it will give everyone the possibility to change things to their liking. Let me know if you miss anything.

Improved customization
With special thanks to @Motti_Bazar for his patience in helping me improving this.

First of all, the hiding of actions:

@Motti_Bazar

Without using the “standard_configuration: false”, I get all possible actions listed but I only want part of them (would like to remove “set preset” and “turn off”) displayed for selection.

There is now the exclude_actions property, which may help you to hide unwanted actions from your the card. It was already introduced in the previous release, but it was still buggy. I think it works better now
You can simply provide a list of names of actions (as they are displayed, so e.g.: ‘heat’) to make them disappear.

Then the more specific customizations:

@Motti_Bazar

When sliding the dot, the steps are done in 0.5 degree. I tried to change this using “customize” to be 1 degree steps with no success.

There were definitely some quirks in the card here.
In v1.8.0 I mixed quite some stuff up internally. And now I mixed stuff up again. But hopefully for the better

The idea is that the standard config and your customization will be merged, so you only have to provide the changes you want to do on top of the standard configuration.
So in case you want to change the timestep for the set_temperature action, you can do this:

customize:
  climate:
    actions:
      - service: set_temperature
        variable:
          field: temperature
          step: 1

While the other properties (name, icon, min / max / unit etc.) will be kept as they are.

Other changes
In v1.80, suddenly everyone was getting big yellow boxes with warnings of schedules that were not included in their config.

I got a nice tip from @tom_l:

@tom_l

@neliss

Still puzzling a bit about what to do with the ‘discovered schedules’ vs multiple cards issue.
It’s kind of a unique situation, with the card auto-generating entities that you may later ‘get lost in HA’ due to changes in your card config.
That, and the fact that the schedules refer to other entities + services, which might get removed as well.
Any good idea is welcome

Disable them and have something like the “show disabled entities” filter from the configuration / entities menu perhaps?

And that’s exactly what I did. Looks very discrete, think its a keeper

@clau-bucur

Is the “remaining time” supposed to be dynamic or only should update on page refresh? Because currently it doesn’t count down. It only changes if I refresh the page.

Done!

Well that wraps it up pretty good.
Maybe I missed some more changes, but I guess you will find out yourself!

PS: Good chance that there will be (as always) some new issues in the card (also the 0.117 HA update messed some things up). Let me know, I will try to fix them in the next couple of days.

[Canaletto (Lionel)]

Whaw !!! Merci pour tout ça