just so I can explain myself best:
I used:
- wait_template: >
{{ is_state('device_tracker.imac_lan' , 'not_home') and
is_state('device_tracker.imac_wifi' , 'not_home') and
states('sensor.dorm_actueel')|float < 1}}
timeout: '00:05:00'
continue_on_timeout: 'false'
the template is fine, and works perfectly with all 3 entities in their various states. Only evaluating the full template to True if both device_trackers are not_home And the sensor <1
Ive thought about the timeout notation, as you do, but ive checked, and it acts on the 5 minute count just fine.
what should happen is that the script stops after the timeout. It simply doesnt, and continues with the rest of the script, if I quote the ‘false’. Doesn’t matter what comes after it. In my setting, it runs another script switching of my iMac… which isn’t desirable…
taking out the quotes, makes it behave as desired… just tried is 2 more times, and 100% repeatable.
My PR was only aimed at the ‘false’, and I have explicitly mentioned that. Reading what you experience with the ‘true’ , that was a wise decision.
Now leaves us with the 'false'
versus false
.
Might it be a bug then, instead of a documentation error…
Please note that the wait_template itself works fine also: if the devices turn not_home within the 5 minutes timeframe the sensor floats below 1, turning the template into True, and immediately the script continues correctly