Scheduler card/custom component

[neliss]

@tmchow

I thought I had no issue with beta but realized I was wrong. I was seeing old schedules that I wasn’t able to delete. Each time I hit delete, it would still show. I then restarted, but got into a weird state where there’s missing schedules now it seems and odd spacing in the card and nothing showing when I tap on the excluded items:

The empty spaces in the card are concerning, they suggests you have some schedules which were not migrated correctly (they got corrupted or something), and therefore the card cannot read/display the properties.
It would be best to remove them completely.
If you keep having problems, please create an issue for it in GitHub.

[maxgiordan (max)]

You solved with the latest updates? For me nothing … I keep having the same problem … no groups are set up and, therefore, I cannot proceed …

[OverZealous (Phil DeJarnett)]

Sorry if this has been answered already, but I can’t seem to find it. I want to add the generated switch.schedule_uvwxyz to an entities card, so that it shows up with a simple toggle to enable or disable the schedule. However, it always shows up just showing the state, and says waiting (or whatever the current state of the schedule is).

Is there an easy way to add the schedule toggle into an entities card? I know when I click on the entity, it shows a toggle in the dialog, so it seems like this should be easy.

[neliss]

Try updating to latest-greatest.
I took care of this…

[neliss]

@maxgiordan

You solved with the latest updates? For me nothing … I keep having the same problem … no groups are set up and, therefore, I cannot proceed …

You should add some entities for which you want to create schedules. Please read the documentation.
If the card does not allow you to add entities (in editor mode), then open an issue for it on GitHub for follow-up.

[OverZealous (Phil DeJarnett)]

Awesomesauce! It worked great, and the update seemed to go smoothly for me. Thanks so much for this integration & component. It really should get adopted as a core feature of HomeAssistant.

[tmchow]

I have updated to latest component, card and deleted the integration and re-added it back.

I then restarted HA.

Went to go add a new schedule and when I hit “save”, nothing happened. I tried it again. Same issue.

In the dev console of chrome, I see this:

Looking at the entities, i see 2 of them created:

Card itself is blank though:

I then removed everything (Integration, Component and Card). Restarted and installed the Component then rebooted. Then added the integration and rebooted. Then added the card and reloaded lovelace.

Tried to add another schedule and same thing – wouldn’t save. But the entity is created:

[neliss]

You haven’t been lucky with this integration, have you.
Anyway, the red error text you shared, I have seen only once. It happened when I created a schedule right after installing the integration (so without restarting HA in between).
It suggests that the card is not able to read stuff from the component.
Could you check the HA log for clues and maybe check the states+attributes of the schedule entities (if state is unknown, something has crashed)?

[tmchow]

@neliss

Could you check the HA log for clues and maybe check the states+attributes of the schedule entities (if state is unknown, something has crashed)?

Looking at the entity that was created, the state is unknown:

I just tried creating another schedule and saw this in the log which confirms success:

2020-12-22 16:19:35 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new switch.scheduler entity: switch.schedule_outside_lights_turn_off

I don’t see anything else in the logs about this, so does this just mean some issue with the card not being able to read from the component as you mentioned?

[Canaletto (Lionel)]

@neliss I installed the new 3.0 and 2.0 component on the last old version (without going through the beta).

I restarted HA twice.

And from there : HACS is disabled despite several restarts.

Finally I restarted the VM and everything went back to normal and I was able to install the v2.0 of the Card. The old schedules were recovered, but I only had 3 of them. I have another installation where I have 15 schedules, we’ll see…

So I say: Bravo ! And thank you again for your patience with us…

PS : don’t forget my idea to have for each timeslot a start action and an end action…

[Bart1992]

Hi,

I’m having some issues with the ‘visual-editor’ not showing( see attachment ). Off course I can configure the lovelace card using ‘code-editor’ however i like the visual editor more :)!

I’ve uninstalled the lovelace card, restarted hass, cleared my browser cache, and installed the lovelace card again. But nothing seem to help? Anyone know why it dissapeared?

[neliss]

I’m pretty sure I messed something up
Is there any error in the browser console log?
See here for instructions on how to see it.

[Bart1992]

Hi neliss,

Thanks for your responce, i’m getting the following error message in the console :

scheduler-card.js:287 Uncaught (in promise) TypeError: Cannot read property 'filter' of undefined
    at Bi (scheduler-card.js:287)
    at Zi (scheduler-card.js:287)
    at Ki (scheduler-card.js:287)
    at scheduler-card.js:1437
    at Array.filter (<anonymous>)
    at HTMLElement.getDomainSwitches (scheduler-card.js:1437)
    at HTMLElement.render (scheduler-card.js:1435)
    at HTMLElement.update (scheduler-card.js:186)
    at HTMLElement.performUpdate (scheduler-card.js:148)
    at HTMLElement._enqueueUpdate (scheduler-card.js:148)
