Scheduler card/custom component

Share your Projects! Dashboards & Frontend
363

Usually yes, but it is not necessary the case.
If you want to only schedule 1 specific entity (say your living room thermostat), you could make all domains false and only add entities configuration for the thermostat.

The discovery mechanism is just there to make sure you don’t have ‘lost’ schedules running in the background. I wrote a short story about it.

364

In this case SWITCHES should not appear ?

image
image1082×409 29.6 KB

365

Standard configuration enables discovery of fans, switches, etc. Disable it.

366

If i disable the related schedulles dont apear… and dont have actions…

image
image1092×849 53.8 KB

367

In that case, keep it on, and use:

domains:
  switch: false
  climate: insert your stuff here
368

That looks like a bug.
But how were you able to add a schedule if the actions list is empty?

369

Yes I think of a bug…
The other schedules have been added with another card.

My goal is to have one card per thermostat.

370 
discover_existing: false
domains:
  light: false
  switch: false
  fan: false
  cover: false
  climate: 
    include:
      - climate.my_thermostat

Put this in both cards (of course with different thermostat id) and it should work…

371

image
image1028×388 27.9 KB

372

Ah sorry, I forgot a dash. I updated it in my code.
But all of this is documented you know…
No need to puzzle with it that much :slightly_smiling_face:

373

Yes I have corrected in the meantime and it’s ok!

374

But I still have two Kitchen thermostats that appear in ALL, single card with

type: 'custom:scheduler-card'
discover_existing: true
title: ALL

And not in Thermostat Cuisine

type: 'custom:scheduler-card'
discover_existing: false
standard_configuration: true
title: Thermostat Cuisine
time_step: 1
domains:
  light: false
  switch: false
  fan: false
  cover: false
  climate:
    include:
      - climate.thermostat_cuisine

image
image1156×988 60.7 KB

376

Try just

type: 'custom:scheduler-card'
discover_existing: false
standard_configuration: true
title: Thermostat Cuisine
time_step: 1
domains:
  light: false
  switch: false
  fan: false
  cover: false
  climate:
377

No, because I want juste one climate thermostat on this card, not all…

378

Well make sure if you customize it, that you add back the default config.

379

I think that the two planning that appear in excess are done before I do the update in 1.5. I will remove them.

380

I still try to start every time with an empty card but I can’t get it done… Is there a solution?

381

What do you mean?

1 Like
382

I would like to have multiple scheduler cards in various panels. Now i still have one which gets longer and longer…

With the help of your discussion in the thread I solved it (as it seems for now) I can make separate cards for various switches. Just the way I want it! Thanks!!

383

Thanks all for mentioning the bugs that came with the release (and sorry for these bugs!)
There is a new version available that should fix all of them.

I have a question to all of you regarding the standard configuration.
I noticed that some of you are struggling with adding and hiding entities, i would like to find a solution to improve this.

Please let me know preference:

  • It’s fine for me that the climate, light, cover, switch and fan entities are there by default. These are all I need. Keep it as it is.
  • Make all supported entities visible in the card by default, I will hide what I don’t want to see.
  • I prefer to start with an empty list. I will choose which entities show up.
  • I don’t like messing with YAML. Just make a UI editor where I can pick which entities are visible.
  • I have another idea. I will tell you below.

0 voters

Thanks!

1 Like