Files
advanced-camera-card/docs/configuration
Dermot Duffy 11cc543406 fix: Hold the 2-way audio backchannel open for the shortest possible time (#2697)
The card claimed a camera's ONVIF audio backchannel in two places that
had
nothing to do with a call: the capability probe at camera init
(`&microphone`),
and a pre-armed `sendonly` audio transceiver on every live WebRTC offer.
Merely
looking at a dashboard occupied the camera's speaker line. Outbound
audio now
travels on its own audio-only WebRTC connection, opened when a call is
answered
and closed when it ends.

- The backchannel is claimed only for the duration of a call. Idle
viewing
  claims nothing.
- Two-way audio now works in `mse`, `mp4` and `mjpeg` modes (note: the
outbound
  audio still traverses WebRTC).
- No renegotiation and no video blink at call start or end.
- A call that cannot carry audio now reports it and ends, instead of
showing a
  live microphone that goes nowhere.
- `live.microphone.always_connected` is now purely about the browser
microphone
  permission prompt.
- Call setup measured at 66ms (LAN) and ~260ms (cellular) for ICE and
DTLS, plus
  ~300ms for `go2rtc` to open an RTSP backchannel.

Verified against a live Frigate + `go2rtc` instance, and by unit tests
at 100%
coverage.

 - Closes #2691
 - Closes #2039
 - Closes #2178

Ref #2299 -- the probe no longer opens a backchannel, but it still runs
per
camera on every load and reconnect, and still dials the camera on the
direct-`go2rtc` path. Caching remains to be done.

Ref AlexxIT/go2rtc#1860 -- once a call has opened a backchannel,
`go2rtc` keeps
that media set up on the camera's RTSP session for the life of the
producer.

Diagnoses #2678
2026-08-21 20:13:58 -07:00
..

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.