Wth why do automations have just a on or off state an not "running"

it’s easy to see when an automation is triggered. but not when the automation is done or stopped. with the added state “running” that would be clear.

Because automations can be turned on or off :slight_smile:
(In on state, they can trigger, in off state, they can’t).

An attribute on an automation might make sense (maybe, although, I’m personally not a fan of attributes).

It’s not so simple with parallel automations that have multiple that are running. The attribute current tells you how many are running. You can make a template sensor or just expose that value to see if it’s running or not.

current :slight_smile:

Possibly add the count to the UI next to the state.

2 Likes

Oh doh! :man_facepalming: