have been through the docs many times , only got a working system from watching a few videos,
sorry if I appear stupid compared to you but I just don’t understand how this works?
you asked for my yml I gave you my yml from both docker and home assistant? why have I upset you?
GNU nano 5.4 docker-compose.yml *
image: blakeblackshear/frigate:stable
shm_size: “64mb” # update for your cameras based on calculation above
devices:
is this not yml? have you read the problems I had with install? do you understand I wrote every step I took so far?
I have edited out my passwords and ip address for cameras as I still am unsure of secrets, this is the only difference in my frigate.yml that has been changed, I had a much more complicated yml setup on my pi4 but simplified it to try and get things working.
I run Hubitat as my main hub at home and think it’s amazing, I have some great automations set up it is almost perfect. I want home assistant to run along side to get things into the system I wouldn’t be able to do without it. Plus the voice notifications with Hubitat always stop the music and I want to get my sonos speakers to carry out a notification without stopping the music all the time, so I need home assistant for this. Plus I need frigate as its definitely the best thing you can get for camera security
I am not the best at technical stuff but have been doing well on other platforms with a little help to get me understanding.
I am fairly new to the home assistant community, as on the other one or 2 attempts to communicate I always get unhelpful comments if any at all. I would like to think there is help out there to bring new people in and I know the Hubitat community has been amazingly helpful and friendly and got my house fully automated from a morning weather alert to a robot vacuum that can close itself in a cubourd
I mentioned it at the start, but please use code formatting
When you just vomit the text into a post without markup we can’t see whether you’ve done anything correctly or not.
There’s no need to reboot, all you need to do is issue docker compose up -d.
I have installed frigate proxy, still not sure what to do next?
I Had already done this its running, I used the command too and it says it’s already up to date and won’t rebuild? the frigate add-ons our not running in home assistant tho I will try again with it running
am I supposed to use this somewhere?
database:
path: /db/frigate.db
what’s this meant to mean?
When running Home Assistant with the Supervised install method, you can get the benefit of running the Addon along with the ability to customize the storage used by Frigate.
In order to customize the storage location for Frigate, simply use fstab to mount the drive you want at /usr/share/hassio/media. Here is an example fstab entry:
UUID=1a65fec6-c25f-404a-b3d2-1f2fcf6095c8 /media/data ext4 defaults 0 0
/media/data/homeassistant/media /usr/share/hassio/media none bind 0 0
by the looks of this I no longer need a frigate.yml in home assistant?
Configuration tabfrigate.yml in your config directory with your detailed Frigate configurationas from last experiences the home assistant crowd would rather put someone down for lack of knowledge rather then point them in the right direction.
I have just copied and pasted my code and yaml likes it so I don’t what wrong with it for you?
I found this guide that takes time to get things done thank you for you help
Please … don’t share images of text
If you can’t work out how to use code markup then use a code share site like https://dpaste.org/ instead.
One last time… use code markup
The problem is that you’re not paying any attention to what we ask, making it impossible to help you.
YAML is all about how things are indented, when you just drop it into the text here we can’t tell that
this:
yaml: here
is actually
this:
yaml: here
For posting code in the forum @Tinkerer pointed to the right direction in his first post in this thread. I’ll point to it again. How to help us help you - or How to ask a good question
Now responding to this, Home assistant yellow and docker compose frigate - #21 by Richfa, it looks like frigate.local is not resolving. Try the pi’s ip addess in the config of the frigate proxy addon.
Thank you, going to start a fresh build tonight, I still have much more to learn then I originally thought.
Even now I will have to put information into this from several different sources to try and get this working
I will start by getting docker and docker compose running fresh, then take it step by step using
https://hub.docker.com/_/eclipse-mosquitto
and use this to get the broker working as it seems to work better at the start
Still struggling with getting frigate in docker to work by itself, I am going to try a workaround as I know I can get it working as a add on in HA
My workaround is to try installing the full version of HA in docker with the config file for frigate either the mqtt in config in docker HA pointing to my main instance of Ha
Do you think this will work in may be easier and more what I am used to hopefully
Not sure if you already solved this by yourself, but otherwise the following YT video maybe helps you:
Or the following blog post:
thank you i managed to figure it out in the end
how? what’d you do differently
sorry for delay, i had it working on my pi by making directory’s on it by using the mkdir command example mkdir frigate, cd frigate, mkdir media, cd media, mkdir storage, exit
then start again making the next volume cd frigate, mkdir config, touch config.yml, nano config.yml
then add the config in there save and close. exit
cd frigate, nano docker-compose.yml, then add your compose file with the 2 above volumes created, save and exit docker-compose up -d
this worked for my pi4 but I have upgraded to a intel nuc as my pi never had enough CPU power now this method doesn’t seem to work unless its due to breaking changes in the frigate install I am not sure. i read that later versions can be used but I haven’t found any links to these files yet to try
my current logs our as follows
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 go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
2023-05-27 07:59:23.329803801 [INFO] Preparing go2rtc config…
2023-05-27 07:59:23.331389119 [INFO] Starting Frigate…
2023-05-27 07:59:23.332644780 [INFO] Starting NGINX…
s6-rc: info: service legacy-services successfully started
Traceback (most recent call last):
File “/usr/local/go2rtc/create_config.py”, line 23, in
with open(config_file) as f:
IsADirectoryError: [Errno 21] Is a directory: ‘/config/config.yml’
2023-05-27 07:59:23.542985525 [INFO] The go2rtc service exited with code 1 (by signal 0)
2023-05-27 07:59:24.089180434 *************************************************************
2023-05-27 07:59:24.089183816 *************************************************************
2023-05-27 07:59:24.089185423 *** Your config file is not valid! ***
2023-05-27 07:59:24.089186881 *** Please check the docs at ***
2023-05-27 07:59:24.089187998 *** Configuration File | Frigate ***
2023-05-27 07:59:24.089189369 *************************************************************
2023-05-27 07:59:24.089190349 *************************************************************
2023-05-27 07:59:24.089208200 *** Config Validation Errors ***
2023-05-27 07:59:24.089209196 *************************************************************
2023-05-27 07:59:24.089210020 [Errno 21] Is a directory: ‘/config/config.yml’
2023-05-27 07:59:24.089820617 Traceback (most recent call last):
2023-05-27 07:59:24.089822382 File “/opt/frigate/frigate/app.py”, line 351, in start
2023-05-27 07:59:24.089823302 self.init_config()
2023-05-27 07:59:24.089824292 File “/opt/frigate/frigate/app.py”, line 80, in init_config
2023-05-27 07:59:24.089825198 user_config = FrigateConfig.parse_file(config_file)
2023-05-27 07:59:24.089826130 File “/opt/frigate/frigate/config.py”, line 1064, in parse_file
2023-05-27 07:59:24.089826930 with open(config_file) as f:
2023-05-27 07:59:24.089827787 IsADirectoryError: [Errno 21] Is a directory: ‘/config/config.yml’
2023-05-27 07:59:24.089828487
2023-05-27 07:59:24.089829392 *************************************************************
2023-05-27 07:59:24.089830538 *** End Config Validation Errors ***
2023-05-27 07:59:24.089831418 *************************************************************
2023-05-27 07:59:24.090041378 [2023-05-27 07:59:24] frigate.app INFO : Starting Frigate (0.12.0-da3e197)
2023-05-27 07:59:24.551877388 [INFO] Preparing go2rtc config…
Traceback (most recent call last):
File “/usr/local/go2rtc/create_config.py”, line 23, in
with open(config_file) as f:
IsADirectoryError: [Errno 21] Is a directory: ‘/config/config.yml’
2023-05-27 07:59:24.719912546 [INFO] The go2rtc service exited with code 1 (by signal 0)
2023-05-27 07:59:25.211206622 [INFO] Service Frigate exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service go2rtc-healthcheck: stopping
2023-05-27 07:59:25.219222600 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2023-05-27 07:59:25.344639749 [INFO] Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
s6-rc: info: service nginx-log successfully stopped
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service frigate-log successfully stopped
s6-rc: info: service go2rtc-log successfully stopped
s6-rc: info: service log-prepare: stopping
s6-rc: info: service s6rc-fdholder: stopping
s6-rc: info: service log-prepare successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service s6rc-fdholder successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped