When adding an automation entity the state is always 'Triggered' and the timestamp is the last triggered time. The documentation states that this is intended, and can be overridden using the content_template option, however this does not work. When using content_template the state is still Triggered instead of the actual on or off state of the automation, and the last changed timestamp does not replace the display of the last triggered timestamp nor does it show an elapsed time.
I would like to show automations that have been turned off temporarily (like a motion announcement when the gardener is out front working), and how long it's been since it was turned off.
When viewing an automation state in the developer states tool, the state is always on or off and the trigger times are attributes. It seems like the best options here are to show the state and last updated times as all other entities do, and then allow overriding this behavior using the attributes.
When adding an automation entity the state is always 'Triggered' and the timestamp is the last triggered time. The documentation states that this is intended, and can be overridden using the content_template option, however this does not work. When using content_template the state is still Triggered instead of the actual on or off state of the automation, and the last changed timestamp does not replace the display of the last triggered timestamp nor does it show an elapsed time.
I would like to show automations that have been turned off temporarily (like a motion announcement when the gardener is out front working), and how long it's been since it was turned off.
When viewing an automation state in the developer states tool, the state is always on or off and the trigger times are attributes. It seems like the best options here are to show the state and last updated times as all other entities do, and then allow overriding this behavior using the attributes.