[Config Support]: HassOS can't connect to the camera on the same network as frigate

[jrusi]

Describe the problem you are having

Frigate is installed in HassOS as add-on and when starting I can see it is using correct network:
2024-09-22 13:06:27.048215135 [INFO] Got IP address from supervisor: 192.168.100.166
The camera is configured as follows:
cameras: BalkonPTZ: # <------ Name the camera enabled: true ffmpeg: inputs: - path: rtsp://user:[email protected]:554/Streaming/Channels/101 roles: - detect detect: enabled: false # <---- disable detection until you have a working camera feed width: 1280 height: 720 version: 0.14
I have a laptop in the same network (192.168.100.0) and I can view the rtsp stream using the url above.

But in Frigate I get "no frames has been received"

[tcp @ 0x55857bef00] Connection to tcp://192.168.100.105:554?timeout=5000000 failed: No route to host

There is no firewall in the middle, no VLANs etc. I can ping the camera from my laptop.

What could be the reason?

Version

0.14.1

Frigate config file

mqtt:
  enabled: false


cameras:
  BalkonPTZ: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://user:[email protected]:554/Streaming/Channels/101
          roles:
            - detect
    detect:
      enabled: false # <---- disable detection until you have a working camera feed
      width: 1280
      height: 720
version: 0.14

Relevant Frigate log output

2024-09-22 13:09:45.725626125  [2024-09-22 15:09:45] ffmpeg.BalkonPTZ.detect        ERROR   : [tcp @ 0x55afe75f00] Connection to tcp://192.168.100.105:554?timeout=5000000 failed: No route to host
2024-09-22 13:09:45.726362733  [2024-09-22 15:09:45] ffmpeg.BalkonPTZ.detect        ERROR   : rtsp://*:*@192.168.100.105:554/Streaming/Channels/101: No route to host
2024-09-22 13:09:49.114957748  [2024-09-22 15:09:49] frigate.video                  ERROR   : BalkonPTZ: Unable to read frames from ffmpeg process.
2024-09-22 13:09:49.115766839  [2024-09-22 15:09:49] frigate.video                  ERROR   : BalkonPTZ: ffmpeg process is not running. exiting capture thread...

Relevant go2rtc log output

2024-09-22 13:06:26.899528242  [INFO] Preparing new go2rtc config...
2024-09-22 13:06:27.048215135  [INFO] Got IP address from supervisor: 192.168.100.166
2024-09-22 13:06:27.188023112  [INFO] Got WebRTC port from supervisor: 8555
2024-09-22 13:06:28.546074315  [INFO] Starting go2rtc...
2024-09-22 13:06:28.781013535  15:06:28.779 INF go2rtc platform=linux/arm64 revision=b2399f3 version=1.9.2
2024-09-22 13:06:28.781030035  15:06:28.779 INF config path=/dev/shm/go2rtc.yaml
2024-09-22 13:06:28.789607120  15:06:28.785 INF [rtsp] listen addr=:8554
2024-09-22 13:06:28.789619305  15:06:28.786 INF [api] listen addr=:1984
2024-09-22 13:06:28.789621861  15:06:28.786 INF [webrtc] listen addr=:8555/tcp
2024-09-22 13:06:36.586245105  [INFO] Starting go2rtc healthcheck service...

Frigate stats

No response

Operating system

HassOS

Install method

HassOS Addon

Object Detector

CPU (no coral)

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[NickM-27]

is the laptop acting as the router? that is an odd ip address for a client device to have. Seems there is something in the network that means HA OS can't communicate with the camera

[jrusi]

Hi,
No it is not.
There is a router (AP) in the network running DHCP server with a pool from: 192.168.100.0/24
HA is getting the ip from DHCP (192.168.100.166) (LAN)
Camera is getting the ip from the same DHCP (192.168.100.105) (WIFI)
Laptop is getting the ip from the same DHCP (192.168.100.178) (WIFI)
So we have 1 AP/router and 3 clients connected to the same network.

[jrusi]

Same issue here: #12602