From 78a5b5996dc3e7f2c8ae39346ea9644d0a5a9861 Mon Sep 17 00:00:00 2001 From: Fabricio Avila Date: Tue, 9 Nov 2021 10:54:03 +0000 Subject: [PATCH] Update entity used in the "STARTUP" example (#20223) --- source/_integrations/template.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown index 8e0cfa3d044..c1d0d2e14ee 100644 --- a/source/_integrations/template.markdown +++ b/source/_integrations/template.markdown @@ -310,7 +310,7 @@ If the template accesses every state on the system, a rate limit of one update p ### Startup -If you are using the state of a platform that might not be available during startup, the Template Sensor may get an `unknown` state. To avoid this, use `is_state()` function in your template. For example, you would replace {% raw %}`{{ states.cover.source.state == 'open' }}`{% endraw %} with this equivalent that returns `true`/`false` and never gives an `unknown` result: +If you are using the state of a platform that might not be available during startup, the Template Sensor may get an `unknown` state. To avoid this, use `is_state()` function in your template. For example, you would replace {% raw %}`{{ states.switch.source.state == 'on' }}`{% endraw %} with this equivalent that returns `true`/`false` and never gives an `unknown` result: {% raw %}