From 2ecb085eff3858936819d1ab5552b41edb02a978 Mon Sep 17 00:00:00 2001
From: Franck Nijhof <git@frenck.dev>
Date: Sun, 6 Sep 2020 16:44:56 +0200
Subject: [PATCH] Time condition can also accept an input_datetime Entity ID
 (#14404)

---
 source/_docs/scripts/conditions.markdown | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown
index 8d5e7bd75dc..f25329c73a0 100644
--- a/source/_docs/scripts/conditions.markdown
+++ b/source/_docs/scripts/conditions.markdown
@@ -350,6 +350,15 @@ A better weekday condition could be by using the [Workday Binary Sensor](/integr
 
 </div>
 
+For the `after` and `before` options a time helper (`input_datetime` entity) can be used instead.
+
+```yaml
+condition:
+  condition: time
+  after: input_datetime.house_silent_hours_start
+  before: input_datetime.house_silent_hours_end
+```
+
 ### Zone condition
 
 Zone conditions test if an entity is in a certain zone. For zone automation to work, you need to have set up a device tracker platform that supports reporting GPS coordinates.