[Camera Support]: Camera intities are not created after the installation of Frigate #19008
-
Describe the problem you are havingThe camera entities are not created after the installation of Frigate NVR. The camera is visible and works in Frigate, but I would like to integrate it in a HA dashboard. During startup of Frigate I get the following error: 2025-07-06 18:12:30.742177213 2025/07/06 20:12:30 [error] 180#180: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000" Version0.15.0-6cb5cfb What browser(s) are you using?Google Chrome Version 137.0.7151.122 Frigate config filemqtt:
enabled: true
host: 192.168.X.XXX
port: 1883
user: mqtt_username
password: mqtt_password
topic_prefix: frigate
cameras:
Camera1: # <------ Name the camera
enabled: true
ffmpeg:
inputs:
- path: rtsp://rtsp_username:[email protected]:554/rtsp # <----- The stream you want to use for detection
roles:
- detect
detect:
enabled: false # <---- disable detection until you have a working camera feed
zones:
Voortuin:
coordinates: 0,0.709,0.492,0.783,0.441,0.986,0,1
loitering_time: 0
Straat:
coordinates: 0,0.472,0,0.688,1,0.811,1,0.496
loitering_time: 0
version: 0.15-1Relevant Frigate log outputs6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service certsync-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
2025-07-06 18:12:25.997983704 [INFO] Preparing new go2rtc config...
2025-07-06 18:12:25.999944533 [INFO] Preparing Frigate...
s6-rc: info: service nginx: starting
2025-07-06 18:12:26.022922562 [INFO] Starting NGINX...
2025-07-06 18:12:26.053762830 [INFO] Got IP address from supervisor: 192.168.1.52
2025-07-06 18:12:26.095994545 [INFO] Got WebRTC port from supervisor: 8555
2025-07-06 18:12:26.110176950 [INFO] No TLS certificate found. Generating a self signed certificate...
2025-07-06 18:12:26.185305987 [INFO] Starting Frigate...
2025-07-06 18:12:27.022510651 [INFO] Starting go2rtc...
2025-07-06 18:12:27.196633483 20:12:27.196 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-07-06 18:12:27.197256915 20:12:27.196 INF config path=/dev/shm/go2rtc.yaml
2025-07-06 18:12:27.199068568 20:12:27.198 INF [api] listen addr=:1984
2025-07-06 18:12:27.199958567 20:12:27.199 INF [rtsp] listen addr=:8554
2025-07-06 18:12:27.200652176 20:12:27.200 INF [webrtc] listen addr=:8555/tcp
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
2025-07-06 18:12:29.293196774 [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2025-07-06 18:12:29.413302496 127.0.0.1 - - [06/Jul/2025:20:12:29 +0200] "" 400 0 "-" "-" "-"
2025-07-06 18:12:29.891396417 2025/07/06 20:12:29 [error] 179#179: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "192.168.X.XXX:8123"
2025-07-06 18:12:29.891812907 2025/07/06 20:12:29 [error] 179#179: *2 auth request unexpected status: 502 while sending to client, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", host: "192.168.X.XXX:8123"
2025-07-06 18:12:29.892154408 172.30.32.2 - - [06/Jul/2025:20:12:29 +0200] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36" "192.168.1.1, 172.30.32.1"
2025-07-06 18:12:30.699032481 [2025-07-06 20:12:30] frigate.util.config INFO : Checking if frigate config needs migration...
2025-07-06 18:12:30.707434318 [2025-07-06 20:12:30] frigate.util.config INFO : frigate config does not need migration...
2025-07-06 18:12:30.742177213 2025/07/06 20:12:30 [error] 180#180: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2025-07-06 18:12:30.742638536 2025/07/06 20:12:30 [error] 180#180: *4 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2025-07-06 18:12:30.771380915 [2025-07-06 20:12:30] frigate.util.services WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2025-07-06 18:12:31.901165320 [2025-07-06 20:12:31] frigate.app INFO : Starting Frigate (0.15.0-6cb5cfb)
2025-07-06 18:12:31.902439219 [2025-07-06 20:12:31] frigate.app INFO : Creating directory: /tmp/cache
2025-07-06 18:12:31.906881687 [2025-07-06 20:12:31] peewee_migrate.logs INFO : Starting migrations
2025-07-06 18:12:31.915781250 [2025-07-06 20:12:31] peewee_migrate.logs INFO : There is nothing to migrate
2025-07-06 18:12:31.915784541 [2025-07-06 20:12:31] frigate.app INFO : Recording process started: 294
2025-07-06 18:12:31.921598781 [2025-07-06 20:12:31] frigate.app INFO : Review process started: 296
2025-07-06 18:12:31.925836072 [2025-07-06 20:12:31] frigate.app INFO : go2rtc process pid: 102
2025-07-06 18:12:31.943367858 [2025-07-06 20:12:31] detector.cpu INFO : Starting detection process: 307
2025-07-06 18:12:31.947626589 [2025-07-06 20:12:31] frigate.detectors WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2025-07-06 18:12:31.966610186 [2025-07-06 20:12:31] frigate.app INFO : Output process started: 326
2025-07-06 18:12:32.006896182 [2025-07-06 20:12:31] frigate.app INFO : Camera processor started for Niko_ODS: 347
2025-07-06 18:12:32.017711745 [2025-07-06 20:12:32] frigate.app INFO : Capture process started for Niko_ODS: 356
2025-07-06 18:12:34.141672838 [2025-07-06 20:12:34] frigate.api.fastapi_app INFO : Starting FastAPI app
2025-07-06 18:12:34.346369779 [2025-07-06 20:12:34] frigate.api.fastapi_app INFO : FastAPI started
2025-07-06 18:12:36.003213135 [INFO] Starting go2rtc healthcheck service...Relevant go2rtc log outputNot sure how to do this?FFprobe output from your cameraNot sure how to do this?Frigate statsNo response Operating systemProxmox Install methodHome Assistant Add-on Object DetectorCPU (no coral) Network connectionWired Camera make and modelNiko 510-01001 Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 12 replies
-
|
Did you install the Frigate Home Assistant Integration? This is separate from Frigate itself. As for the errors you're seeing in the log, see the FAQ, Usage question 4. |
Beta Was this translation helpful? Give feedback.
-
|
Are you using HACS? |
Beta Was this translation helpful? Give feedback.
-
|
Yes |
Beta Was this translation helpful? Give feedback.
-
|
See the integration's installation instructions when you use HACS: https://github.com/blakeblackshear/frigate-hass-integration?tab=readme-ov-file#installation |
Beta Was this translation helpful? Give feedback.
-
|
I reinstalled the hacs component and now it appears in the integration list. Thanks for your support! |
Beta Was this translation helpful? Give feedback.
-
|
Great, glad it's working for you. |
Beta Was this translation helpful? Give feedback.
Did you install the Frigate Home Assistant Integration? This is separate from Frigate itself.
As for the errors you're seeing in the log, see the FAQ, Usage question 4.