Files

T

Dermot Duffy 85d6811761 fix: Release the microphone to the browser when a call ends (#2685 )

The microphone is connected when a call needs it and released the moment
that
call ends, so the browser stops reporting it as in use at hangup rather
than
`disconnect_seconds` later.

Existing configurations are migrated automatically by the visual editor.

 - Closes: #2681 

BREAKING CHANGE: `live.microphone.disconnect_seconds` is removed. The
microphone is released when a call ends, so there is no idle countdown
to
configure. Use `live.microphone.always_connected` to hold it open
instead.

BREAKING CHANGE: The `microphone_connect` and `microphone_disconnect`
actions
are removed. The card owns the microphone lifecycle; `microphone_mute`
and
`microphone_unmute` remain.

BREAKING CHANGE: `call` is removed from `live.microphone.auto_mute`,
whose
default is now `[]`. The microphone is muted when a call ends regardless
of
this option.

BREAKING CHANGE: `microphone_unmute` has no effect outside a call.
Nothing
carries the audio at any other time, so the request is ignored rather
than
opening the microphone.

2026-08-14 16:17:31 -07:00

8.9 KiB

Raw Blame History

URL Actions

It is possible to pass the Advanced Camera Card one or more actions from the URL (e.g. select a particular camera, open the live view in expanded mode, etc).

When actions are executed

The Advanced Camera Card will execute these actions in the following circumstances:

On initial card load.
On 'tab' change in a dashboard.
When a navigate action is called on the dashboard (e.g. a button click requests navigation).
When the user uses the back / forward browser buttons whilst viewing a dashboard.

Instructions

To send an action to all Advanced Camera Cards on a dashboard:

[PATH_TO_YOUR_HA_DASHBOARD]?advanced-camera-card-action.[ACTION]=[VALUE]

To send an action to a specific named Advanced Camera Card:

[PATH_TO_YOUR_HA_DASHBOARD]?advanced-camera-card-action.[CARD_ID].[ACTION]=[VALUE]

Note

For backwards compatibility, the card will also respond to frigate-card-action as a query-parameter with the same syntax.

Parameter	Description
`ACTION`	One of the supported Advanced Camera Card custom actions. See Supported Actions.
`CARD_ID`	When specified only cards that have a `card_id` parameter will act.
`VALUE`	A value for actions that accept one: required by `camera_select`; optional for `substream_on` (interpreted as the `stream` to engage; omit to cycle).

Tip

Both . and : may be used as the delimiter. If you use : some browsers may require it be escaped to %3A.

Note

If a dashboard has multiple Advanced Camera Cards on it, even if they are on different 'tabs' within that dashboard, they will all respond to the actions unless the action is targeted with a CARD_ID as shown above.

Supported Actions

Only a subset of all actions are supported in URL form.

Action	Supported in URL	Explanation
`camera_select`	✅
`camera_ui`	✅
`clip`	✅
`clips`	✅
`default`	✅
`diagnostics`	✅
`download`	✖️	Latest media information is not available on initial render.
`expand`	✅
`folder`	✅
`folders`	✅
`fullscreen`	✖️	Javascript does not support activating fullscreen without direct human interaction. Use `expand` as an alternative.
`gallery`	✅
`image`	✅
`live`	✅
`media`	✅
`media_player`	✖️	Please request if you need this.
`menu_toggle`	✅
`microphone_mute`, `microphone_unmute`	✖️
`mute`, `unmute`	✖️
`play`, `pause`	✖️
`ptz`	✖️	Please request if you need this.
`recording`	✅
`recordings`	✅
`review`	✅
`reviews`	✅
`screenshot`	✖️	Latest media information is not available on initial render.
`ptz_controls`	✖️	Please request if you need this.
`snapshot`	✅
`snapshots`	✅
`substream_off`	✅	The `camera` field is not exposed via URL; the selected camera is used. Use the action config directly to target another camera.
`substream_on`	✅	Pass the substream camera ID as the URL value to engage it directly; omit the value to cycle.

Examples

See URL actions examples.

8.9 KiB Raw Blame History