Automation Last Triggered is always null

[jstride (Jake Stride)]

None of my automations have a last triggered set even for those I’m seeing running (likewise my xiaomi binary sensor switches don’t get last_updated/changed updated when they are pressed). Am I missing something?

I’m basically hoping to stop automations running immediately one after another if you press the button twice by accident and was hoping to use states.automation.some_automation.last_triggered

[petro]

Has HA been restarted? If you restart, it wipes those values out.

[jstride (Jake Stride)]

Plenty of other automations have laat_triggered seems to be ones based on an event that fail to update.

[petro]

Any errors in the log?

[Holdestmade]

I too am having this problem. I noticed it when on another post:

Unsupported operand type(s) for -: 'NoneType' and 'float'

Seems I am not the only one, lots of posts on here, all say they are reset on restart Wonder how yours aren’t ?

All my automations reset to null on reset and automations restart.

@123 has been trying his setup and all his keep the last_triggered attribute on restart.

Only difference we can see is I am on Hassio and he is not.

Anyone have any ideas ?

[Holdestmade]

So, @123 has figured this out. If you have initial_state set to true in your automation, that will cause HA to change the last_triggered attribute to null on automations reload or restart

[123 (Taras)]

Relevant post is here:

Unsupported operand type(s) for -: 'NoneType' and 'float'

I found the culprit. It’s not the installation flavor (venv, docker, hass.io, hassbian) but that silly remedy all too frequently recommended to everyone to fix their automation on/off woes. Namely this one: initial_state: true Here’s how I tested it: I added initial_state: true to one of the three automations on my test server, restarted Home Assistant and, ta-dah, its last_triggered is now null. I triggered the automation and its last_triggered is assigned a date/time. I reloaded …