From 120b2574035b8d73fc2607972d68434446e4a571 Mon Sep 17 00:00:00 2001
From: epenet <6771947+epenet@users.noreply.github.com>
Date: Mon, 30 Jun 2025 10:52:58 +0200
Subject: [PATCH] Binary sensor templates can return unknown state (#39739)

---
 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 2e2be5425f1..de19f2645c3 100644
--- a/source/_integrations/template.markdown
+++ b/source/_integrations/template.markdown
@@ -382,7 +382,7 @@ binary_sensor:
       type: device_class
       default: None
     state:
-      description: The sensor is `on` if the template evaluates as `True`, `yes`, `on`, `enable` or a positive number. Any other value will render it as `off`. The actual appearance in the frontend (`Open`/`Closed`, `Detected`/`Clear` etc) depends on the sensor's device_class value
+      description: The sensor is `on` if the template evaluates as `True`, `yes`, `on`, `enable` or a positive number. The sensor is `unknown` if the template evaluates as `None`. Any other value will render it as `off`. The actual appearance in the frontend (`Open`/`Closed`, `Detected`/`Clear` etc) depends on the sensor's device_class value
       required: true
       type: template