In the above example, the sensor is a mains powered device that’s very chatty, sending illuminance updates every 2-3 seconds and the automation doesnt trigger (as often as I would expect)
My basic tests suggest that if the sensor keeps updating the illuminance values, its effectively resetting the 30 seconds.
With a binary sensor, its more straightforward… its either on or off for the duration. But for something like illuminance or active power, I’m not clear.
Thats what I suspected, but I just wanted to double check.
I’m trying to find a way to make the automation fire less often, which caused me to look at the above.
Also, keep in mind that a state trigger without at least one assigned to/from/not_to/not_from value will fire on all updates not only of the state of the entity, but also updates to any of its attributes. In some integrations sensors have tons of attributes which can update asynchronously from the state, so an open-ended State trigger with a for duration will almost never fire.