From 9d1e9c6cd33320b02c03107a33775c00433571f8 Mon Sep 17 00:00:00 2001 From: Franck Nijhof Date: Tue, 1 Jul 2025 23:11:05 +0200 Subject: [PATCH] Clarify the timestamp of buttons doesn't matter for the automation example (#39798) --- source/_integrations/button.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/source/_integrations/button.markdown b/source/_integrations/button.markdown index ac62dcc0ccf..8b7b2544176 100644 --- a/source/_integrations/button.markdown +++ b/source/_integrations/button.markdown @@ -42,7 +42,10 @@ In addition, the entity can have the following states: - **Unknown**: The state is not yet known. Because the {% term state %} of a button entity in Home Assistant is a timestamp, it -means we can use it in our automations. For example: +changes every time the button is pressed. This means we can trigger automations on +any state change of the button entity, which effectively captures when the button +is pressed. We don't need to use the actual timestamp value; we only care that the +state changed, indicating a button press: ```yaml triggers: