I’ve created simple automation that starts a pump when one of five valves gets open and stops the pump when all valves are closed. Below is my code: - alias: Turn on the pump after 5 seconds trigger: platform: state entity_id: switch.podlogowka_salon, switch.podlogowka_sypialnia, switch.…

Basically, with what we now know. We can watch for any valve coming on (or going off), (that’s the entity list in the binary_sensor) this will update the sensor using the template. If the template evaluates to true, one of the valves is on (2, 3, 4 or all 5 - it doesn’t matter) the delay_on mean…

Automation - trigger for state - crazy behaviour (maybe a bug?)

Configuration

rocketman October 11, 2019, 12:46am 2

I had a similar problem, and it looks like there is no “official” expected behavior for what should happen when an automation fires while that same automation is still executing: