Currently, there is only the option to continue or abort in a “Wait for Trigger” action depending on the “continue on timeout” toggle.
Ideally, this toggle would be changed to two paths, dependent on whether the “Wait for Trigger” receives the desired trigger, or times out. If the user wants to abort the script on timeout, it would still be possible to add a “Stop” action on the timeout path, but would allow for a separate set of actions as well.
Already possible by checking wait variable after the wait_template or wait_for_trigger have exited. The documentation contains an example of how to use to use it.
Thank you. Again, this is a feature I’d like to see in the automation UI.
It’s unlikely the Automation Editor, in Visual mode, will expose every feature in Home Assistant’s scripting language because it would not only clutter the UI, it would overwhelm the novice user with a dizzying array of choices, including advanced features that aren’t used often.
FWIW, I can’t speak for all experienced users but I don’t use the Automation Editor, not in Visual mode or YAML mode (because even in YAML mode it introduces quirks and constraints).
Interesting. How do you trigger sutomation? Throught calling scripts?
I create my automations using a text editor (Visual Studio Code with Home Assistant Config Helper), not the Automation Editor. I use the documentation for Home Assistant’s scripting language as my feature guide, not the subset of features exposed by the Automation Editor’s Visual mode.
Oh wow. You may have just completely changed the way I write for, and interact with HA! Thanks!
To your original point, I completely understand that it would be chaotic to expose ALL of the YAML features in the UI, this and the “State OR” threads were two specific features I thought would be helpful.