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 
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:
am_pm setting is dropped.first_weekday setting is dropped.Hope it works fluently for all, let me know if there are troubles!
Group entities
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
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:
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:
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:
And that’s exactly what I did. Looks very discrete, think its a keeper
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.
Whaw !!! Merci pour tout ça 
Great !!!
Can you give an example how to implement display_options ?
Thanks for the job!
Very helpful. It will really simplify the automations I have.
I have a problem. After updating, I will add a scheduler tab and it will not appear. I refresh the page and it is present. I switch the view and come back and the screen is blank again. The default theme and custom is the same. HA 0.117.1 browser chrome
Sure!
This is the standard setting:
display_options:
primary_info: "{entity}: {action}"
secondary_info:
- relative-time
- additional-tasks
icon: action
So you could use it as a starting point, make changes as you wish.
I added some documentation about it.
Well that’s weird! The card should work snappy…
I also don’t have the issue you’re having.
If you could share a specific pattern you do to get this issue (or maybe even make a screen video), i would like to check it out.
I will try to restart Rpi. Then I’ll let you know.
I’m having the same issue. I have two separate scheduler cards, one on separate lovelace “tabs”. If I refresh the page while on tab eg “Climate” my climate scheduler card shows up. But if I select the “Automations” tab, my other scheduler card is not there. I can refresh, and it will show up. But then, clicking back to “Climate” and the scheduler card there is gone.
I had just updated your card and restarted HA (did not check this functionality however) then updated HA to .117.1 and noticed this behaviour.
I tried restarting and it didn’t help. I also have 2 cards, 1 PC monitor and a second tablet on the wall. I am convinced that this was done by updating to v 0.117.1
I went back to HA version 0.16.4 and it’s the same.
If we don’t refreash the page and let it do so, the memory consumption of the page continues to increase (10 G) until it crashes.
Same here. Though I thought maybe not at first as I didn’t see any increase but after a short while I look back and it’s at 1.5G+
Same issue. After updating, unable to create new scheduler, just the button ‘edit’ appears at the bottom of a newly created ‘scheduler card’.
However the new UI (with time presetting, selection of groups, switches, lights, climates, …) is available.
I returned the scheduler to version 1.8.4 and everything is fine.
I don’t experience any of these problems.
Obviously, else I wouldn’t have made a release.
People who have issues with the card are invited to create an issue in GitHub (as usual).
Hope they can provide enough details such that I can reproduce the problem, else I can only guess.
If version 1.8.4 works better for you, that’s ok with me 
The reproduction of the problem is simple :
I think there is a link between the fact that it doesn’t recharge and this memory consumption. But I am not a developer to give more indications…
I’m also not a developer, so I can provide screenshots or the same information. My problem is identical. Just a layman’s view, there must be a difference between a new and an old version. The old version does not show this problem.
Hello
I have 7 climates. Each of them can be either in mode ‘confort’ which means 20°C all the time or they can be controlled with the scheduler with ‘confort’ or ‘eco’ temperature during specific timeslot.
I need to define 7 daily schedulers.
I also need
Therefore, I want to use the script capability in the scheduler.
In the example you provide, temperature is sent as a field (and I assume that temperature means the temperature set as a target for the climate and not the current_temperature).
but how to send additional fields (such as climate name) to the script if I want to avoid to write seven different scripts.
Can you give us more information on the ‘script option’. I mean the option to schedule scripts with fields?
I think that’s the best option to achieve what I want.
If you have other ideas, let me know
Thanks
