[Config Support]: Home Assistant + Frigate Integration - Slow / Laggy Live Cam Stream #22753

spikar85 · 2026-04-04T00:36:12Z

spikar85
Apr 4, 2026

Describe the problem you are having

I’m running Frigate in a Proxmox LXC container (Debian) with go2rtc enabled on port 1984, and I can see all my streams there. MSE streams work perfectly and are smooth in Frigate, but WebRTC streams won’t load at all. In Home Assistant (using the Frigate integration/card), the camera feeds are very laggy and often show “waiting for live stream to load.”. Has anyone experienced this or know what I should check or change to fix WebRTC and improve streaming performance in Home Assistant?

Version

0.17.1-416a9b7

Frigate config file

example of setup for 1 x cam

go2rtc:
  streams:
    alfresco_main:
      - rtsp://redacted:redacted@192.168.1.20:554/cam/realmonitor?channel=1&subtype=0
    alfresco_live:
      - rtsp://redacted:redacted@192.168.1.20:554/cam/realmonitor?channel=1&subtype=2
    alfresco_detect:
      - rtsp://redacted:redacted@192.168.1.20:554/cam/realmonitor?channel=1&subtype=3

cameras:
  alfresco:
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/alfresco_detect
          roles:
            - detect
        - path: rtsp://127.0.0.1:8554/alfresco_main
          roles:
            - record
    detect:
      enabled: true
      width: 1280
      height: 720
      fps: 10
    live:
      streams: 
       Main Stream: alfresco_live

Relevant Frigate log output

info | 2026-04-04 00:00:01 | startup                   | Preparing Frigate...
info | 2026-04-04 00:00:01 | startup                   | Starting Frigate...
info | 2026-04-04 00:00:03 | frigate.util.config       | Checking if frigate config needs migration...
info | 2026-04-04 00:00:03 | frigate.util.config       | frigate config does not need migration...
info | 2026-04-04 00:00:03 | frigate.app               | Starting Frigate (0.17.1-416a9b7)
info | 2026-04-04 00:00:04 | peewee_migrate.logs       | Starting migrations
info | 2026-04-04 00:00:04 | peewee_migrate.logs       | There is nothing to migrate
info | 2026-04-04 00:00:04 | frigate.app               | Recording process started: 702
info | 2026-04-04 00:00:04 | frigate.app               | Review process started: 715
info | 2026-04-04 00:00:04 | frigate.app               | go2rtc process pid: 117
info | 2026-04-04 00:00:04 | frigate.app               | Embedding process started: 725
info | 2026-04-04 00:00:04 | frigate.app               | Output process started: 775
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Camera processor started for front_steps: 813
info | 2026-04-04 00:00:04 | frigate.api.fastapi_app   | Starting FastAPI app
info | 2026-04-04 00:00:04 | frigate.api.fastapi_app   | FastAPI started
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Capture process started for front_steps: 872
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Camera processor started for garage_front: 975
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Capture process started for garage_front: 1031
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Camera processor started for front_gate: 1100
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Capture process started for front_gate: 1184
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Camera processor started for backyard: 1271
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Capture process started for backyard: 1328
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Camera processor started for alfresco: 1394
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Capture process started for alfresco: 1473
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Camera processor started for garage_inside: 1541
info | 2026-04-04 00:00:04 | frigate.camera.maintainer | Capture process started for garage_inside: 1618
info | 2026-04-04 00:11:19 | frigate.comms.dispatcher  | Turning off recordings for front_steps
info | 2026-04-04 00:11:33 | frigate.comms.dispatcher  | Turning on recordings for front_steps

Relevant go2rtc log output

info | 2026-04-04 00:00:01 | startup | Preparing new go2rtc config...
info | 2026-04-04 00:00:02 | startup | Starting go2rtc...
info | 2026-04-04 00:00:02 | startup | go2rtc platform=linux/amd64 revision=df95ce3 version=1.9.10
info | 2026-04-04 00:00:02 | startup | config path=/config/go2rtc_homekit.yml
info | 2026-04-04 00:00:02 | rtsp    | listen addr=:8554
info | 2026-04-04 00:00:02 | api     | listen addr=:1984
info | 2026-04-04 00:00:02 | webrtc  | listen addr=:8555
info | 2026-04-04 00:00:11 | startup | Starting go2rtc healthcheck service...

Frigate stats

No response

Operating system

Proxmox

Install method

Docker Compose

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    cap_add:
      - CAP_PERFMON
    restart: unless-stopped
    stop_grace_period: 30s
    image: ghcr.io/blakeblackshear/frigate:stable
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card1:/dev/dri/card1
    shm_size: '800mb'   # <-- THIS fixes the SHM error
    volumes:
      - ./config:/config
      - /mnt/nvme:/media/frigate
      - type: tmpfs # 1GB In-memory filesystem for recording segment storage
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000" #HACS API
      - "8971:8971"
      - "8554:8554" # RTSP feeds
      - "1984:1984" #GO2RTC

Object Detector

OpenVino

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

Answered by inkeep-ai-assistant[bot]

Apr 4, 2026

Your WebRTC issues and laggy Home Assistant streams are likely caused by missing WebRTC configuration. WebRTC requires additional setup beyond just enabling go2rtc.

WebRTC Configuration Required

