[support ?] HA+lovelace card : livestream stops/fails after a few seconds

[Karmak23]

Sorry if this is a misconfiguration issue but it drives me nuts.

Description of the issue

When loading any HA page in firefox containing a frigate-card, the live stream cards show immediately, video goes on as expected (with v0.12 the reactivity blows my mind).

But after a fixed number of seconds (sooner for the birdseye [8secs] that for the other cards [~13 secs]), all frigate-card streams fail with this error :

Failed to receive response from Home Assistant for request.[ Check troubleshooting](https://github.com/dermotduffy/frigate-hass-card#troubleshooting).

{
  "request": {
    "type": "media_source/browse_media",
    "media_content_id": "media-source:https://frigate/frigate/event-search/clips////birdseye//",
    "id": 37
  },
  "response": {
    "code": "unknown_error",
    "message": "Unknown error"
  }
}

The other card fails the same way, which makes me think it’s a configuration issue:

Failed to receive response from Home Assistant for request.[ Check troubleshooting](https://github.com/dermotduffy/frigate-hass-card#troubleshooting).

{
  "request": {
    "type": "media_source/browse_media",
    "media_content_id": "media-source:https://frigate/frigate/event-search/clips////Jardin//",
    "id": 87
  },
  "response": {
    "code": "unknown_error",
    "message": "Unknown error"
  }
}

I’ve read the troubleshooting section, but didn't find anything related to this.

Context / configuration

• frigate 0.12 (latest, pulled yesterday) docker-compose install. (but the problem occurs since 0.10)
• HA 20230404 supervised install, everything up-to-date.
• frigate hass integration 4.0.0 (problem occurs since before 3.0.0)

In HA lovelace, the failing birdseye card :

type: custom:frigate-card
cameras:
  - frigate:
      camera_name: birdseye
menu:
  style: overlay
  buttons:
    cameras:
      enabled: false
    live:
      enabled: false
    clips:
      enabled: false
    snapshots:
      enabled: false
    download:
      enabled: false
    frigate_ui:
      enabled: false
    timeline:
      enabled: false
    media_player:
      enabled: false
    frigate:
      enabled: false
  position: right
live:
  preload: true
  draggable: false
view_layout:
  column: 2

But any simple card like this one also exhibits the issue :

type: custom:frigate-card
cameras:
  - camera_entity: camera.jardin
    live_provider: webrtc-card
    webrtc_card:
      entity: camera.jardin
live:
  webrtc_card:
    ui: true

Note: any "non-hass" stream card does not have the problem:

type: vertical-stack
cards:
  - show_state: true
    show_name: true
    camera_view: live
    type: picture-entity
    entity: camera.atelierexterieur
  - type: horizontal-stack
    cards:
      - type: entities
        entities:
          - entity: switch.atelierexterieur_detect
            name: Détection
      - type: entities
        entities:
          - entity: button.atelier_exterieur_reboot
            name: Reboot

This card streams for hours and never fails.

Question

I{m pretty sure this is a configuration issue, but i’m stuck. How to debug the problem ? Where to search ? What can I provide to narrow it down ? Thanks for your time.

[NickM-27]

I'd suggest using to v5 if the frigate card and using go2rtc live provider instead

[NickM-27]

It's a beta so you need to enable beta releases for the frigate card in HACS

[Karmak23]

The crash is fixed with v5.0.0-beta1 without any configuration change, but the "not-birdseye" card shows fixed images (eg 1 per second) at the detect resolution, while my frigate config.yml is [partially shown] in this other thread.

Anyway, thanks for the pointer, the crash is gone.

Also, this could lead to a new thread, but while I’ve got port 1934 open in docker-compose.yml, installing the WebRTC Camera integration in HA can't reach the go2rtc server at http:https://127.0.0.1:1934/ . I will try to hunt in the logfile before asking for help again.

[Karmak23]

The low resolution is fixed with use of live_provider: ha (default was jsmpeg, don’t know why…).
Still not happy because no webrtc, but I will dig into logs ASAP.
Thanks again.

[NickM-27]

You should be using the go2rtc provider

[Karmak23]

You should be using the go2rtc provider

Yeah I know but can’t achieve to install it because of the port 1934 issue. The HA integration cannot connect while everything seems fine on the frigate docker container side.

[Karmak23]

Original problem is solved, marking the discussion as such. Thanks @NickM-27 !