Scheduler card/custom component

Esmax555 · December 5, 2025, 8:15am

What is as STR ?

hi knuti1960
Can you show me your script ?

Thx a lot

knuti1960 · December 5, 2025, 9:48am

Sure. It’s nothing special, just set all the thermostats to ECO and deactivate the schedules.

sequence:
  - action: switch.turn_off
    metadata: {}
    data: {}
    target:
      entity_id:
        - switch.schedule_heizung_buro_vtherm_mo_do
        - switch.schedule_heizung_buro_vtherm_freitags
        - switch.schedule_heizung_buro_vtherm_samstags
        - switch.schedule_heizung_buro_vtherm_sonntags
        - switch.schedule_heizung_kuche_mo_do
        - switch.schedule_heizung_kuche_vtherm_freitags
        - switch.schedule_heizung_kuche_vtherm_samstags
        - switch.schedule_heizung_kuche_vtherm_sonntags
        - switch.schedule_heizung_wozi_re_vtherm_samstags
        - switch.schedule_heizung_wozi_re_vtherm_sonntags
        - switch.schedule_heizung_wozi_re_vtherm_mo_do
        - switch.schedule_heizung_wozi_re_vtherm_freitags
        - switch.schedule_heizung_bad_vtherm_mo_fr
        - switch.schedule_64a7d4
        - switch.schedule_heizung_kizi_vtherm_mo_fr
        - switch.schedule_heizung_kizi_sa_so
        - switch.schedule_heizung_wozi_li_vtherm_samstags
        - switch.schedule_heizung_wozi_li_vtherm_sonntags
        - switch.schedule_heizung_wozi_li_vtherm_mo_do
        - switch.schedule_heizung_wozi_li_vtherm_freitags
        - switch.schedule_heizung_wozi_u_li_vt_mo_do
        - switch.schedule_heizung_wozi_u_re_vt_mo_do
        - switch.schedule_heizung_wozi_u_li_vt_freitags
        - switch.schedule_heizung_wozi_u_re_vt_freitags
        - switch.schedule_heizung_wozi_u_li_samstags
        - switch.schedule_heizung_wozi_u_re_vt_samstags
        - switch.schedule_heizung_wozi_u_li_vt_sonntags
        - switch.schedule_heizung_wozi_u_re_vt_sonntags
        - switch.schedule_kiinderbesuch_am_we
        - switch.schedule_heizung_kizi_besuch_montags
        - switch.schedule_heizung_kizi_vt_besuch_dienstags
        - switch.schedule_heizung_kizi_nur_heute_an_fur_home_office
  - device_id: 858ee48c9ce59383e745fe3a212bbcd1
    domain: climate
    entity_id: ddaa33a1f1567cb8ec0ae73c3fd413ab
    type: set_preset_mode
    preset_mode: eco
  - device_id: 81037b1d39fa46d1ef107c9bf2a36955
    domain: climate
    entity_id: 14de703957f816195d716d4b8bfebb68
    type: set_preset_mode
    preset_mode: eco
  - device_id: cf092651db00f206711048a9e7c11c77
    domain: climate
    entity_id: 0cae547104b70b30255c01120dda1146
    type: set_preset_mode
    preset_mode: eco
  - device_id: 9e4878a6468d788c673ef2cb3865870d
    domain: climate
    entity_id: 91d9c376ab468601e312830a7d0df4b4
    type: set_preset_mode
    preset_mode: eco
  - device_id: e05cf20682703e948574900ca621d407
    domain: climate
    entity_id: ae4f2045a821801ecee17b8cc0b0fc15
    type: set_preset_mode
    preset_mode: eco
  - device_id: c0ef800594f9bc9637ed2fc54d500375
    domain: climate
    entity_id: 5b4e47e13e01043325a751a38044b24e
    type: set_preset_mode
    preset_mode: eco
  - device_id: f78f355dbe2468202d554738973cb681
    domain: climate
    entity_id: 48082854638193c24940b28ec5cf74ec
    type: set_preset_mode
    preset_mode: eco
  - device_id: 0b97f42a76772b11c32d552119e0e1c8
    domain: climate
    entity_id: fb2c3d167c4fe97c31f0c030827443cd
    type: set_preset_mode
    preset_mode: eco
