Automations: show time and date of next sheduled action

[frankn66]

Hi,

I noticed that the Setting/Automations tab shows a column for when an automation was “last run”. It would be helpful to add a column that also shows when the automation is scheduled to trigger “next”. For example, this is very useful if you have a sprinkler automation that is dependant on a time or time related action like “sunrise”. The idea is that you can see in one single screen, the automation name, a column when the automation was “last” run and one column when the automation is scheduled to run “next”.

Can this be added to the HA UI? It would seem logical to add this by default in the UIl there is enough space available for one more column.

Thank you,

[code-in-progress (Bill - I write code.)]

This seems like it should be a feature request (and don’t forget to vote for your own feature request).

[Didgeridrew]

While “last run” is a known fact, “next run” is, at best, a guess… and only kind-of-feasible for a very limited number of time-related triggers. The vast majority of triggers are not strictly time-based, they are based on events that can occur at any time.

@frankn66

It would seem logical to add this by default in the UIl there is enough space available for one more column.

It does not seem logical to me to add a column that would be mostly blank or full of fake data.

---

Proposal: "next_trigger" attribute for automations

It would be useful to have an additional attribute for automations which would contain a timestamp value that is equal to the next time the automation will be triggered. There is currently an attribute which says when the automation was last triggered. The “next trigger” value would be in the same format. Open question: If the time is not able to be discerned (many automations are not time-based, but instead triggered on events) what should the value be?

[frankn66]

This was added as a feature request.

[frankn66]

If the automation does not dpend on a future “calculated” timestamp like “sunrise / sunset” it could simply be blank. Before HA I used an automation system that showed the two columns: “last run” and “next time it will run”, when it was dependant on an event like sunrise or some specific time plus an offset like 6:00AM plus 2 hours, then the “next” column would show the exact time the automtion would be triggered next. And the automations that were not dependant on a time would simply show a dash.