Frigate Streams Broken After 2024.11

Configuration
21

I don’t know about recordings, I use the Frigate interface for reviewing recordings.

22

Just to be clear, the 5.5.1 update to the frigate integration, along with enabling the Use Webrtc option in it, does not fix the problem people are reporting, namely that you cannot play back recordings.

23

It works for me in 24.12.0b3 (beta), ymmv

24

WebRTC will only work if configured & activated in Frigate.

25

Can confirm. Updating to the beta fixed it for me.

1 Like
26

So the issue is with HA and not the integration? Im running 2024.11.3 and typically dont update to betas but this is broken for me as well. I dont expose frigates frontend to the web but expose it through HA via the integration and media browser which has been working up until recently. I figured it was an integration and frigate issue and not HA borking things up.

27

Yes, if you don’t want to use the beta, 24.12.0 is 2 days away afik.

28

I can confirm, problem is fixed in 2024.12.0

29

How did you fix the problem? I upgraded to 2024.12.0 and still have the issue.

30

Did you also update the Frigate integration ? (either via Hacs or manually in custom_components )

31

When you say you still have the issue, do you mean via a notificaiton play? or via the Media browser.

32

Updating to 2024.12.0 fixed both problems for me, notification clip play and media library play.
Did you try to clear cache?

33

What device? Android / iPhone

34

Browser on linux and android and android app.

35

I can confirm that December update fixed it for me. Both live stream and recorded clips are working again.

36

The situation is weird on mine.

Sometimes all video streams work sometimes but sometimes 1 of 4 streams fails.

Sometimes the problematic camera entity reports unavailable but the video stream is working fine.

HA Core version 2024.12.1
Frigate integration version 5.5.1
Frigate version 0.14.1-f4f3cfa

37

image

This is all I get with 5fps. WebRTC isnt working even though its enabled. It works fine with Frigate UI. I setup the frigate config per the doc with:

  webrtc:
    candidates:
      - 172.20.3.50:8555
      - stun:8555
38

What is this “stun:8555” . Does this stun resolve to an IP address?

I have just something like yours:

 webrtc:
    candidates:
      - 172.20.3.50:8555

and it works for me.

I did have to configure docker (running frigate inside) to pass on port 8555.
relevant part of docker-compose:

    ports:
      - "8971:8971" # Authenticated UI and API access without TLS.
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
39

I followed the instructions here

I removed the stun line and restarted. Still no go.

40

This is specifically for the live view on the home assistant integration for Frigate.