You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I am trying to unify some automations using a script. The script is meant to check whether the value stored in an input field matches the field/parameter passed to it by the automation. Here is the code:
- condition: stateentity_id: input_text.schalterszenestate: "{{ scene }}"
To my surprise, "{{ scene }}" is not substituted with the value of the field, but taken as a literal value. I can validate this by manually setting the value of the field to "{{ scene }}" and seeing that this causes the condition to evaluate to true. scene is defined in the script, in successfully uses it at another location.
This seems like a bug to me. If it is not, I did not see this mentioned in the documentation.
What version of Home Assistant Core has the issue?
core-2024.5.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
LarsWigger
changed the title
Condition state does takes template literally
Condition state takes template literally
May 11, 2024
The problem
Hello,
I am trying to unify some automations using a script. The script is meant to check whether the value stored in an input field matches the field/parameter passed to it by the automation. Here is the code:
To my surprise,
"{{ scene }}"
is not substituted with the value of the field, but taken as a literal value. I can validate this by manually setting the value of the field to"{{ scene }}"
and seeing that this causes the condition to evaluate totrue
.scene
is defined in the script, in successfully uses it at another location.This seems like a bug to me. If it is not, I did not see this mentioned in the documentation.
What version of Home Assistant Core has the issue?
core-2024.5.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: