Hidden enabled schedules

[JKoehorst2]

Checklist

• I checked for similar existing issues (both open and closed) before posting (lot of similarities, but didn't find the same one)
• I am running the latest version (component=3.3.8, card=4.0.10)

Expected behavior

Disabling all schedules in the dashboards should not trigger any action from a schedule.

Actual behavior

I have 9 schedules on my dashboards, if I disabled them all there are still 6 enabled schedules in the scheduler.storage file.
Some are of old unused devices and cause no problem. But some are of devices that are in use and switch on or off at times we don't want them to.

Steps to Reproduce

I didn't manage to reproduce it, adding and deleting schedules works as expected.
If these problems occur, it's always after changing an existing schedule.

If anyone has an idea how to test something I would gladly do so, I really like this component. But wake-up lights coming on an hour early is no fun.

[JKoehorst2]

Well, that's an argument to close any issue.
But I managed to reproduce it, I'm making a bunch of screenshots now to make it clear.

[JKoehorst2]

In short the problem is with configuring the visible entities in a schedule.
If you have an active schedule and pick another entity for this schedule, the previous schedule rule will stay active and is not visible anymore.

Steps to reproduce:
Make a simple schedule for a plug:

It looks like this in the storage file, as expected:

Pick a different visible entity for this schedule:

Now only the schedules of the different entity are displayed:

But the hidden schedule stays active in the storage file:

This way you loose track of the active schedules.
It would be nice if hidden schedules are automatically disabled.

[JKoehorst2]

scheduler.storage isn't written until Home Assistant shuts down, so your description is bad/wrong.

No, the file is written around 10sec. later.
I can disable a schedule and refresh the file editor in HA 10sec. later and the change is there.

EDIT: on my x86 running HassOS.

[nielsfaber]

Please take note of this setting:

The setting controls whether or not the scheduler-card will only show the schedules according to your card configuration, or all in your HA installation.
The ones that are in your HA installation but not in your card configuration (for example, a schedule which controls a cover entity, but you set your card configuration to not include cover entities), will show up at the bottom of the card, under this clickable button:

The switch at the top of the card:

only will enable/disable schedules that are visible in the card.
So setting this to OFF will not guarantee that all schedules in your HA installation are OFF.

I hope this helps.

If you still think there is a bug, please provide evidence.
E.g. show a screen video where you disable a schedule but it remains active in the background (background being either the scheduler.storage file or the state of corresponding switch entity).

[JKoehorst2]

Thanks, I see, maybe I'm using it in the wrong way. But I like to have a schedule card next to the device to only show the schedules of that device (scheduled off airco, stuff like that).

I never use a big list containing all schedules because it quickly becomes unclear.

I'm not going to argue if this is a bug, design flaw or whatever, but it is a source of problems of otherwise a great component.

[infamy]

So to add to this. it is annoying that this can happen but more concerning is that it is NOT reflected in the controlled device logs that it was turn on or off by the scheduled entity. (and no link back to it) so its possible to have a schedule that is "hidden" that you cannot find under automation or via the logs for the device being controlled. (some of this is on the HA side) but seems to be somewhat related to this.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days