Scheduler card/custom component

thats exactly the same issue i have.

Usually when you add the card to your lovelace on the left side should appear a visual editor where you can select the entities and all other things. This part doesn’t work, is not shown. And I*m not able to add them manually.

So I’m not so stupid … there’s something wrong … still a very interesting job, congratulations to neliss.

Hi
I have a schedule to turn underfloor heating on & off, which works great.
But, using the timing scheme, it has to perform an action at midnight (start of a new day). I’ve got this set to turn the underfloor heating off, but it is already off from the night before. That works fine, but it causes the heating controller to light-up in the bedroom every night at midnight.
Is there a way of defining & performing “no action” for a time period? I know how to define the custom actions, but how can I define a “do nothing” custom action?
Thanks

I saw an issue with the deleting of schedules. I have it fixed locally, will release an update soon.

There is no need to assign actions to each timeslot.
The view is just restricted from 00:00 - 23:59 (spanning a full day), but you can create slots as you desire, and leave slots blank where you don’t want actions.

Can anyone tell why my custom schedule name isn’t working here?
Nothing seems to change the primary info.

Never mind I found the answer in a post above.

neliss

Nov 17

display_options applies to the whole card, not to one entitiy.
So it shouldn’t be placed within customize .
This is also documented .

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.

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 …

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.

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

1 Like

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.

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.

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:
image

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:

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)?

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?

@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…

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?

1 Like

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

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

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.