September 24, 20241 yr 23 minutes ago, wgstarks said: I may be wrong but I don’t think you can configure the same port (8555) as udp and tcp. Having both on the same port is valid.
September 24, 20241 yr 32 minutes ago, wgstarks said: I may be wrong 8 minutes ago, JonathanM said: Having both on the same port is valid. Well then I was correct, I was definitely wrong. 🙃 Sorry
September 24, 20241 yr 45 minutes ago, _cr8tor_ said: Cant seem to install this but its also so basic for config i have no idea why not. Thoughts? config: https://imgur.com/a/afk1Y7h error: https://imgur.com/a/0G7j9CO I got this working. All of those settings that have a description that ends with "Remove this if you are not using it". Well, i was removing them. Other than the nvidia items. Instead, i left all the default settings and it ran successfully and i can log in and configure it now.
September 29, 20241 yr Author On 9/24/2024 at 11:57 PM, _cr8tor_ said: Its the default config options there, i did adjust it to 5556 for the udp and no change. You have to delete the entries you are not using, as you can read in the description on each entry.
October 10, 20241 yr hey guys, after updating my frigate when it broke it was all going well for a couple weeks and then a bunch of errors, i then restarted it and it came good again, however i now have a bunch of errors again, seems to be these errors over and over, any idea on what i need to resolve please. ill need it in basic terms please as im quite a noob 2024-10-10 04:20:40.348681242 [2024-10-10 04:20:40] ffmpeg.name_of_your_camera.detect ERROR : [tcp @ 0x5587c4636140] Connection to tcp://10.0.10.10:554?timeout=5000000 failed: Connection timed out 2024-10-10 04:20:40.348787342 [2024-10-10 04:20:40] ffmpeg.name_of_your_camera.detect ERROR : rtsp://10.0.10.10:554/rtsp: Connection timed out 2024-10-10 04:20:45.384809015 [2024-10-10 04:20:45] frigate.video ERROR : name_of_your_camera: Unable to read frames from ffmpeg process. 2024-10-10 04:20:45.384973086 [2024-10-10 04:20:45] frigate.video ERROR : name_of_your_camera: ffmpeg process is not running. exiting capture thread... 2024-10-10 04:20:50.370460595 [2024-10-10 04:20:50] watchdog.name_of_your_camera ERROR : Ffmpeg process crashed unexpectedly for name_of_your_camera. 2024-10-10 04:20:50.370621154 [2024-10-10 04:20:50] watchdog.name_of_your_camera ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-10-10 04:20:50.370763344 [2024-10-10 04:20:50] ffmpeg.name_of_your_camera.detect ERROR : [tcp @ 0x564007608140] Connection to tcp://10.0.10.10:554?timeout=5000000 failed: Connection timed out 2024-10-10 04:20:50.383082319 [2024-10-10 04:20:50] ffmpeg.name_of_your_camera.detect ERROR : rtsp://10.0.10.10:554/rtsp: Connection timed out
October 10, 20241 yr Author On 9/28/2024 at 5:17 PM, Olivier Roy said: Hi everyone, I am trying to configure Frigate with hardware acceleration using an old GPU lying around but I can’t get it working. It shows up in System Devices as: [1002:68d9] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/7570] It should be compatible with Frigate according to the documentation: https://docs.frigate.video/configuration/hardware_acceleration/#amdati-gpus-radeon-hd-2000-and-newer-gpus-via-libva-mesa-driver Here is my container configuration: Here is my config.yml file: Here are the logs when I start the container: Try placing FFMPEG as a root entry and not inside the camera only
October 10, 20241 yr Author 5 hours ago, bushbasha said: hey guys, after updating my frigate when it broke it was all going well for a couple weeks and then a bunch of errors, i then restarted it and it came good again, however i now have a bunch of errors again, seems to be these errors over and over, any idea on what i need to resolve please. ill need it in basic terms please as im quite a noob 2024-10-10 04:20:40.348681242 [2024-10-10 04:20:40] ffmpeg.name_of_your_camera.detect ERROR : [tcp @ 0x5587c4636140] Connection to tcp://10.0.10.10:554?timeout=5000000 failed: Connection timed out 2024-10-10 04:20:40.348787342 [2024-10-10 04:20:40] ffmpeg.name_of_your_camera.detect ERROR : rtsp://10.0.10.10:554/rtsp: Connection timed out 2024-10-10 04:20:45.384809015 [2024-10-10 04:20:45] frigate.video ERROR : name_of_your_camera: Unable to read frames from ffmpeg process. 2024-10-10 04:20:45.384973086 [2024-10-10 04:20:45] frigate.video ERROR : name_of_your_camera: ffmpeg process is not running. exiting capture thread... 2024-10-10 04:20:50.370460595 [2024-10-10 04:20:50] watchdog.name_of_your_camera ERROR : Ffmpeg process crashed unexpectedly for name_of_your_camera. 2024-10-10 04:20:50.370621154 [2024-10-10 04:20:50] watchdog.name_of_your_camera ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-10-10 04:20:50.370763344 [2024-10-10 04:20:50] ffmpeg.name_of_your_camera.detect ERROR : [tcp @ 0x564007608140] Connection to tcp://10.0.10.10:554?timeout=5000000 failed: Connection timed out 2024-10-10 04:20:50.383082319 [2024-10-10 04:20:50] ffmpeg.name_of_your_camera.detect ERROR : rtsp://10.0.10.10:554/rtsp: Connection timed out Looks like your Frigate is not able to reach your camera, so check your communications.
October 10, 20241 yr 4 hours ago, yayitazale said: Looks like your Frigate is not able to reach your camera, so check your communications. why would it work for a few weeks and then error out? what side am i checking it on, frigate or my actual NVR side. as my NVR is still working fine. what changed between the new frigate and the old frigate that i would have needed to change for the communications side?
October 10, 20241 yr Author 28 minutes ago, bushbasha said: why would it work for a few weeks and then error out? what side am i checking it on, frigate or my actual NVR side. as my NVR is still working fine. what changed between the new frigate and the old frigate that i would have needed to change for the communications side? I don't know your communications infrastructure, configurations, etc. Nor can I know if you have made changes to anything that might affect. In any case, the latest mayor version change (v14) has quite a few changes so you may want to read the release notes as well as the new documentation. https://docs.frigate.video/ https://github.com/blakeblackshear/frigate/releases/tag/v0.14.0
October 18, 20241 yr Frigate crashed today and I think it's due to my coral TPU overheating? Any ideas here? It's been working fine for over a week now. This is the PCI version. I rebooted and it came back, but don't know what might have caused it. I have attached 2 screenshots before and after the reboot. detectors: coral: type: edgetpu device: pci:0 Edited October 18, 20241 yr by deliverer
October 18, 20241 yr 5 minutes ago, deliverer said: Frigate crashed today and I think it's due to my coral TPU overheating? Any ideas here? It's been working fine for over a week now. This is the PCI version. detectors: coral: type: edgetpu device: pci:0 Holy moly that's hot!! Mine rarely gets to 55c. Idles at 48c Did you have the boost mode on the tpu? What's your camera/config set up like? Overworking with too many operations per second?
October 19, 20241 yr Probably easier to add a little 30mm fan to it like we do for HBA cards? I have the USB coral version & below are frigate stats with 5x camera feeds @ 8fps each for detection. Recording is 20fps each 4k. Edited October 19, 20241 yr by dopeytree
October 19, 20241 yr Author On 10/18/2024 at 6:17 PM, deliverer said: Frigate crashed today and I think it's due to my coral TPU overheating? Any ideas here? It's been working fine for over a week now. This is the PCI version. I rebooted and it came back, but don't know what might have caused it. I have attached 2 screenshots before and after the reboot. detectors: coral: type: edgetpu device: pci:0 Yes it looks like you had a thermal shutdown. Yo should add some kind of active cooling.
October 20, 20241 yr Hello, I have a new Problem with Frigate 😔 I had to restart the server several times after performing a BIOS update. Then I checked the individual dockers to see if everything was working, and I noticed that there were a few problems with Frigate. The following errors are displayed: 2024-10-20 15:30:57.383331920 [2024-10-20 15:30:57] frigate.app INFO : Starting Frigate (0.14.1-f4f3cfa) 2024-10-20 15:30:57.383354450 [2024-10-20 15:30:57] frigate.util.config INFO : Checking if frigate config needs migration... 2024-10-20 15:30:57.424972116 [2024-10-20 15:30:57] frigate.util.config INFO : frigate config does not need migration... 2024-10-20 15:30:57.492744878 [2024-10-20 15:30:57] peewee_migrate.logs INFO : Starting migrations 2024-10-20 15:30:57.492808978 [2024-10-20 15:30:57] peewee_migrate.logs INFO : There is nothing to migrate 2024-10-20 15:30:57.536346596 [2024-10-20 15:30:57] frigate.app INFO : Recording process started: 365 2024-10-20 15:30:57.537280988 [2024-10-20 15:30:57] frigate.app INFO : Recording process started: 374 2024-10-20 15:30:57.539880141 [2024-10-20 15:30:57] frigate.app INFO : go2rtc process pid: 98 2024-10-20 15:30:57.576308580 [2024-10-20 15:30:57] detector.coral1 INFO : Starting detection process: 394 2024-10-20 15:30:57.586639104 [2024-10-20 15:30:57] detector.coral2 INFO : Starting detection process: 400 2024-10-20 15:30:57.596977808 [2024-10-20 15:30:57] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as pci:0 2024-10-20 15:30:57.597486929 [2024-10-20 15:30:57] frigate.app INFO : Output process started: 416 2024-10-20 15:30:57.601464874 [2024-10-20 15:30:57] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as pci:1 2024-10-20 15:30:57.601764565 [2024-10-20 15:30:57] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-10-20 15:30:57.601882605 [2024-10-20 15:30:57] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-10-20 15:30:57.636500592 [2024-10-20 15:30:57] frigate.app INFO : Camera processor started for Eingang_rechts: 448 2024-10-20 15:30:57.646912616 [2024-10-20 15:30:57] frigate.app INFO : Camera processor started for Eingang_links: 453 2024-10-20 15:30:57.658714762 [2024-10-20 15:30:57] frigate.app INFO : Camera processor started for Hinten_rechts: 459 2024-10-20 15:30:57.673977162 [2024-10-20 15:30:57] frigate.app INFO : Camera processor started for Hinten_links: 472 2024-10-20 15:30:57.689051572 [2024-10-20 15:30:57] frigate.app INFO : Capture process started for Eingang_rechts: 490 2024-10-20 15:30:57.703237412 [2024-10-20 15:30:57] frigate.app INFO : Capture process started for Eingang_links: 498 2024-10-20 15:30:57.717409961 [2024-10-20 15:30:57] frigate.app INFO : Capture process started for Hinten_rechts: 503 2024-10-20 15:30:57.730972779 [2024-10-20 15:30:57] frigate.app INFO : Capture process started for Hinten_links: 508 2024-10-20 15:30:58.906570836 [2024-10-20 15:30:58] frigate.video ERROR : Hinten_rechts: Unable to read frames from ffmpeg process. 2024-10-20 15:30:58.906869107 [2024-10-20 15:30:58] frigate.video ERROR : Hinten_rechts: ffmpeg process is not running. exiting capture thread... 2024-10-20 15:30:59.193160553 [2024-10-20 15:30:59] frigate.video ERROR : Eingang_links: Unable to read frames from ffmpeg process. 2024-10-20 15:30:59.193403033 [2024-10-20 15:30:59] frigate.video ERROR : Eingang_links: ffmpeg process is not running. exiting capture thread... 2024-10-20 15:30:59.811290457 [2024-10-20 15:30:59] frigate.video ERROR : Hinten_links: Unable to read frames from ffmpeg process. 2024-10-20 15:30:59.811671587 [2024-10-20 15:30:59] frigate.video ERROR : Hinten_links: ffmpeg process is not running. exiting capture thread... 2024-10-20 15:31:00.166152494 [2024-10-20 15:31:00] frigate.video ERROR : Eingang_rechts: Unable to read frames from ffmpeg process. 2024-10-20 15:31:00.166331425 [2024-10-20 15:31:00] frigate.video ERROR : Eingang_rechts: ffmpeg process is not running. exiting capture thread... I didn't change anything in the config and everything worked before. I also checked the BIOS settings, but everything is fine there and the old settings were completely adopted. The cameras are running and I can access them normally. It's just that nothing is displayed in Frigate.
October 21, 20241 yr On 10/19/2024 at 12:01 PM, yayitazale said: Yes it looks like you had a thermal shutdown. Yo should add some kind of active cooling. installing my newly aqcuired pcie card this week, any specific recommendations / example links re: active cooling?
October 24, 20241 yr On 9/24/2024 at 5:24 PM, _cr8tor_ said: I got this working. All of those settings that have a description that ends with "Remove this if you are not using it". Well, i was removing them. Other than the nvidia items. Instead, i left all the default settings and it ran successfully and i can log in and configure it now. Thanks for this, I was really trying to wrap my head around the error I was receiving when installing without any of the options I won't use.
October 31, 20241 yr Are there any plans to implement user permissions? For example an admin user that has access to settings/config, and other users that can only view cameras?
October 31, 20241 yr Wierd live view resizing on the fly. running frigate for a few months w/out issues. couple of weeks ago the live view started acting weird. i have 8 tapo c210's. they always showed the view in a nice widescreen looking sizing, now they randomly resize themselves looks like similar to bouncing from 16:9 to 4:3 - but i never changed any settings. they will just adjust on their own with no visible reason why. screenshots included for reference. A and C are the same cams, B and D are the same cams. You can see the size difference on B and D. they'll just resize seemingly randomly. what is going on here? i think i saw in the config i can specify a size but never had to previously.
November 2, 20241 yr Author On 10/31/2024 at 2:39 PM, TurboStreetCar said: Are there any plans to implement user permissions? For example an admin user that has access to settings/config, and other users that can only view cameras? You can find out by yourself: https://github.com/blakeblackshear/frigate/discussions/12292
November 2, 20241 yr Author On 10/31/2024 at 5:06 PM, Azreal said: Wierd live view resizing on the fly. running frigate for a few months w/out issues. couple of weeks ago the live view started acting weird. i have 8 tapo c210's. they always showed the view in a nice widescreen looking sizing, now they randomly resize themselves looks like similar to bouncing from 16:9 to 4:3 - but i never changed any settings. they will just adjust on their own with no visible reason why. screenshots included for reference. A and C are the same cams, B and D are the same cams. You can see the size difference on B and D. they'll just resize seemingly randomly. what is going on here? i think i saw in the config i can specify a size but never had to previously. You should define the size of the cameras. You can see in the example config of the docs: https://docs.frigate.video/configuration/
November 3, 20241 yr On 11/2/2024 at 9:19 AM, yayitazale said: You should define the size of the cameras. You can see in the example config of the docs: https://docs.frigate.video/configuration/ yeah was hoping to understand why it's happening when it didn't for months. however, where would i define it? is it under the go2rtc -> streams? or is it in the camera setup under output_args or inputs? i see it in the reference under the detect stream, but that doesn't sound right to me or i don't think it aligns with what i'm doing anyways. these particular camera are just continuous recording, no object detection or other triggered type events for these.
November 5, 20241 yr Author On 11/3/2024 at 4:51 PM, Azreal said: yeah was hoping to understand why it's happening when it didn't for months. however, where would i define it? is it under the go2rtc -> streams? or is it in the camera setup under output_args or inputs? i see it in the reference under the detect stream, but that doesn't sound right to me or i don't think it aligns with what i'm doing anyways. these particular camera are just continuous recording, no object detection or other triggered type events for these. Not sure, please open a issue in github issues page. https://github.com/blakeblackshear/frigate/issues
November 8, 20241 yr Greetings all After a lot of testing and research it seems that Frigate is crashing my flash boot drive and killing my server. I installed frigate about 1 month ago with a very simple one camera config. I first had my flash drive crash in early October and replaced the drive and restored with a Unraid connect backup from the previous weekend. For about a week I only spun up may Home Assistant VM and did my parity checks to make sure the system was stable. I started my all of my dockers and then within 24 hours another drive says it's corrupt or unavailable. Thinking it just maybe a fluke, I replaced that drive again and recovered from a backup, Parity checked and only brought up my VM and one docker. Waited a few days and brought up another docker. I Brought up the Frigate docker and within 24 hours the flash drive failed. Luckily I was able to put my Flash boot drive in a windows machine and repaired it and got back running. I put in a ticket with Unraid support and we got the syslogs and found the error below. For one last test this Monday brought up the server with just the Frigate docker and it failed again. Repaired the drive, spun up everything except Frigate and it's been stable. So I've isolated the issue to the Frigate docker. I think it has something to do with the USB Coral TPU. Yes I've switched USB ports and confirmed it's working in another computer. Attached is a picture of the docker config for frigate. Outside of that I don't know. I need to get this working as I have very limited time to work on this for the rest of the year. server config Supermicro X10SRH-CF Intel Xeon CPU E5-2698 v4 128GB RAM USB Coral TPU Nvidia 3060 12gb (Not used for Frigate) Error in the Syslogs Nov 4 20:50:15 PhreakServe kernel: usb 3-6: device descriptor read/8, error -110 Nov 4 20:50:15 PhreakServe kernel: usb 3-6: USB disconnect, device number 3 Nov 4 20:50:15 PhreakServe emhttpd: Unregistered Flash device blacklisted (EBLACKLISTED2)
November 8, 20241 yr You can run Unraid without the flash drive plugged in, how is your drive failing while not being written to? Edited November 8, 20241 yr by Espressomatic
November 9, 20241 yr 11 hours ago, Phreaknes said: it seems that Frigate is crashing my flash boot drive Flash drive is loaded to RAM on boot. Frigate is NOT crashing your flash drive. 11 hours ago, Phreaknes said: Nvidia 3060 12gb (Not used for Frigate) Yet in your container setup you have listed tensor models to use. Am thinking you need to go back and read the docs for frigate. And the docs for unraid.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.