Hi there,
I have running HA Core newest Version with HACS also newest Version on a I3 PC with debian 12.
I want to integrate Frigate for Cameras, installed with HACS…
When i want to add the Intergration this screen comes up and i can’t get any connection and so i cant do anything else.
Can i change the port? And if so, where?
Do i have to open Port 5000 Forwarding in my FritzBox?
Need some help to get this going please.
where is frigate running? this is only the integration
Hu? What does this mean, only the Integration?
I understood it is installed with hacs?
Just ask Google:
Is Frigate an addon or integration?
Frigate is a Docker container that can be run on any Docker host including as a HassOS Addon. Note that a Home Assistant Addon is not the same thing as the integration. The integration is required to integrate Frigate into Home Assistant.
So as i have no docker, how do i have to install this on HA Core?
the integration is installed with HACS, but frigate itself needs to be installed in docker or via the addon. This is covered in the docs Installation | Frigate
Frigate is a Docker container that can be run on any Docker host including as a HassOS Addon. Note that a Home Assistant Addon is not the same thing as the integration. The integration is required to integrate Frigate into Home Assistant.
you install docker
no other way to install it directly on my linux?
well, as i have cockpit running on my system i now have installed Podman-Cockpit.
Seems to be as Docker-Cockpit is old and was replaced by podman.
But I never did anything with Docker/Podman Images…
Can someone help me to install this container in Cockpit?
Its looking like this:
i am a step further:
I installed docker and could install the frigate.
docker ps -a shows:
root@I3-Server:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d22238b77468 ghcr.io/blakeblackshear/frigate:stable "/init" 27 hours ago Up 17 hours 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp, 1935/tcp, 0.0.0.0:8554-8555->8554-8555/tcp, :::8554-8555->8554-8555/tcp, 0.0.0.0:8555->8555/udp, :::8555->8555/udp frigate
so it seems to be running.
When i try to call the frigate webpage i only get this:
If i call the integration i still get the “no connection” error.
a simple frigate.yaml is included in the folder where configuration.yaml also is.
mqtt:
enabled: False
cameras:
name_of_your_camera: Vorne
ffmpeg:
inputs:
- path: rtsp://192.168.2.111:16383/stream1
roles:
- detect
detect:
enabled: False # <---- disable detection until you have a working camera >
width: 1280 # <---- update for your camera's resolution
height: 720 # <---- update for your camera's resolution
Any ideas how to get this running?
look at docker logs frigate and see what it says
2023-09-29 00:15:07.219791646 [INFO] Preparing go2rtc config...
Traceback (most recent call last):
File "/usr/local/go2rtc/create_config.py", line 23, in <module>
with open(config_file) as f:
IsADirectoryError: [Errno 21] Is a directory: '/config/config.yml'
2023-09-29 00:15:07.449277274 [INFO] The go2rtc service exited with code 1 (by signal 0)
many many of those errors…
that means your config file does not exist where you are configured the docker container to look
well, i didnt configure anything inside docker.
I just followed the install text.
As I said before, i never used docker before and i would be happy if someone could give me a step by step instruction. (Still cant understand why some things must be so user-unfriendly under Linux…)
i used this lines to setup the frigate-container: NOTE, that i specified the path to config file in /etc/frigate, but logs show still /config/config.yml!
podman run -d --name frigate --restart=unless-stopped --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --device /dev/bus/usb:/dev/bus/usb --device /dev/dri/renderD128 --shm-size=64m -v /path/to/your/storage:/media/frigate -v /path/to/your/config.yml:/etc/frigate/config.yml -v /etc/localtime:/etc/localtime:ro -e FRIGATE_RTSP_PASSWORD='password' -p 5000:5000 -p 8554:8554 -p 8555:8555/tcp -p 8555:8555/udp ghcr.io/blakeblackshear/frigate:stable
So what do i do wrong??
You are supposed to change the /path/to/your/storage and /path/to/your/config and leave the right side of the : alone
ahhh 
OK.
Thank you, now i got it running!
One Thing is strange: I cant get connect via http://192.168.2.221:5000
What could be wrong? (And what is this webpage good for?)
if it won’t connect there then check the logs, most likely the config is not valid
s6-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 nginx-log successfully started
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service go2rtc-healthcheck successfully started
2023-10-03 21:29:20.378388562 [INFO] Preparing go2rtc config...
s6-rc: info: service legacy-services: starting
2023-10-03 21:29:20.378583806 [INFO] Starting Frigate...
2023-10-03 21:29:20.380560711 [INFO] Starting NGINX...
s6-rc: info: service legacy-services successfully started
2023-10-03 21:29:20.953445203 [INFO] Starting go2rtc...
2023-10-03 21:29:21.027956299 21:29:21.027 INF go2rtc version 1.2.0 linux/amd64
2023-10-03 21:29:21.028258878 21:29:21.028 INF [api] listen addr=:1984
2023-10-03 21:29:21.028613170 21:29:21.028 INF [rtsp] listen addr=:8554
2023-10-03 21:29:21.029136823 21:29:21.029 INF [srtp] listen addr=:8443
2023-10-03 21:29:21.029389447 21:29:21.029 INF [webrtc] listen addr=:8555
2023-10-03 21:29:21.088593763 2023/10/03 21:29:21 [error] 130#130: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168. 2.221, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1 :5001/stats", host: "192.168.2.221:5000"
2023-10-03 21:29:21.088667593 192.168.2.221 - - [03/Oct/2023:21:29:21 +0200] "G ET /api/stats HTTP/1.1" 502 157 "-" "HomeAssistant/2023.9.3 aiohttp/3.8.5 Python /3.11" "-"
2023-10-03 21:29:22.119876376 [2023-10-03 21:29:22] frigate.app INFO : Starting Frigate (0.12.1-367d724)
2023-10-03 21:29:22.151036246 [2023-10-03 21:29:22] peewee_migrate INFO : Starting migrations
2023-10-03 21:29:22.157340863 [2023-10-03 21:29:22] peewee_migrate INFO : There is nothing to migrate
2023-10-03 21:29:22.187555128 [2023-10-03 21:29:22] detector.cpu1 INFO : Starting detection process: 283
2023-10-03 21:29:22.207886836 [2023-10-03 21:29:22] detector.cpu2 INFO : Starting detection process: 285
2023-10-03 21:29:22.207896348 [2023-10-03 21:29:22] frigate.detectors WARNING : CPU detectors are not recommended and should only be used for test ing or for trial purposes.
2023-10-03 21:29:22.207900025 [2023-10-03 21:29:22] frigate.detectors WARNING : CPU detectors are not recommended and should only be used for test ing or for trial purposes.
2023-10-03 23:09:12.088527460 2023/10/03 23:09:12 [error] 131#131: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.221, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001/stats", host: "192.168.2.221:5000"
i think this is the error, but i dont know how it happens…