Skip to content

Commit bf2ca91

Browse files
committed
power: update trigger behavior values
1 parent 967cb2d commit bf2ca91

2 files changed

Lines changed: 5 additions & 5 deletions

File tree

source/_includes/triggers/behavior.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,6 @@
22

33
When you target more than one entity (or select an area, floor, or label that contains several), the **Trigger when** option controls how the trigger responds:
44

5-
- **Each** (`any` in YAML, default): the trigger fires every time any one of the targeted entities transitions. For example, if you monitor three motion sensors in the living room and someone walks past sensor 1, the automation fires. When they walk past sensor 2 a moment later, it fires again. Every individual event counts.
5+
- **Each** (`each` in YAML, default): the trigger fires every time any one of the targeted entities transitions. For example, if you monitor three motion sensors in the living room and someone walks past sensor 1, the automation fires. When they walk past sensor 2 a moment later, it fires again. Every individual event counts.
66
- **First** (`first` in YAML): the trigger fires only on the first transition in the targeted group, then waits until all targeted entities have reset before it fires again. For example, if you monitor the same three motion sensors, the automation fires when the first one picks up movement (someone entered the room). The other two firing afterward are ignored, so you get one notification per "someone walked in" event instead of three.
7-
- **All** (`last` in YAML): the trigger fires only after the last targeted entity in the group has fired, meaning all of them are now in the expected state. For example, if you monitor the lights in the living room, bedroom, and hallway, the automation fires only once all three have turned off. This is useful for scenarios like "start the robot vacuum only after every light on the floor is off," so you know the room is truly empty.
7+
- **All** (`all` in YAML): the trigger fires only after the last targeted entity in the group has fired, meaning all of them are now in the expected state. For example, if you monitor the lights in the living room, bedroom, and hallway, the automation fires only once all three have turned off. This is useful for scenarios like "start the robot vacuum only after every light on the floor is off," so you know the room is truly empty.

source/_triggers/power.crossed_threshold.markdown

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -136,12 +136,12 @@ behavior:
136136
description: |
137137
When multiple entities are targeted, controls when the trigger fires:
138138

139-
- `any` (**Each** in the UI, default): fires every time any targeted entity crosses the threshold.
139+
- `each` (**Each** in the UI, default): fires every time any targeted entity crosses the threshold.
140140
- `first` (**First** in the UI): fires only on the first threshold crossing.
141-
- `last` (**All** in the UI): fires only after every targeted entity crosses the threshold.
141+
- `all` (**All** in the UI): fires only after every targeted entity crosses the threshold.
142142
required: false
143143
type: string
144-
default: any
144+
default: each
145145
for:
146146
description: |
147147
How long the reading must remain past the threshold before the trigger fires. Accepts a duration string in `HH:MM:SS` format. For example, `00:05:00` waits 5 minutes before the trigger runs.

0 commit comments

Comments
 (0)