From b2ed9d709aeb7925db583b68a561df3eac3d36de Mon Sep 17 00:00:00 2001 From: nadimz Date: Wed, 2 Jul 2025 14:10:10 +0200 Subject: [PATCH] Improve the description of the state field of Template Lock (#39784) Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/template.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown index de19f2645c3..1f66306c795 100644 --- a/source/_integrations/template.markdown +++ b/source/_integrations/template.markdown @@ -1446,7 +1446,7 @@ lock: type: boolean default: false state: - description: Defines a template to set the state of the lock. + description: Defines a template to set the state of the lock. Valid output values from the template are `locked`, `unlocked`, `open`, `locking`, `unlocking`, `opening`, and `jammed`, which are directly mapped to the corresponding states. In addition, `true` and `on` are valid as synonyms to `locked` while `false` and `off` are valid as synonyms to `unlocked`. required: true type: template unlock: @@ -3471,7 +3471,7 @@ vacuum: "attribute: template": description: The attribute and corresponding template. required: true - type: template + type: template availability_template: description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"`, or a non-zero number, the entity will be `available`. If the template returns any other value, the entity will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed. required: false