jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify the timestamp of buttons doesn't matter for the automation example (#39798)

Browse Source
This commit is contained in:
Franck Nijhof 2025-07-01 23:11:05 +02:00 committed by GitHub
parent 020099ebad
commit 9d1e9c6cd3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
source/_integrations/button.markdown
View File

@ -42,7 +42,10 @@ In addition, the entity can have the following states:
- **Unknown**: The state is not yet known. - **Unknown**: The state is not yet known.
Because the {% term state %} of a button entity in Home Assistant is a timestamp, it 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 ```yaml
triggers: triggers: