Scheduler card/custom component

[b4ker]

Thanks for your fast reply. Sorry, but what do you mean with “hard refresh”?

Basically only with lights it’s working perfect:

As soon I add switch to domains, it stops to display anything, so if I click on “ADD ITEM” it’s not showing even the lights:

[KTibow (Kendell R)]

Try doing Ctrl+Shift+R, then Ctrl+R. (Ctrl is command on mac)

[b4ker]

Thanks for the advise, but unfortunately no luck…

[claudegel (Claude Gelinas)]

I just sent a PR for french translation

[claudegel (Claude Gelinas)]

Yes it could be very usefull to have a month setting or seasonnal setting.

• during winter turn_on outside christmass light at 20 minutes after sunset
• in summer reduce cooling temperature at night
• in winter reduce heating temperature at night
• etc

For now I don’t know if it is possible to stop a specific schedule for winter and start it back next spring for example.

[neliss]

@MrLemur

It’s quite strange, as I don’t have any switch groups and not added any custom names for domains.

Adding in a console log for userconfig when it is constructed shows that name is undefined. Where is this taken from?

Release v1.2.3 fixes this.
Thanks for reporting

@b4ker

Thanks for your really great work, I was already looking for something like this! For domains: light it is working like a charm, but as soon I add switch to domains, then it’s not showing any group/entity anymore, basically if I click on “ADD ITEM” nothing happens… Any advise? Thanks again!

Release v1.2.3 should fix this for you.
There was a typo specific to switch entities, resulting in catastrophic epic fail of the card

@claudegel

I just sent a PR for french translation

Thanks a lot! Its added to release v1.2.3.

[neliss]

@Yammers

Sorry i mean like if i wanted to something to come on at certain times of the month or year like holiday lights etc over christmas

I like the idea, but this a delicate subject.
One of the main goals i had in mind creating the card, is that it should have very little whistles and bells, so you can make changes fast and the GUI remains mobile friendly.

@claudegel

Yes it could be very usefull to have a month setting or seasonnal setting.

• during winter turn_on outside christmass light at 20 minutes after sunset
  …
  For now I don’t know if it is possible to stop a specific schedule for winter and start it back next spring for example.

Since each schedule is a switch in HA, you can already make more advanced automations on top to determine which schedules should be enabled in which period.
The other way around, you can also create schedules that trigger automation or script entities which will have more advanced conditions.

@claudegel

• in summer reduce cooling temperature at night
• in winter reduce heating temperature at night
• etc

For thermostats specifically i am working on an easier interface to change temperatures.
It will work with time blocks that you can drag to define the time span, and for each block you will be able to define the temperature.
It will roughly look like this:

Ofcourse it is still a big work-in-progress, so it will require some patience from your side.
I am hoping that eventually the GUI becomes so nifty that making adjustments becomes a breeze.
Let’s get back to this topic in a month or so

[b4ker]

Thanks for the update, but unfortunately the issue is still there, I’ve tried to remove the whole component and reinstall it but the behavior is still the same. Without switch domain it is working great.

[neliss]

Okay strange.
Reinstalling the component will not solve anything.
Can you check the console log in your browser? There should be a message that scheduler card is at v1.2.3.
If so, then we need to dive deeper

[b4ker]

OK, it was my fault, it was required to clear my browser cache, now its working as expected! Great Job, much appreciated!

[MrLemur]

Unfortunately it’s gone back to the original problem with v1.2.3. Lights and switches button shows, but clicking Lights does not show any entities.

Same error in console:

scheduler-card.js:186 Uncaught (in promise) TypeError: Cannot read property 'replace' of undefined
    at ds (scheduler-card.js:186)
    at scheduler-card.js:468
    at Array.map (<anonymous>)
    at HTMLElement.getEntities (scheduler-card.js:465)
    at HTMLElement.render (scheduler-card.js:408)
    at HTMLElement.update (scheduler-card.js:186)
    at HTMLElement.performUpdate (scheduler-card.js:148)
    at HTMLElement._enqueueUpdate (scheduler-card.js:148)

Again I added a conditional, and most of the light entities showed up, but some had no label. These are in the format light.83afdfe0_898eadff - these are entities from browser_mod component. As thse are auto-generated, they might not have a unique entity ID. Can it be changed to use the name of the device instead?

[KTibow (Kendell R)]

Do they have a friendly name?

[MrLemur]

Friendly name is not added as these are automatic entities.

[BrianHanifin (Brian)]

@neliss

If you want to include only specific entities of a type entities: configuration is the way to go.
Even if all of these need the same actions, you will have to define them one by one.
Perhaps there is room for improvement here

Oh, so we need a default: section to assign default actions to all entities of a domain. Which can of course be overridden in the entities: section.

[claudegel (Claude Gelinas)]

How do we select the language now that there is couple .json language file. Does it pisk the config from HA ?

[neliss]

EN, NL, FR, DE languages are in place.
They should indeed be automatically selected based on the selected language in HA, not by YAML config.
If it doesn’t work for you perhaps your country letters should be mapped to appropriate language.
I’m not sure, HA documentation on this is not very clear.
Let me know if there are problems

[MrLemur]

Did you have any luck with the lights not showing? Is it possible to check for an undefined name, and use the entity name instead?

[neliss]

Yes, I am restructurizing the code that processes the configuration quite a bit.
Empty labels will be a thing of the past. Indeed the entity_id will be used as a fallback.

[MrLemur]

Ah OK thanks! I submitted a PR for this, but I’m not sure what edge cases there might be.

[neliss]

Could you give v1.2.4 a try?
It should improve things drastically.