Minor docs example updates.
This commit is contained in:
@@ -20,7 +20,6 @@ view:
|
||||
| `reset_after_interaction` | `true` | If `true` the card will reset to the default configured view (i.e. 'screensaver' functionality) after `interaction_seconds` has elapsed after user interaction. |
|
||||
| `triggers` | | How to react when a camera is [triggered](cameras/README.md?id=triggers). |
|
||||
| `default_cycle_camera` | `false` | When set to `true` the selected camera is cycled on each default view change. |
|
||||
| `update_entities` | | **YAML only**: A card-wide list of entities that should cause the view to reset to the default (if the entity only pertains to a particular camera use [`triggers`](cameras/README.md?id=triggers) for the selected camera instead. |
|
||||
|
||||
## `default_reset`
|
||||
|
||||
|
||||
+6
-5
@@ -479,9 +479,9 @@ overrides:
|
||||
This example changes the default card view from `live` to `image` depending on
|
||||
the value of the `binary_sensor.alarm_armed` sensor. The override alone will
|
||||
only change the _default_ when the card next is requested to change to the
|
||||
default view. By also including the `update_entities` parameter, we ask the card
|
||||
to trigger a card update based on that entity -- which causes it to use the new
|
||||
overriden default immediately.
|
||||
default view. By also including the `view.default_reset.entities` parameter, we
|
||||
ask the card to trigger a card update based on that entity -- which causes it to
|
||||
use the new overriden default immediately.
|
||||
|
||||
```yaml
|
||||
type: custom:frigate-card
|
||||
@@ -489,8 +489,9 @@ cameras:
|
||||
- camera_entity: camera.office
|
||||
view:
|
||||
default: live
|
||||
update_entities:
|
||||
- binary_sensor.alarm_armed
|
||||
default_reset:
|
||||
entities:
|
||||
- binary_sensor.alarm_armed
|
||||
overrides:
|
||||
- conditions:
|
||||
- condition: state
|
||||
|
||||
Reference in New Issue
Block a user