Dermot Duffy
17146c8ca6
The `initialized` state (used in conditions/triggers) was written once and never cleared, so it meant "has this card ever been initialized" while everything reading it took it as "is this card usable now". Home Assistant takes a card off the page and puts it back whenever its dashboard tab is left and returned to, so the card initialized again while the state claimed it was initialized throughout: `trigger: initialized` fired once per card rather than once per startup, and automations were dropped in between. The card lifecycle is now an explicit state machine (`SessionManager`), the only writer of `initialized`, which separates a card that is starting up from one initializing part of itself again while it runs. A new `ever` parameter (conditions/triggers) selects the old latched behaviour. `remote_control` uses that parameter to keep its two camera priorities correct under repeated starts. With `camera_priority: entity` the card now re-reads the entity every time it starts, so a camera selected while the card was away is picked up on return. With `camera_priority: card` the card writes the entity on its first start only, unchanged, since repeating that write would overwrite a camera the user had selected. Closes: #2642 BREAKING CHANGE: `condition: initialized` is now `false` whenever the card is not usable, and `trigger: initialized` fires each time the card starts up rather than only the first time. Set `ever: true` on either to keep the previous behaviour.
Configuration
The card supports a myriad of configuration options for simple or complex setups.
Absolute minimum configuration
type: custom:advanced-camera-card
Minimal camera configuration
type: custom:advanced-camera-card
cameras:
- camera_entity: camera.office
Minimal folder configuration
type: custom:advanced-camera-card
folders:
- type: ha
Configuration blocks
Top-level configuration blocks
No top-level option is required. If cameras is omitted the card will still
render and can operate in image or folders views depending on configuration.
| Option | Description |
|---|---|
automations |
Take action when conditions are met. |
cameras |
Configures the cameras to be used in the card. Optional. If present, the first listed camera is the default. |
cameras_global |
Global defaults that apply to all cameras from the cameras section. |
card_id |
An optional ID to uniquely identify this card. For use when actions are being sent to card(s) via URL actions. Must exclusively consist of these characters: [a-zA-Z0-9_]. |
dimensions |
Configures the overall card dimensions. |
editor |
Configures the visual card editor. |
elements |
Add custom elements to the card. |
folders |
Configures folders to be used in the card. Optional. If present, the first listed folder is the default. |
image |
Configures the image view. |
live |
Configures the live view. |
media_gallery |
Configures the media gallery. |
media_viewer |
Configures the media viewer. |
menu |
Configures the card menu. |
overrides |
Override card configuration when conditions are met. |
performance |
Configures the card performance. |
profiles |
Apply pre-configured sets of defaults to ease card configuration. |
remote_control |
Configures how a card instance can be remotely controlled. |
status_bar |
Configures the card status bar. |
timeline |
Configures the timeline view. |
view |
Configures the default view and behavior of the card. |
Common configuration blocks
| Option | Description |
|---|---|
actions |
Configure actions. |
conditions |
Configure conditions. |