Current Action as a State

[Corneloues]

Checklist

• I checked for similar existing requests (both open and closed) before posting.
• My request is generic, other users may benefit from it too.

Proposal

Return the current action as a state. Therefore each schedule becomes a state machine.

Additional info

States can be used as conditions or triggers thus giving greater flexibility.

By example:

• I only want to make the the Boost dashboard section visible when the current action is not "Heat".
• I want to interrupt one schedule because the state of another schedule has changed.
• I want to trigger several automations dependent on the state of the schedule.

[bennydiamond]

+1 to this.

I'd like to know what was the last schedule element that triggered and have this value in a sensor or even as an attribute to each schedule switch entity.

Generating an event with data containing the scheduler switch entity name and time of trigger could be neat as well.

[nielsfaber]

It is chosen to have a schedule represented as an (on/off) switch entity. I'd like to keep it that way.
The next timeslot / action is visible in the attributes of the switch entity.

[Corneloues]

It is chosen to have a schedule represented as an (on/off) switch entity. I'd like to keep it that way. The next timeslot / action is visible in the attributes of the switch entity.

Can you recommend the, how I could achieve the use cases in my initial feature request using your existing switch please?

[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

[Corneloues]

I'm still keen to understand how I can achieve the scenarios highlighted in the feature request, while honouring your decision to keep the schedule as an on/off switch.

[hacscred]

@Corneloues All of the things you want, I have operational. Just get some consultant to do so it or do it yourself, but there's no problem in the scheduler.