Allow numeric state trigger/condition against zone entities (#32038)

Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
This commit is contained in:
Franck Nijhof 2024-03-26 19:41:57 +01:00 committed by GitHub
parent 384fb14612
commit a30e2cd33c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 4 additions and 4 deletions

View File

@ -277,8 +277,8 @@ Listing above and below together means the numeric_state has to be between the t
In the example above, the trigger would fire a single time if a numeric_state goes into the 17.1-24.9 range (above 17 and below 25). It will only fire again, once it has left the defined range and enters it again.
</div>
Number helpers (`input_number` entities), `number` and `sensor` entities that
contain a numeric value, can be used in the `above` and `below` thresholds,
Number helpers (`input_number` entities), `number`, `sensor`, and `zone` entities
that contain a numeric value, can be used in the `above` and `below` thresholds,
making the trigger more dynamic, like:
```yaml

View File

@ -218,8 +218,8 @@ condition:
below: 25
```
Number helpers (`input_number` entities), `number` and `sensor` entities that
contain a numeric value, can be used in the `above` and `below`
Number helpers (`input_number` entities), `number`, `sensor`, and `zone` entities
that contain a numeric value, can be used in the `above` and `below`
options to make the condition more dynamic.
```yaml