Frigate container running on Home Assistant doesn't have access to LAN IPs

[mb02155]

Describe the problem you are having

I installed the Frigate add-on on a new install of Home Assistant and was not able to access any camera (tried multiple brands).

2024-07-25 05:54:34.455976599 [2024-07-24 22:54:34] frigate.video ERROR : driveway: Unable to read frames from ffmpeg process.
2024-07-25 05:54:34.456180316 [2024-07-24 22:54:34] frigate.video ERROR : driveway: ffmpeg process is not running. exiting capture thread...
2024-07-25 05:54:49.452285720 [2024-07-24 22:54:49] watchdog.driveway ERROR : Ffmpeg process crashed unexpectedly for driveway.

I decided to connect interactively to the frigate docker container running on HA (docker exec -it /bin/bash) and found that (after installing ping) I was not able to ping any IPs for the cameras or anything else on my LAN. I also tried a frame capture using ffmpeg (ffmpeg -loglevel debug -y -rtsp_transport tcp -i rtsp://uname:[email protected]:554/cam/realmonitor?channel=1&subtype=0 -vframes 1 testframe3.jpg) and was unable to capture a frame since it also was not able to connect to the camera.

Please let me know what I need to do to resolve this.

Thank you!

Steps to reproduce

Install HAssOS
Install Frigate add-on
Create frigate.yaml file
start frigate

Version

0.13.2-6476f8a / go2rtc 1.8.4

Frigate config file

mqtt:
    host: 192.168.1.5
    port: 1883
    user: mqttuser
    password: password1!
    enabled: false
    
detectors:
  coral:
    type: edgetpu
    device: usb

logger:
  default: info
  
        
go2rtc:
  log:
    format: text
    level: "debug"
  streams:
    driveway: 
      - rtsp://uname:[email protected]:554/cam/realmonitor?channel=1&subtype=2          
      - "ffmpeg:driveway#video=h264"
        
cameras:
  driveway: 
    enabled: True
    ffmpeg:
      hwaccel_args: preset-intel-vaapi
      inputs:
        - path: rtsp://uname:[email protected]:554/cam/realmonitor?channel=1&subtype=2
          input_args: preset-rtsp-restream
          roles:
            - detect

    detect:
      enabled: False # <---- disable detection until you have a working camera feed

Relevant log output

2024-07-25 05:54:59.466156170  [2024-07-24 22:54:59] ffmpeg.driveway.detect         ERROR   : [tcp @ 0x561a074f0e80] Connection to tcp://192.168.1.96:554?timeout=5000000 failed: Connection timed out
2024-07-25 05:54:59.466167018  [2024-07-24 22:54:59] ffmpeg.driveway.detect         ERROR   : rtsp://*:*@192.168.1.96:554/cam/realmonitor?channel=1&subtype=2: Connection timed out
2024-07-25 05:55:04.494767206  [2024-07-24 22:55:04] frigate.video                  ERROR   : driveway: Unable to read frames from ffmpeg process.
2024-07-25 05:55:04.494931474  [2024-07-24 22:55:04] frigate.video                  ERROR   : driveway: ffmpeg process is not running. exiting capture thread...
2024-07-25 05:55:09.479666723  [2024-07-24 22:55:09] watchdog.driveway              ERROR   : Ffmpeg process crashed unexpectedly for driveway.
2024-07-25 05:55:09.480332763  [2024-07-24 22:55:09] watchdog.driveway              ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-07-25 05:55:09.480635254  [2024-07-24 22:55:09] ffmpeg.driveway.detect         ERROR   : [tcp @ 0x55f7b9f9be80] Connection to tcp://192.168.1.96:554?timeout=5000000 failed: Connection timed out
2024-07-25 05:55:09.481178506  [2024-07-24 22:55:09] ffmpeg.driveway.detect         ERROR   : rtsp://*:*@192.168.1.96:554/cam/realmonitor?channel=1&subtype=2: Connection timed out
2024-07-25 05:55:14.502628012  [2024-07-24 22:55:14] frigate.video                  ERROR   : driveway: Unable to read frames from ffmpeg process.
2024-07-25 05:55:14.502798916  [2024-07-24 22:55:14] frigate.video                  ERROR   : driveway: ffmpeg process is not running. exiting capture thread...
2024-07-25 05:55:19.489571952  [2024-07-24 22:55:19] watchdog.driveway              ERROR   : Ffmpeg process crashed unexpectedly for driveway.

Operating system

HassOS

Install method

HassOS Addon

Network connection

Wired

Camera make and model

Tried amcrest and ubiquiti

Any other information that may be helpful

No response

[NickM-27]

Sounds like a network configuration issue, there's no reason this shouldn't work out of the box

[NickM-27]

Could still be a problem with how HA supervisor is controlling the addon. Unfortunately since that is the case you don't have much control over the addon. Otherwise I'd suggest configuring it to use host networking mode instead of bridge.

I don't have much experience with HA OS as I have HA, frigate, etc installed as docker containers.

[mb02155]

Thanks for the response.

How would I go about configuring the Frigate container to use host networking mode instead of bridge?

[NickM-27]

You can't when it is running as an addon

[mb02155]

I am open to running everything (Home Assistant, frigate, rtlamr2mqtt,mosquito & zigbee2mqtt) as individual docker containers if that will resolve the issue. What base OS would you suggest for this? Also, what is the best way to automatically start docker containers at boot?

Also, I did find posts elsewhere that others are having the same issue. Is there a way to work with HA team to allow plug-ins to use host networking?

Thanks!

[NickM-27]

Generally Debian is recommended in the docs. You just set the docker compose restart mode so it restarts on startup.

I don't know, I am not aware of HA stance on this