Replies: 25 comments 35 replies
-
I am going to use this this week thank you ! Never used Ubuntu but going to install it and run frigate. As my Synology can't run coral. |
Beta Was this translation helpful? Give feedback.
-
Hello @rugene76, I successfully used your guide and got version 11.1 up-and-running just fine. Version 12 has been released now. How do I modify the image to use version 12? Thanks - this was an excellent guide! Update* image: ghcr.io/blakeblackshear/frigate:stable You can update your guide for others. |
Beta Was this translation helpful? Give feedback.
-
Pick one. You cannot have both. |
Beta Was this translation helpful? Give feedback.
-
I've updated my proxmox guide with a few edits and a new section called "Updating individual pieces" that specifically addresses updating the coral driver after a proxmox kernel update, as well as portainer, docker and frigate v12 updates. |
Beta Was this translation helpful? Give feedback.
-
This is great, thank you for compiling and sharing this document. |
Beta Was this translation helpful? Give feedback.
-
FYI, portainer instructions have changed from version specific to a more generic url: https://docs.portainer.io/start/install-ce/server/docker/linux |
Beta Was this translation helpful? Give feedback.
-
Hi, hope this is the right place to post this. I've also created a similar guide for setting up Frigate and Home Assistant containers using Podman rootless containers. If there are any errors do not hesitate to correct me. Hope this helps for those who want to install it another way. https://www.spiffygoose.com/en/posts/2023_05_24_frigate-nvr-setup-with-homeassistant-using-podman/ |
Beta Was this translation helpful? Give feedback.
-
THANK YOU! I have been struggling with getting Frigate up and running for few days now and this .pdf saved me a lot of headache! ...funny, now I think it is quite easy. But getting it right form all online resources is still PITA... |
Beta Was this translation helpful? Give feedback.
-
Thank you for this guide! I'm part of the way through, currently waiting for my Coral device delivery before I continue. I do have one question: I might be missing it, but when I look through the guide I am not seeing the actual Frigate installation itself. I see the .yml configuration file example in the guide, as well as the example/sample to create the Portainer 'stack', but I'm not seeing the actual Frigate installer. I do see this line in the Portainer stack sample: Thanks again in advance! |
Beta Was this translation helpful? Give feedback.
-
Great guide, I followed these steps, hardware accelerion worksfine on Ryzen 5 7530U, Proxmox 8.1, LXC Ubuntu 23.10, Frigate 0.12.1. The only additional thing I had to do is to add "LIBVA_DRIVER_NAME: radeonsi" to the container config and install va-mesa-driver on the host. Thank you. |
Beta Was this translation helpful? Give feedback.
-
@rugene76 I have a couple questions for you if you don't mind? -What adapters are you using for the coral TPUs, I have a optiplex 7090 micro and am looking to install Corals like you have, Thanks for any help you can provide! |
Beta Was this translation helpful? Give feedback.
-
@rugene76, thank you so much for the guide. I have been struggling for a week. |
Beta Was this translation helpful? Give feedback.
-
Hello
My sample code in portainer stack editor:
What am I doing wrong? I would appreciate any help as I am completely new to this topic |
Beta Was this translation helpful? Give feedback.
-
full path to distro required image: ghcr.io/blakeblackshear/frigate:stable |
Beta Was this translation helpful? Give feedback.
-
I was hoping one of these other suggestions was going to help you, but
seems not to have.
From my personal experience, your speficic issue is usually related to a
poorly formatted yaml.
The usual culprits are:
an empty secondary option (ie, services, service, setting, option. Usually,
you have a setting without options or an option placed incorrectly.
Check your format spacing.
Services gets no space. Frigate gets 2 spaces. Any setting under frigate
gets 4 spaces and options of those settings get 6 spaces...
So, look at the, *=space
Services:
**frigate:
****devices
******/dev/bus/usb
Even a single extra or missing space will Bork your attempt.
Run your yaml through a checker (ill see if I can post a link)
- Robert Burton Thompson V
President: RnD Technologies
Ph: (717)466-9069
…On Wed, Sep 11, 2024, 2:07 AM pioro700 ***@***.***> wrote:
I have Coral M2
—
Reply to this email directly, view it on GitHub
<#4041 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB7VRSP5KUVI5AUFR5CBZKTZV7M3DAVCNFSM6AAAAAAQ76G43OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRQHE4TSNI>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
Maybe you deleted the camera password but that’s the first thing I see. After the admin ***@***.***:554/live/ch11On Sep 12, 2024, at 11:28 AM, pioro700 ***@***.***> wrote:
I have IP camera model : C6F0SoZ3N0PfL2
this is my Frigate Conf.
`mqtt:
enabled: true
host: 192.168.1.222
port: 1883
user: mqtt
password: haslo_mqtt
topic_prefix: frigate
client_id: frigate
stats_interval: 60
logger:
default: info
ffmpeg:
hwaccel_args: preset-vaapi
detectors:
coral:
type: edgetpu
device: pci
go2rtc:
streams:
IPCamera:
- ***@***.***:554/live/ch11
- ffmpeg:IPCamera#video=copy
IPCamera_detect:
- ***@***.***:554/live/ch12
- ffmpeg:IPCamera_detect#video=copy
webrtc:
candidates:
- 192.168.1.222:8555
- stun:8555
log:
level: debug
exec: trace
cameras:
IPCamera:
enabled: true
ui:
order: 1
ffmpeg:
output_args:
record: preset-record-generic
inputs:
- path: rtsp://localhost:8554/IPCamera_detect
input_args: preset-rtsp-restream
roles:
- detect
- path: rtsp://localhost:8554/IPCamera
input_args: preset-rtsp-restream
roles:
- record
objects:
track:
- person
- plate
filters:
plate: {}
live:
stream_name: IPCamera
record:
enabled: true
expire_interval: 60
retain:
days: 7
mode: active_objects
events:
pre_capture: 30
post_capture: 60
retain:
default: 60
snapshots:
enabled: true
clean_copy: false
timestamp: true
bounding_box: true
crop: false
height: 720
required_zones: []
retain:
default: 60
motion:
threshold: 40
lightning_threshold: 0.8
contour_area: 10
frame_alpha: 0.01
frame_height: 50
improve_contrast: true
mqtt_off_delay: 30
detect:
enabled: true
width: 1280
height: 720
fps: 10
stationary:
interval: 50
threshold: 50
version: 0.14
`
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Look at your file. You have the rtsp://admin: line in the config file. Can you login to the camera? On Sep 12, 2024, at 12:17 PM, pioro700 ***@***.***> wrote:
Where you can see it ?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Try with a bare-bones frigate config file. Remove all the extraneous options and just get the camera working. You can add everything else back in later. That’s what I would do. On Sep 12, 2024, at 12:36 PM, pioro700 ***@***.***> wrote:
I removed the password from the camera. I can log into it both with and without the password.
I sparred the rtsp path in VLC player and it works flawlessly.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Try something like this. Until you get the basic camera working there is no point in the options. mqtt: host: 192.168.178.82 user: mqtt password: PASSWORDffmpeg: hwaccel_args: preset-vaapidetect: width: 1280 height: 720go2rtc: streams: office: - ***@***.***:554/stream1 cameras: Office: ffmpeg: output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/office input_args: preset-rtsp-restream roles: - detect - recorddetectors: coral: type: edgetpu device: usbrecord: enabled: true retain: days: 3 mode: motion events: retain: default: 3 mode: active_objectstelemetry: stats: intel_gpu_stats: true version_check: trueui: timezone: Europe/Berlinversion: 0.14On Sep 12, 2024, at 12:39 PM, Frank Spatt ***@***.***> wrote:Try with a bare-bones frigate config file. Remove all the extraneous options and just get the camera working. You can add everything else back in later. That’s what I would do. On Sep 12, 2024, at 12:36 PM, pioro700 ***@***.***> wrote:
I removed the password from the camera. I can log into it both with and without the password.
I sparred the rtsp path in VLC player and it works flawlessly.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Path has an extra ‘/‘On Sep 12, 2024, at 12:48 PM, pioro700 ***@***.***> wrote:
Ok. I tried this config:
mqtt:
enabled: true
host: 192.168.1.222
port: 1883
user: mqtt
password: haslo_mqtt
topic_prefix: frigate
client_id: frigate
stats_interval: 60
logger:
default: info
ffmpeg:
hwaccel_args: preset-vaapi
detectors:
coral:
type: edgetpu
device: pci
cameras:
IPCamera:
detect:
width: 1280
height: 720
fps: 5
ffmpeg:
inputs:
- path: ***@***.***:554/rtsp
roles:
- detect
version: 0.14
and that's what I've got :
2024-09-12 12:44:00.225926831 [INFO] Preparing new go2rtc config...
2024-09-12 12:44:00.227368121 [INFO] Preparing Frigate...
2024-09-12 12:44:00.230093521 [INFO] Starting NGINX...
2024-09-12 12:44:00.258718818 [INFO] Starting Frigate...
2024-09-12 12:44:00.614711635 [INFO] Starting go2rtc...
2024-09-12 12:44:00.784457857 12:44:00.783 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-09-12 12:44:00.784462317 12:44:00.783 INF config path=/dev/shm/go2rtc.yaml
2024-09-12 12:44:00.784464772 12:44:00.783 INF [rtsp] listen addr=:8554
2024-09-12 12:44:00.784466953 12:44:00.784 INF [webrtc] listen addr=:8555/tcp
2024-09-12 12:44:00.784722408 12:44:00.784 INF [api] listen addr=:1984
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
2024-09-12 12:44:01.377951660 [INFO] Starting certsync...
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2024-09-12 12:44:01.490715860 127.0.0.1 - - [12/Sep/2024:12:44:01 +0200] "" 400 0 "-" "-" "-"
2024-09-12 12:44:01.777023496 [2024-09-12 12:44:01] frigate.app INFO : Starting Frigate (0.14.1-f4f3cfa)
2024-09-12 12:44:01.777313302 [2024-09-12 12:44:01] frigate.util.config INFO : Checking if frigate config needs migration...
2024-09-12 12:44:01.787209659 [2024-09-12 12:44:01] frigate.util.config INFO : copying config as backup...
2024-09-12 12:44:01.788039721 [2024-09-12 12:44:01] frigate.util.config INFO : Migrating frigate config from 0.13 to 0.14...
2024-09-12 12:44:01.792693768 [2024-09-12 12:44:01] frigate.util.config INFO : Migrating export file names...
2024-09-12 12:44:01.793034484 [2024-09-12 12:44:01] frigate.util.config INFO : Finished frigate config migration...
2024-09-12 12:44:01.827874534 [2024-09-12 12:44:01] peewee_migrate.logs INFO : Starting migrations
2024-09-12 12:44:01.828456327 [2024-09-12 12:44:01] peewee_migrate.logs INFO : There is nothing to migrate
2024-09-12 12:44:01.834078394 [2024-09-12 12:44:01] frigate.app INFO : Recording process started: 269
2024-09-12 12:44:01.840106585 [2024-09-12 12:44:01] frigate.app INFO : Recording process started: 271
2024-09-12 12:44:01.846000699 [2024-09-12 12:44:01] frigate.app INFO : go2rtc process pid: 107
2024-09-12 12:44:01.875191561 [2024-09-12 12:44:01] frigate.app INFO : Output process started: 299
2024-09-12 12:44:01.893088029 [2024-09-12 12:44:01] frigate.app INFO : Camera processor started for IPCamera: 314
2024-09-12 12:44:01.901215164 [2024-09-12 12:44:01] frigate.app INFO : Capture process started for IPCamera: 316
2024-09-12 12:44:01.922561631 [2024-09-12 12:44:01] detector.coral INFO : Starting detection process: 298
2024-09-12 12:44:01.922565355 [2024-09-12 12:44:01] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as pci
2024-09-12 12:44:01.929293036 [2024-09-12 12:44:01] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found
2024-09-12 12:44:01.956746403 [2024-09-12 12:44:01] frigate.video ERROR : IPCamera: Unable to read frames from ffmpeg process.
2024-09-12 12:44:01.957083225 [2024-09-12 12:44:01] frigate.video ERROR : IPCamera: ffmpeg process is not running. exiting capture thread...
2024-09-12 12:44:10.227672497 [INFO] Starting go2rtc healthcheck service...
2024-09-12 12:44:21.960737196 [2024-09-12 12:44:21] watchdog.IPCamera ERROR : Ffmpeg process crashed unexpectedly for IPCamera.
2024-09-12 12:44:21.961110310 [2024-09-12 12:44:21] watchdog.IPCamera ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2024-09-12 12:44:21.961454891 [2024-09-12 12:44:21] ffmpeg.IPCamera.detect ERROR : [tcp @ 0x562ada22a2c0] Connection to tcp://:554?timeout=5000000 failed: Cannot assign requested address
2024-09-12 12:44:21.961463450 [2024-09-12 12:44:21] ffmpeg.IPCamera.detect ERROR : ***@***.***:554/rtsp: Cannot assign requested address
2024-09-12 12:44:21.990447239 [2024-09-12 12:44:21] frigate.video ERROR : IPCamera: Unable to read frames from ffmpeg process.
2024-09-12 12:44:21.990785541 [2024-09-12 12:44:21] frigate.video ERROR : IPCamera: ffmpeg process is not running. exiting capture thread...
2024-09-12 12:44:27.560842372 [2024-09-12 12:44:27] frigate.comms.mqtt ERROR : Unable to publish to stats: client is not connected
2024-09-12 12:44:31.987194194 [2024-09-12 12:44:31] watchdog.IPCamera ERROR : Ffmpeg process crashed unexpectedly for IPCamera.
2024-09-12 12:44:32.002254874 [2024-09-12 12:44:31] watchdog.IPCamera ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2024-09-12 12:44:32.002267299 [2024-09-12 12:44:31] ffmpeg.IPCamera.detect ERROR : [tcp @ 0x55fd3e9a72c0] Connection to tcp://:554?timeout=5000000 failed: Cannot assign requested address
2024-09-12 12:44:32.002274334 [2024-09-12 12:44:31] ffmpeg.IPCamera.detect ERROR : ***@***.***:554/rtsp: Cannot assign requested address
2024-09-12 12:44:32.028750309 [2024-09-12 12:44:32] frigate.video ERROR : IPCamera: Unable to read frames from ffmpeg process.
2024-09-12 12:44:32.029182117 [2024-09-12 12:44:32] frigate.video ERROR : IPCamera: ffmpeg process is not running. exiting capture thread...
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I'm going to go back to the no admin password as being one of your issues.
You can't trail your admin with the colons you have, it's expecting a
password there when you leave it like that.
You need ***@***.***
Or ***@***.***
***@***.*** going to cause some kind of issues. I don't know if
this is the only problem, but it is A problem.
- Robert Burton Thompson V
President: RnD Technologies
Ph: (717)466-9069
…On Thu, Sep 12, 2024, 7:32 AM pioro700 ***@***.***> wrote:
The example you gave completely confuses me and in no way am I able to
find the references in “https://docs.frigate.video/configuration/”.
As I wrote in the first post I am completely new to this topic.
—
Reply to this email directly, view it on GitHub
<#4041 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB7VRSLQ3RI7LE25LBRK3BLZWF3UXAVCNFSM6AAAAAAQ76G43OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRSGUZDENA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
No, I'm saying that your config has you pointing to
***@***.***
It Should be
***@***.***
Without the ":" after admin
That ":" after admin is advising the system that there should be a password
attached. As formatting for that is
***@***.***
But,you aren't supplying a password, so... You want:
***@***.***
I hope that explains it better
…On Thu, Sep 12, 2024, 7:54 AM pioro700 ***@***.***> wrote:
I completely don't understand your notation:
no.1 *@*.*** is the same as no.2 *@*.*** and no.3 *@*.***
Do you mean : ***@***.***:port ????
If so, I tried both with and without password and the effect is exactly
the same.
—
Reply to this email directly, view it on GitHub
<#4041 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB7VRSMCQ26NZ45GQWCV3YLZWF6GNAVCNFSM6AAAAAAQ76G43OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRSGU2DEMA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
Thanks for posting such a thorough and detailed document! I'm really excited to get started on this project, as I've been wanting to find an alternative to Blue Iris for a LONG time! You've put all the pieces in place, and again, I thank you. I got a Coral and an adapter ordered yesterday, and I'll grab an eBay PC today along with a large HD. So hopefully, by next week I should be able to start putting the pieces together. It should be fun and a BIG step away from Blue Iris' mediocrity. |
Beta Was this translation helpful? Give feedback.
-
This project totally beat me down. The instructions, while detailed, are out of date. I've spent 4 hours this afternoon trying to get the Coral installed on Ubuntu 24.04 and still can't get it to work. It appears that the instructions from the Coral website are outdated and do not lead to a successful driver installation on 24.04. I'm not sure what I have right now, but I'm definitely dead in the water with my Frigate project, so if anyone is following and could lend a hand, I'd sure appreciate it. I had such high hopes that this all-encompassing instruction document would have all the pieces to the puzzle. |
Beta Was this translation helpful? Give feedback.
-
I recently upgraded to proxmox 8 and had a great deal of trouble getting coral installed. I found these commands to run on the promox host that worked. Don't know why but they do.... The following is for proxmox 8, the proxmox 7 install procedure will not work. Do these commands exactly: This was all done from root user#First verify your machine has MSI-X by running this command apt install sudo -y |
Beta Was this translation helpful? Give feedback.
-
I recently struggled with installing frigate on docker. The necessary info is scattered across the web and requires a great deal of technical knowledge. To help others avoid what I went through, I've created an installation guide aimed at the technical enthusiast with casual linux skills. For instance, someone not familiar with docker or portainer or who has only vague or rusty understanding of linux. I figure its the least I can do to help out the frigate project.
I've attached my first crack at the guide for a look see. Please let me know what you think.
Installing frigate from scratch.pdf
Beta Was this translation helpful? Give feedback.
All reactions