WebRTC works by creating a TCP or UDP connection on port 8555, but it requires extra configuration:(1)

1. Add WebRTC candidates to your go2rtc config:

For internal/local access, you need to set the WebRTC candidates list. If 192.168.1.10 is your Frigate host IP:(1)

go2rtc:
  streams:
    alfresco_main:
      - rtsp://redacted:redacted@192.168.1.20:554/cam/realmonitor?channel=1&subtype=0
    alfresco_live:
      - rtsp://redacted:redacted@192.168.1.20:554/cam/realmonitor?channel=1&subtype=2
    alf…

View full answer

2026-04-04T00:36:54Z

inkeep-ai-assistant[bot]
Bot Apr 4, 2026

Your WebRTC issues and laggy Home Assistant streams are likely caused by missing WebRTC configuration. WebRTC requires additional setup beyond just enabling go2rtc.

WebRTC Configuration Required

WebRTC works by creating a TCP or UDP connection on port 8555, but it requires extra configuration:(1)

1. Add WebRTC candidates to your go2rtc config:

For internal/local access, you need to set the WebRTC candidates list. If 192.168.1.10 is your Frigate host IP:(1)

go2rtc:
  streams:
    alfresco_main:
      - rtsp://redacted:redacted@192.168.1.20:554/cam/realmonitor?channel=1&subtype=0
    alfresco_live:
      - rtsp://redacted:redacted@192.168.1.20:554/cam/realmonitor?channel=1&subtype=2
    alfresco_detect:
      - rtsp://redacted:redacted@192.168.1.20:554/cam/realmonitor?channel=1&subtype=3
  webrtc:
    candidates:
      - 192.168.1.10:8555
      - stun:8555

(1)

2. Expose port 8555 in Docker:

Your docker-compose is missing the WebRTC port. Add these lines to your ports section:(1)

ports:
  - "5000:5000"
  - "8971:8971"
  - "8554:8554"
  - "1984:1984"
  - "8555:8555/tcp"
  - "8555:8555/udp"

(1)

Home Assistant RTSP Access

For live streams to function in Home Assistant, they need to be accessible on the RTSP port (default: 8554) at <frigatehost>:8554. Home Assistant will directly connect to that streaming port when the live camera is viewed.(2)

Camera Settings Recommendations

For the best live view experience, adjust these settings in your camera's firmware:(1)

Video codec: H.264 (avoid "smart codec" or "+" variants like H.264+ or H.265+ as these remove keyframes)(1)
Audio codec: AAC(1)
I-frame interval: Match your camera's frame rate, or choose "1x". If your stream outputs 20fps, your i-frame interval should be 20.(1)

Audio Transcoding

If MSE works but WebRTC doesn't, you may need to transcode audio to opus for WebRTC support. MSE requires PCMA/PCMU or AAC audio, while WebRTC requires PCMA/PCMU or opus audio:(1)

go2rtc:
  streams:
    alfresco_live:
      - rtsp://redacted:redacted@192.168.1.20:554/cam/realmonitor?channel=1&subtype=2
      - "ffmpeg:alfresco_live#audio=opus"

(1)

After making these changes, restart Frigate and test WebRTC again in the go2rtc web interface at port 1984.

📚 Sources:

Have another question? Just tag @inkeep.

0 replies

spikar85 · 2026-04-04T00:49:41Z

spikar85
Apr 4, 2026
Author

Thanks BOT! :)

I also added live_provider to my card to force choice of stream.

`type: vertical-stack
cards:

type: custom:advanced-camera-card
cameras:
- camera_entity: camera.alfresco
  live_provider: go2rtc
  go2rtc:
  stream: alfresco_live`

0 replies

contactpb · 2026-04-04T01:42:01Z

contactpb
Apr 4, 2026

It might also be worth looking at the 'Use Frigate-native WebRTC support' setting in HA Settings -> Devices + Services -> Frigate -> Options. I was struggling with similar problems yesterday (intermittent/lagging/no video) trying to get live views working with the Picture Entity card and enabling this resolved all issues for me. I think it's documented here: https://docs.frigate.video/configuration/live/

0 replies

Navigation Menu

Uh oh!

[Config Support]: Home Assistant + Frigate Integration - Slow / Laggy Live Cam Stream #22753

Uh oh!

{{title}}

Uh oh!

Replies: 3 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

[Config Support]: Home Assistant + Frigate Integration - Slow / Laggy Live Cam Stream #22753

Uh oh!

spikar85 Apr 4, 2026

Describe the problem you are having

Version

Frigate config file

Relevant Frigate log output

Relevant go2rtc log output

Frigate stats

Operating system

Install method

docker-compose file or Docker CLI command

Object Detector

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

WebRTC Configuration Required

Replies: 3 comments

Uh oh!

inkeep-ai-assistant[bot] Bot Apr 4, 2026

WebRTC Configuration Required

Home Assistant RTSP Access

Camera Settings Recommendations

Audio Transcoding

Uh oh!

spikar85 Apr 4, 2026 Author

Uh oh!

contactpb Apr 4, 2026

spikar85
Apr 4, 2026

inkeep-ai-assistant[bot]
Bot Apr 4, 2026

spikar85
Apr 4, 2026
Author

contactpb
Apr 4, 2026