Bi @ scheduler-card.js:287
Zi @ scheduler-card.js:287
Ki @ scheduler-card.js:287
(anonymous) @ scheduler-card.js:1437
getDomainSwitches @ scheduler-card.js:1437
render @ scheduler-card.js:1435
update @ scheduler-card.js:186
performUpdate @ scheduler-card.js:148
_enqueueUpdate @ scheduler-card.js:148
async function (async)
_enqueueUpdate @ scheduler-card.js:148
requestUpdateInternal @ scheduler-card.js:148
set @ scheduler-card.js:148
value @ chunk.1ea6ef6c0d2b8e9fc07f.js:981
performUpdate @ app.e45b0549.js:10297
_enqueueUpdate @ app.e45b0549.js:10297
async function (async)
_enqueueUpdate @ app.e45b0549.js:10297
requestUpdateInternal @ app.e45b0549.js:10297
set @ app.e45b0549.js:10297
commit @ app.e45b0549.js:10297
commit @ app.e45b0549.js:10297
update @ app.e45b0549.js:10297
__commitTemplateResult @ app.e45b0549.js:10297
commit @ app.e45b0549.js:10297
update @ app.e45b0549.js:10297
__commitTemplateResult @ app.e45b0549.js:10297
commit @ app.e45b0549.js:10297
a @ app.e45b0549.js:10297
H.render @ app.e45b0549.js:10297
update @ app.e45b0549.js:10297
performUpdate @ app.e45b0549.js:10297
_enqueueUpdate @ app.e45b0549.js:10297
async function (async)
_enqueueUpdate @ app.e45b0549.js:10297
requestUpdateInternal @ app.e45b0549.js:10297
set @ app.e45b0549.js:10297
value @ chunk.1ea6ef6c0d2b8e9fc07f.js:981
performUpdate @ app.e45b0549.js:10297
_enqueueUpdate @ app.e45b0549.js:10297
async function (async)
_enqueueUpdate @ app.e45b0549.js:10297
requestUpdateInternal @ app.e45b0549.js:10297
set @ app.e45b0549.js:10297
commit @ app.e45b0549.js:10297
commit @ app.e45b0549.js:10297
update @ app.e45b0549.js:10297
__commitTemplateResult @ app.e45b0549.js:10297
commit @ app.e45b0549.js:10297
a @ app.e45b0549.js:10297
H.render @ app.e45b0549.js:10297
update @ app.e45b0549.js:10297
performUpdate @ app.e45b0549.js:10297
_enqueueUpdate @ app.e45b0549.js:10297
async function (async)
_enqueueUpdate @ app.e45b0549.js:10297
requestUpdateInternal @ app.e45b0549.js:10297
set @ app.e45b0549.js:10297
(anonymous) @ app.e45b0549.js:41607
value @ app.e45b0549.js:41607
value @ app.e45b0549.js:44533
performUpdate @ app.e45b0549.js:10297
_enqueueUpdate @ app.e45b0549.js:10297
async function (async)
_enqueueUpdate @ app.e45b0549.js:10297
requestUpdateInternal @ app.e45b0549.js:10297
set @ app.e45b0549.js:10297
value @ app.e45b0549.js:41607
(anonymous) @ app.e45b0549.js:41607
s @ core.87e3602e.js:1
(anonymous) @ core.87e3602e.js:1
(anonymous) @ core.87e3602e.js:1
_handleMessage @ core.87e3602e.js:1
(anonymous) @ core.87e3602e.js:1

[neliss]

This is probably caused by an entity in your HA config that the card is unable to process.
I changed some things in the v2.0.1 release, that will make the card robust for such entities.
Please update to this version.

With the new version, you can check the browser log for information about which entity gives the problem.

[maxgiordan (max)]

If it helps to understand any errors: I just upgraded to version 2.01 and everything works like a gem.
Sorry if I repeat myself: great job!

[Bart1992]

I’ve updated also to 2.0.1, everything is working perfectly now.
Thanks for all the hard work! And maybe I repeat others, but this integration makes Hass usefull (using it since the beginning in august 2020!

[5310]

Thanks for all your great work.
I have a feature request and am off traveling for holiday so no easy github access so sorry I am posting it here using my phone.

A vacation mode schedule that randomly turn things on and off. I currently use an appdeamon app called occupsim. I tell it the number of times I want the light turned on and it creates a random schedule for that many on/offs. Is this something the Scheduler could do?
Thanks

[tmchow]

@5310

A vacation mode schedule that randomly turn things on and off. I currently use an appdeamon app called occupsim. I tell it the number of times I want the light turned on and it creates a random schedule for that many on/offs. Is this something the Scheduler could do?

Would it be just easier to have an automation do it?

Random Light Schedule

This is how I do my random lights when I am away from home. The below automation calls the script every 15 minutes plus 1 to 10 minutes random. The script checks if the light is on/off and trips it the other way. There is a group of inside lights that it chooses from. Automation: id: away_lights alias: Away Lights trigger: platform: time minutes: ‘/15’ condition: condition: and conditions: condition: state entity_id: alarm_control_panel.alarm_system state: ‘armed_away’ condition:…

[5310]

Thanks for the ideas. My appdaemon does the same thing. Just thought that random and repeat functionality would be a great addition.

[Canaletto (Lionel)]

Hello!

appdaemon…
For a long time it scared me a little. Then I used for ControlerX… And yesterday I spent hours on Schedy which is really a very well done scheduller ! Alas he doesn’t have a GUI!