Ignore empty "value_template" fields. #14838
Unanswered
apbarratt
asked this question in
Automations / scripts / scenes
Replies: 2 comments
-
Thank you to Tinkerer on the Discord server for assistance figuring this one out for me :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When creating a numeric_state trigger recently, I found that my automation stopped triggering.
When reviewing the yaml for the trigger, I found the following:
I must have typed something briefly into the visual editor's value template field then removed it. I can think of no reason a person would deliberately set a value_template to an empty string (though happy to be corrected).
Suggested solution 1
I would suggest that here (and perhaps in other similar situations) the visual editor should remove value_template if it is set to an empty string.
Suggested solution 2
Alternatively, a small "unset" button of some sort next to optional fields might be valuable. Such a button would only become visible if indeed an input field has been set to a value at all and thus it would become quickly obvious when an unwanted empty value may cause issues. Or so is my thinking.
Beta Was this translation helpful? Give feedback.
All reactions