Scheduler card/custom component

[hazio]

This is amazing! Hopefully HA integrates this natively, great work!

[pepe59]

I created a translation of cs.json on GitHub. What should I do next to add it to the scheduler.
Create pull request ?

[Xavier_Pous]

Hello help me please !

I try to install twice schudeler component and scheduler card but it’s doesn’t work.

I reinstall HA completely but the result is the same.

When configure the card ans save i have a tous message :

Echec call service scheduler/add. Service not find.

Do you have solution ?

Thanks

[neliss]

@pepe59

I created a translation of cs.json on GitHub. What should I do next to add it to the scheduler.
Create pull request ?

Thanks for making a Czech translation of the card. I will add it in the next release.

@Xavier_Pous

When configure the card ans save i have a tous message :

Echec call service scheduler/add. Service not find.

Did you follow the installation steps?
Also the last one?

[KTibow (Kendell R)]

Are you using a translator? Try a better one:
translate.google.com
Anyway, you need to go to the integrations page of HA under configuration, and add the scheduler.

[Xavier_Pous]

yes I followed the recommendations of the installation under HACS.
I looked in development tools, service and I did not find:
Scheduler/add

[KTibow (Kendell R)]

Restart? Can you take screenshots of every step of installation and post them here?

[Xavier_Pous]

Yes I did it under HACS

[Xavier_Pous]

I am under 0.116.4.
the installation of both components went well under HACS. I have to restart after installation

[tmchow]

@neliss

group entities are a difficult case. Because the actions you can do will depend on the entities that you fill in the group (you can put light but also cover or climate entities in it).
If you would have chosen a light group instead, all would have worked as you want.
If you really want to have support for scheduling group entities, please make a FR on GitHub.

I don’t think I can use a light group because in my case for these lights, I’m using smart switches and you can’t use switch entities in the light domain.

I’ll make a FR on GitHub as it’s the only way this could work if you support it (with caveat like you said of ensuring the group is all consistent with contained entities)

@neliss

Well, a schedule is a switch , so if all switch entities are exposed to Alexa, that’s what you will get…
I guess you could better ask this question to the maintainers of the Alexa integration instead.
I cannot make them magically be filtered out
As far as I know most of these integrations use a include/exclude mechanism for whitelisting entities, so I would assume you could create a list of switches you want to expose.
If I could simplify things by introducing some kind of attribute to the entities to distinguish them, I’d be happy to…

I’ve written to the Habu Casa team in a support ticket outlining the issue and asking for wildcard filtering. We’ll see

[jalsing (Jason)]

@tmchow

I don’t think I can use a light group because in my case for these lights, I’m using smart switches and you can’t use switch entities in the light domain.

Well you can alias the switches to lights in the configuration.yaml, at least that’s what I do with my smart plugs I have lamps attached to…

[tmchow]

@jalsing

Well you can alias the switches to lights in the configuration.yaml, at least that’s what I do with my smart plugs I have lamps attached to…

Tell me more!

[jalsing (Jason)]

Here’s what mine looks like. Actually 2 plugs and two wall switches…

light:
  - platform: switch
    name: TV Lamp
    entity_id: switch.tv
  - platform: switch
    name: Couch Lamp
    entity_id: switch.couch_lamp                               
  - platform: switch
    name: Family Room Ceiling
    entity_id: switch.family_room_ceiling
  - platform: switch
    name: Front Entry
    entity_id: switch.front_entry

[tmchow]

@jalsing

Here’s what mine looks like. Actually 2 plugs and two wall switches…

Copy to clipboard

light:
  - platform: switch
    name: TV Lamp
    entity_id: switch.tv
  - platform: switch
    name: Couch Lamp
    entity_id: switch.couch_lamp                               
  - platform: switch
    name: Family Room Ceiling
    entity_id: switch.family_room_ceiling
  - platform: switch
    name: Front Entry
    entity_id: switch.front_entry

Thanks! Are the corresponding Light entities created now just a 1:1 mirror on the original switch names or is there a way to configure the alias? I didn’t see it in the help docs so assuming no. So your light aliases are:

light.tv
light.couch_lamp
light.family_room_ceiling
light.front_entry

I’ve got my entities like switch.front_door_light, so it’ll annoy me as light.front_door_light due to the repitition in of the word “light”, but switch.front_door won’t make sense so i’ll have to live with it.

[jalsing (Jason)]

I believe it uses whatever you have for "name’, here’s another one I have, this one the light entity is ‘light.mantle_lamp’ even though the switch entity is something different. Hope this helps.

  - platform: switch
    name: Mantle Lamp
    entity_id: switch.miniplug1

[neliss]

I don’t want you to create extra entities in HA for scheduler card.
Would rather proceed with the FR for group entities.
It shouldn’t take that much effort, and would help others as well.

[tmchow]

I got the aliasing to work and using the new light group with your scheduler card. In general I’d agree not to need to create mew entities just for scheduler card but I think there are other benefits here of doing it this way as my guess is many people would want the switch to actually be a light as it makes other integrations simpler. For me, I was juggling switches and lights which made things confusing for me and error prone.

[guims78 (guims)]

Hello, I think I missed something but where is the slider to activate or not the scheduler ?

[joem (Zsolt)]

I’m trying to add my phone sensors to use them as conditions, for example:

sensor.in2023_battery_state
sensor.in2023_battery_level

Unfortunately I can’t get it to show up in my list. Could anyone point me in the right direction?

[neliss]

@guims78

Hello, I think I missed something but where is the slider to activate or not the scheduler ?

Since release v1.7.3 the switches are replaced to show remaining time instead.
Now you can tap+hold an item to disable/enable it.
Last week there was a vote on whether people liked this improvement, most people prefered the old situation.
Thats why v1.8.0 will revert this change.

@joem

I’m trying to add my phone sensors to use them as conditions, for example:

Copy to clipboard

sensor.in2023_battery_state
sensor.in2023_battery_level

Unfortunately I can’t get it to show up in my list. Could anyone point me in the right direction?

You will have to define the states ranges for sensors (the entity does not have any property showing the min/max values for sensors).
Its all written down here.