chore: use of correct 24-hour clock terminology (#38758)

This commit is contained in:
Alastair McCormack 2025-04-28 07:22:17 +01:00 committed by GitHub
parent 3215dc7980
commit 563bfd34fd
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions

View File

@ -696,7 +696,7 @@ A string that represents a time to fire on each day. Can be specified as `HH:MM`
automation:
- triggers:
- trigger: time
# Military time format. This trigger will fire at 3:32 PM
# 24-hour time format. This trigger will fire at 3:32 PM
at: "15:32:00"
```

View File

@ -727,7 +727,7 @@ For example, if you wanted to select a field from `trigger` in an automation bas
- `utcnow()` returns a datetime object of the current time in the UTC timezone.
- For specific values: `utcnow().second`, `utcnow().minute`, `utcnow().hour`, `utcnow().day`, `utcnow().month`, `utcnow().year`, `utcnow().weekday()` and `utcnow().isoweekday()`.
- Using `utcnow()` will cause templates to be refreshed at the start of every new minute.
- `today_at(value)` converts a string containing a military time format to a datetime object with today's date in your time zone. Defaults to midnight (`00:00`).
- `today_at(value)` converts a string containing a 24-hour time format to a datetime object with today's date in your time zone. Defaults to midnight (`00:00`).
- Using `today_at()` will cause templates to be refreshed at the start of every new minute.