alias: ALLE Heizungen ECO (DAUERHAFT)
description: Alle Vtherms dauerhaft auf ECO, Zeitpläne werden deaktiviert
icon: mdi:radiator-off

I have a few other scripts of this type for all kinds of configurations that are not covered by schedules. For example, “Turn on all heaters in the living room for the next 2 hours” or something like that.
In retrospect, I find all of this quite unnecessary, because we almost always make the desired settings via voice command. The temperature specified by voice command (or manually) automatically overrides the scheduler setting, at least until the next scheduled change (in the scheduler).
However, there are a few situations where disabling the scheduler is essential, and that’s where the scripts come in handy.

tykeal · December 5, 2025, 12:35pm

STR == Short Term Rental (think Airbnb or VRBO)

MrM · December 10, 2025, 8:42am

A quick note for anyone whose scheduler card looks odd and won’t open settings, for example: check whether the Scheduler Card is still selected in HACS. For me it suddenly wasn’t selected anymore and stuck at version 3.x. A simple re-activation (download) solved it, and after the update all existing schedules continue to work normally.

Greetings

brjhaverkamp · January 2, 2026, 4:08pm

Hi all,

I started using the scheduler card a few days ago. After my first confusion due to the latest version looking very different from the documentation, I am slowly getting the hang of it.
Although I’m still confused by the usage paradigm: First I have to chose a time/timeslot, then an action and then the device. In my view the opposite would be more intuitive: First choose the device you want to control. Then the action I want it to do and then the time I want it to do that.
That would at least in my opinion be more in line with how you normally program devices like the central heating.
And I have to discover how to create multiple schedules for Home/Away/Work.

One thing I did notice, and I am not sure if it’s a bug is if I change an already created schedule to a time scheme by enabling the end time, the end time stays greyed out. i had to delete the schedule and recreate it as a time scheme to get it working.

Also I’m not sure how to deal with a combination of actions. I want to switch on my AC and set the temperature to 21’C at 6:00 in the morning.
Do I need to different schedules for this?

Oh, and is there a way to change the schedule gui to 24 hour mode? Instead of AM/PM?

Regards, and thanks for the great work!

Bert

davidtja · January 3, 2026, 10:01am

FWIW this is an outstanding module and should be a part of HA core, however I do agree its tough to get your head around.
For example, why do the below show as excluded. Though it seems to work fine.

bob.t · January 3, 2026, 11:26am

Check the TAG(s) assigned to the card, and then the TAG(s) assigned to the individual schedules.

Tags are filters, allowing one to have multiple schedule Cards that each show a different/filtered set of schedules.

Scheduler/General card “filtered”

Scheduler/General card “unfiltered”

davidtja · January 4, 2026, 10:33am

Thanks for that could’nt see anything obvious but recreated and resolved the problem. Appreciate help.

spanzetta · January 4, 2026, 3:39pm

I am struggling to create a schedule using YAML code (and not UI) because the schedule I need is quite long… see below the time slots I need to manage…

For each of them I need to use a different action (the same 2 that alternates every 2 rows)

Is there a way to create using YAML code ? If yes… how?

The 2 actions to alternate (for the entity climate.casa) are the following:

Action 1

service: climate.set_temperature
data:
temperature: 21

Action 2

service: climate.turn_off

Time slots to manage:

00:00:00 - 00:45:00 → action 1
00:45:00 - 01:00:00 → action 2
01:00:00 - 01:45:00 → action 1
01:45:00 - 02:00:00 → action 2
02:00:00 - 02:45:00 → …
02:45:00 - 03:00:00
03:00:00 - 03:45:00
03:45:00 - 04:00:00
04:00:00 - 04:45:00
04:45:00 - 05:00:00
05:00:00 - 05:45:00
05:45:00 - 06:00:00
06:00:00 - 06:45:00
06:45:00 - 07:00:00
07:00:00 - 07:45:00
07:45:00 - 08:00:00
08:00:00 - 08:45:00
08:45:00 - 09:00:00
09:00:00 - 09:45:00
09:45:00 - 10:00:00
10:00:00 - 10:45:00
10:45:00 - 11:00:00
11:00:00 - 11:45:00
11:45:00 - 12:00:00
12:00:00 - 12:45:00
12:45:00 - 13:00:00
13:00:00 - 13:45:00
13:45:00 - 14:00:00
14:00:00 - 14:45:00
14:45:00 - 15:00:00
15:00:00 - 15:45:00
15:45:00 - 16:00:00
16:00:00 - 16:45:00
16:45:00 - 17:00:00
17:00:00 - 17:45:00
17:45:00 - 18:00:00
18:00:00 - 18:45:00
18:45:00 - 19:00:00
19:00:00 - 19:45:00
19:45:00 - 20:00:00
20:00:00 - 20:45:00
20:45:00 - 21:00:00
21:00:00 - 21:45:00
21:45:00 - 22:00:00
22:00:00 - 22:45:00
22:45:00 - 23:00:00
23:00:00 - 23:45:00

I already searched into documentation and tried many times (also using ChatGPT which wasn’t usefull at all) but without success…

I will appreciate if someone could help

Thanks in advance

McJameson · January 6, 2026, 8:44am

Instead of using the scheduler card you could use two automations, which will be triggered at the full hour and at 45 minutes of an hour.

spanzetta · January 6, 2026, 1:21pm

Thanks for the reply… You are right … but I like the Scheduler because you can enable/disable it with a single click…

I wonder if it’s possible to create schedule trough YAML instead of trough GUI (which is fine for simple schedule… not appropriate for complex schedule)

McJameson · January 6, 2026, 1:27pm

You can enable/disable an automation with one click as well by putting the respective entity in your card. I am using this to turn the automations for my outdoor lights on/off.

Don’t understand me wrong, I very much like and use the scheduler in various ways. But I also faced a similar problem as you before and decided it was too much work for too little benefit.
I tried manipulating the config files before, but they were blocked by the system. Thus, my changes wouldn’t persist.

As somebody once said:
There is the right tool for everything, but no tool is right for everything!

spanzetta · January 6, 2026, 3:04pm

right… I will do that way… once I know it’s complicate (if not impossible) to do that trough scheduler (as said I already tried hard to do that way… without success) I will do with automation…
I agree with the saying you mentioned…
Thanks a lot

guensen0 · January 7, 2026, 5:04pm

Hi, is it possible to display customized variables in the list like {action} etc.? like its done for standard procedures like setting the temperature of an thermostat…

jost.wolf · January 8, 2026, 8:26pm

Hi, I’ve set up scheduler card with scheduler component.

But since the HA core update to 2026.1, I can’t pick any heating type as action anymore. It’s simply not in the list.

The old heating schedules still work, but I can’t make new ones.

knuti1960 · January 8, 2026, 9:18pm

Have you installed the latest versions of both (card + component)? Everything works as usual here, even with HA 2026.1.
Or assigning the wrong tags?

drsnyder · January 10, 2026, 1:41pm

Hi, today I got the same Problem as jost.wolf. After Updating the HA Core, i can´t pick any entities as action any more. The old schedules work without a Problem.

Core 2026.1.0
scheduler Card 4.0.10
scheduler component 3.3.8

jost.wolf · January 10, 2026, 5:43pm

I didn’t add any tags.

Yesterday, I’ve downloaded and installed both components again. No changes.

Same versions as drsnyder

knuti1960 · January 10, 2026, 6:21pm

I just tried it again, and I have to revise my statement above; I probably didn’t test it properly. For example, when I want to select a preset for the heating (the selection field is initially displayed!), the selection field disappears as soon as I click on it (I didn’t take this last step in the last test.).
I think we’ll have to wait for the developer; something probably needs to be adjusted there.

jost.wolf · January 10, 2026, 10:27pm

There seems to be a hot-fix until the developer comes around with an update. Can not select any entity · Issue #1061 · nielsfaber/scheduler-card · GitHub