From 3aae1c75f6840284a674f67d43e7ee68dd6e2f3c Mon Sep 17 00:00:00 2001 From: Mark Bergsma Date: Tue, 11 Jun 2024 22:17:45 +0200 Subject: [PATCH] Explain time entity support in time condition --- source/_docs/scripts/conditions.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/source/_docs/scripts/conditions.markdown b/source/_docs/scripts/conditions.markdown index 21f7c96694eb..0e993a4cd9c6 100644 --- a/source/_docs/scripts/conditions.markdown +++ b/source/_docs/scripts/conditions.markdown @@ -563,7 +563,7 @@ A better weekday condition could be by using the [Workday Binary Sensor](/integr -For the `after` and `before` options a time helper (`input_datetime` entity) +For the `after` and `before` options a time helper (`input_datetime` entity), a `time` entity, or another `sensor` entity containing a timestamp with the "timestamp" device class, can be used instead. @@ -574,6 +574,9 @@ condition: after: input_datetime.house_silent_hours_start before: input_datetime.house_silent_hours_end + - alias: "Example referencing a time entity" + before: time.dnd_start + - alias: "Example referencing another sensor" after: sensor.groceries_delivery_time ```