advanced-camera-card/README.md

Frigate Lovelace Card

A full-featured Frigate Lovelace card:

• Live viewing.
• Clips and snapshot browsing via mini-gallery.
• Automatic updating to continually show latest clip / snapshot.
• Support for filtering events by zone and label.
• Arbitrary entity access via menu (e.g. motion sensor access).
• Full Lovelace editing support.
• Theme friendly.
• Advanced: Support for WebRTC live viewing.

Installation

• Use HACS to install the card:

Home Assistant > HACS > Frontend > "Explore & Add Integrations" > Frigate Card

• Add the following to configuration.yaml:

lovelace:
  resources:
    - url: /hacsfiles/frigate-hass-card/frigate-hass-card.js
      type: module

• Restart Home Assistant.
• Add the new card to the Lovelace configuration!

Options

Required

Option	Default	Description
camera_entity		The Frigate camera entity to use in the live camera view.

Optional

Option	Default	Description
frigate_camera_name	The string after the "camera." in the camera_entity option (above).	This parameter allows the camera name heuristic to be overriden for cases where the entity name does not cleanly map to the Frigate camera name (e.g. when the Frigate camera name is capitalized, but the entity name is lower case). This camera name is used for communicating with the Frigate backend, e.g. for fetching events.
view_default	live	The view to show by default. See views below.
frigate_client_id	frigate	The Frigate client id to use. If this Home Assistant server has multiple Frigate server backends configured, this selects which server should be used. It should be set to the MQTT client id configured for this server, see Frigate Integration Multiple Instance Support.
view_timeout		A numbers of seconds of inactivity after which the card will reset to the default configured view. Inactivity is defined as lack of interaction with the Frigate menu.
frigate_url		The URL of the frigate server. If set, this value will be (exclusively) used for a Frigate UI menu button.
autoplay_clip	false	Whether or not to autoplay clips in the 'clip' view. Clips manually chosen in the clips gallery will still autoplay.

Appearance

Option	Default	Description
menu_mode	hidden-top	The menu mode to show by default. See menu modes below.
menu_buttons.{frigate, live, clips, snapshots, frigate_ui}	true	Whether or not to show these builtin actions in the card menu.

Advanced

Option	Default	Description
label		A label used to filter events (clips & snapshots), e.g. 'person'.
zone		A zone used to filter events (clips & snapshots), e.g. 'front_door'.

WebRTC Options

WebRTC support blends the use of the ultra-realtime WebRTC live view with convenient access to Frigate events/snapshots/UI. A perfect combination!

Option	Default	Description
live_provider		Whether frigate or webrtc should provide the live camera view.
webrtc.entity		The RTSP entity to use with WebRTC.
webrtc.*		Any other options in a webrtc: YAML dictionary are silently passed through to WebRTC. See WebRTC Configuration for full details this external card provides.

Note: WebRTC must be installed and configured separately (see details) before it can be used with this card.

Entities

Additional entities may be configured to trigger updates to the card, and optionally to appear in the menu. An entities section may be added to the card configuration containing a list with entries of the following format:

Option	Default	Description
entity		Entity ID to use to trigger updates, and optionally appear in the menu.
icon	[default entity icon]	An optional manual override of the icon to use in the menu, e.g. mdi:car.
show	true	Whether or not to show the entity in the menu. When false the entity ID will trigger card updates only, but not appear in the menu.

Example

This example allows access to the detection, recordings and snapshots switches from the menu. It also enables a different entity to trigger a card update (but without appearing in the menu).

entities:
  - entity: switch.front_door_recordings
  - entity: switch.front_door_snapshots
  - entity: switch.front_door_detect
  - entity: binary_sensor.front_door_person_motion
    show: false

Specifying the WebRTC Camera

There are two ways to specify the WebRTC source camera:

• Manual setup of separate RTSP camera entities in Home Assistant. These entities will then be available for selection in the GUI card editor for the Frigate card under the WebRTC options, or can be manually specified with a webrtc.entity option in YAML:

[rest of Frigate card configuration]
webrtc:
  entity: 'camera.front_door_rstp`

• OR manually configuring the url parameter as part of a manual Frigate card configuration, like the following example:

[rest of Frigate card configuration]
webrtc:
  url: 'rtsp://USERNAME:PASSWORD@CAMERA:554/RTSP_PATH'

See WebRTC configuration for full configuration options.

Views

This card supports several different views.

Key	Description
live (default)	Shows the live camera view, either the name Frigate view or WebRTC if configured.
snapshots	Shows the snapshot gallery for this camera/zone/label.
snapshot	Shows the most recent snapshot for this camera/zone/label.
clips	Shows the clip gallery for this camera/zone/label.
clip	Shows the most recent clip for this camera/zone/label.

Automatic updates in the clip or snapshot view

Updates will occur whenever on every change of the state of the camera_entity or any entity configured under entities. In particular, if the desire is to have an auto-refreshing view of the most recent event, the camera_entity will not be sufficient alone since the Home Assistant state for Frigate camera entities does not change often. Instead, use the Frigate binary_sensor for that camera (or any other entity at your discretion) to trigger the update:

entities:
  - entity: binary_sensor.office_person_motion

See entities above.

Getting from a snapshot to a clip

Clicking on a snapshot will take the user to a clip that was taken at the ~same time as the snapshot (if any).

Getting event details

More details about an event can be found by clicking the 'globe' icon in the menu, which takes the user to the Frigate page for that event.

Menu Modes

This card supports several menu configurations.

Key	Description	Screenshot
hidden-{top,bottom,right,left} (default)	Hide the menu by default, expandable upon clicking the 'F' button.
overlay-{top,bottom,right,left}	Overlay the menu on top of the card contents. The 'F' button shows the default view.
above	Render the menu above the card. The 'F' button shows the default view.
below	Render the menu below the card. The 'F' button shows the default view.

Example YAML Configuration

A configuration that uses WebRTC for live:

- type: 'custom:frigate-card'
  camera_entity: camera.front_door
  frigate_url: http://frigate
  live_provider: webrtc
  webrtc:
    entity: camera.front_door_rtsp

A configuration that shows the latest clip on load, but does not automatically play it:

- type: 'custom:frigate-card'
  camera_entity: camera.front_door
  frigate_url: http://frigate
  view_default: clip

Screenshot: Snapshot / Clip Gallery

Full viewing of clips:

Card Editing

This card supports full editing via the Lovelace card editor. Additional arbitrary configuration for WebRTC may be specified in YAML mode.

Troubleshooting

Failed to fetch

Note: This error should no longer be possible >= v0.1.5 .

Failed to fetch is a generic error indicating your browser (and this card) could not communicate with the Frigate server specified in the card configuration. This could be for any number of reasons (e.g. incorrect URL, incorrect port, broken DNS, etc).

If the 'globe' icon in the menu bar of the card also doesn't open the Frigate UI, the address entered is probably incorrect/inaccessible.

Mixed content

Note: This error should no longer be possible >= v0.1.5 .

If you are accessing your Home Assistant instance over https, you will likely receive this error unless you have configured the card to also communicate with Frigate via https (e.g. via a reverse proxy). This is because the browser is blocking the attempt to mix access to both https and http resources.

The javascript console (how to access) will show an error such as:

Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an 
insecure resource '<URL>'. This request has been blocked; the content must be
served over HTTPS.

Accessing both Home Assistant and Frigate over https will likely resolve this issue (e.g. through the use of a reverse proxy in front of Frigate).