Use frontend state name with localization in automation trigger and condition descriptions #13674
Unanswered
krazos
asked this question in
Automations / scripts / scenes
Replies: 0 comments
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.
-
The auto-generated description of automation triggers and conditions reports the actual (backend) state of the entity. For consistency with the new state and attribute value auto-completion, it would be better for the auto-generated description to instead use the frontend state name with localization.
Example 1 (Trigger - state of binary sensor w/ device_class = door):
When Front Door changes from on to offshould becomeWhen Front Door changes from open to closedExample 2 (Condition - state of person):
Confirm John is not_homeshould becomeConfirm John is awayBeta Was this translation helpful? Give feedback.
All reactions