Whilst the Frigate support in this card is the best among camera engines, the name incorrectly suggests that Frigate is a requirement. Instead, to broaden the appeal, change to more camera agnostic name. This does not suggest any change in priority, role or support for Frigate. This change is likely to be bug prone, due to the size of the rename -- the code contains 1500+ references to "Frigate" most of which make sense to rename, some which do not, all of which needed human assessment. - Closes #1298 BREAKING CHANGE: References to `frigate-card` in all kinds of configuration need to be updated to `advanced-camera-card`. An automated config upgrade should take care of the majority of usecases (click `Edit -> Upgrade -> Save`), though may not be perfect.
1.4 KiB
1.4 KiB
automations
Automatically take actions based on conditions being met.
?> To change configuration conditionally use overrides.
automations:
- conditions:
- [condition]
actions:
- [action]
actions_not:
- [action]
| Option | Default | Description |
|---|---|---|
conditions |
A list of conditions that must evaluate to true in order to trigger the automation. |
|
actions |
An optional list of actions that will be run when the conditions evaluate true. |
|
actions_not |
An optional list of actions that will be run when the conditions evaluate false. |
Fully expanded reference
automations:
- conditions:
- condition: fullscreen
fullscreen: true
actions:
- action: custom:advanced-camera-card-action
advanced_camera_card_action: live_substream_on
actions_not:
- action: custom:advanced-camera-card-action
advanced_camera_card_action: live_substream_off