13 hours ago, yayitazale said:

Can you post your configuration of the docker container? It looks you have deleted this from extra parameters:

 

--mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000

 

This the location for video recording segments caching as you can read here:

https://docs.frigate.video/frigate/installation#storage

 

You are totally correct, idk why this has been removed. I just add it again now

Frigate doesn't seem to be detecting my nvidia GPU for hardware acceleration when checking the frigate system information

This is my extra parameters line "--shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --restart unless-stopped --runtime=nvidia"

I have entered the GPU ID and the set the capabilities to all. This is also the same when the capabilities are set to 'compute,utility,video'

nvidia-smi on the unraid terminal shows the ffmpeg process for the 1 camera I currently have and also the tensorrt detector process

 

I also have the hardware acceleration args like this in the frigate config:

 

ffmpeg:

  hwaccel_args:

    - -hwaccel

    - cuda

    - -c:v

    - h264_cuvid

 

Unsure of where to go next?

 

Edited November 13, 20232 yr by th3unpleasantpeasant

4 hours ago, th3unpleasantpeasant said:

Frigate doesn't seem to be detecting my nvidia GPU for hardware acceleration when checking the frigate system information

This is my extra parameters line "--shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --restart unless-stopped --runtime=nvidia"

I have entered the GPU ID and the set the capabilities to all. This is also the same when the capabilities are set to 'compute,utility,video'

nvidia-smi on the unraid terminal shows the ffmpeg process for the 1 camera I currently have and also the tensorrt detector process

 

I also have the hardware acceleration args like this in the frigate config:

 

ffmpeg:

  hwaccel_args:

    - -hwaccel

    - cuda

    - -c:v

    - h264_cuvid

 

Unsure of where to go next?

 

Seems to now be working after a full server restart

On 11/12/2023 at 7:38 PM, yayitazale said:

Can you post your configuration of the docker container? It looks you have deleted this from extra parameters:

 

--mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000

 

This the location for video recording segments caching as you can read here:

https://docs.frigate.video/frigate/installation#storage

 

Ok, after I added this again, here are the results after two days:

 

Filesystem      Size  Used Avail Use% Mounted on
/dev/loop2      108G   40G   66G  38% /
tmpfs            68M     0   68M   0% /dev
shfs            2.0T  526G  1.5T  27% /frigate/media
shm              68M  3.2M   64M   5% /dev/shm
/dev/loop2      108G   40G   66G  38% /etc/hosts
tmpfs           1.1G  1.6M  999M   1% /tmp/cache
overlay          17G  1.3G   16G   8% /usr/bin/nvidia-smi
rootfs           17G  1.3G   16G   8% /etc/vulkan/icd.d/nvidia_icd.json
tmpfs            17G   13k   17G   1% /proc/driver/nvidia
tmpfs            17G  4.1k   17G   1% /etc/nvidia/nvidia-application-profiles-rc.d
overlay          17G  1.3G   16G   8% /lib/firmware/nvidia/545.29.02/gsp_ga10x.bin
devtmpfs        8.4M     0  8.4M   0% /dev/nvidia0

 

I just don't know why /dev/loop2 is consuming a lot, you can see I have tmp/cache for 1GB

Any idea what's wrong there?

On 11/14/2023 at 11:20 AM, reasonable-panel3162 said:

Ok, after I added this again, here are the results after two days:

 

Filesystem      Size  Used Avail Use% Mounted on
/dev/loop2      108G   40G   66G  38% /
tmpfs            68M     0   68M   0% /dev
shfs            2.0T  526G  1.5T  27% /frigate/media
shm              68M  3.2M   64M   5% /dev/shm
/dev/loop2      108G   40G   66G  38% /etc/hosts
tmpfs           1.1G  1.6M  999M   1% /tmp/cache
overlay          17G  1.3G   16G   8% /usr/bin/nvidia-smi
rootfs           17G  1.3G   16G   8% /etc/vulkan/icd.d/nvidia_icd.json
tmpfs            17G   13k   17G   1% /proc/driver/nvidia
tmpfs            17G  4.1k   17G   1% /etc/nvidia/nvidia-application-profiles-rc.d
overlay          17G  1.3G   16G   8% /lib/firmware/nvidia/545.29.02/gsp_ga10x.bin
devtmpfs        8.4M     0  8.4M   0% /dev/nvidia0

 

I just don't know why /dev/loop2 is consuming a lot, you can see I have tmp/cache for 1GB

Any idea what's wrong there?

I don't know if this is normal or the is something wrong please ask on github and keep me in track of the issue.

On 11/15/2023 at 6:45 PM, yayitazale said:

I don't know if this is normal or the is something wrong please ask on github and keep me in track of the issue.

ok understood the reason! sometimes a stupid mistake can ruin everything. I just don't know when /media/frigate became /frigate/media in my configuration, I think the moment I created that shared for videos I made that mistake.

Basically Frigate was saving the videos inside the docker, now all things are good.
 

Recently, my Frigate/WhosAtMyFeeder installation quit identifying the bird species. Frigate logs ~50 "birds" every day, but they are no longer categorized by species. Is there something I need to look at to get this working again?

 

v/r

Jon 

18 minutes ago, irishjd said:

Recently, my Frigate/WhosAtMyFeeder installation quit identifying the bird species. Frigate logs ~50 "birds" every day, but they are no longer categorized by species. Is there something I need to look at to get this working again?

 

v/r

Jon 

Did you change anything? Is there anything in the logs of WhosAtMyFeeder?

2 minutes ago, yayitazale said:

Did you change anything? Is there anything in the logs of WhosAtMyFeeder?

No changes... the only error that I see in the logs are:

 

INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.

So there actually was a change. I am using a Ubiquity UniFi camera and they just upgraded their software. I made this assumption when I noticed that the frigate logs have a lot of errors about reading the camera feed. I'll dig a little deeper and see if I can figure it out.

 

3 minutes ago, irishjd said:

So there actually was a change. I am using a Ubiquity UniFi camera and they just upgraded their software. I made this assumption when I noticed that the frigate logs have a lot of errors about reading the camera feed. I'll dig a little deeper and see if I can figure it out.

 

I think that the upgrade caused the issue, but I am not sure how to fix it?

 

ERROR : rtsps://192.168.100.1:7441/uN84YwyHVF8TCCd8?enableSrtp: Invalid data found when processing

 

19 minutes ago, irishjd said:

I think that the upgrade caused the issue, but I am not sure how to fix it?

 

ERROR : rtsps://192.168.100.1:7441/uN84YwyHVF8TCCd8?enableSrtp: Invalid data found when processing

 

https://docs.frigate.video/configuration/camera_specific#unifi-protect-cameras

15 minutes ago, yayitazale said:

https://docs.frigate.video/configuration/camera_specific#unifi-protect-cameras

I made the changes, but am still getting lots of errors:

 

2023-11-24 14:19:49.675441963 [INFO] Starting Frigate... 2023-11-24 14:19:52.412526156 [2023-11-24 14:19:52] frigate.app INFO : Starting Frigate (0.12.1-367d724) 2023-11-24 14:19:52.510022406 [2023-11-24 14:19:52] peewee_migrate INFO : Starting migrations 2023-11-24 14:19:52.546997821 [2023-11-24 14:19:52] peewee_migrate INFO : There is nothing to migrate 2023-11-24 14:19:52.687207281 [2023-11-24 14:19:52] frigate.app INFO : Output process started: 2264 2023-11-24 14:19:52.695841386 [2023-11-24 14:19:52] detector.coral INFO : Starting detection process: 2262 2023-11-24 14:19:52.717823683 [2023-11-24 14:19:52] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2023-11-24 14:19:52.780520737 [2023-11-24 14:19:52] frigate.app INFO : Camera processor started for birdcam: 2268 2023-11-24 14:19:52.799918688 [2023-11-24 14:19:52] frigate.app INFO : Capture process started for birdcam: 2269 2023-11-24 14:19:53.802704985 [2023-11-24 14:19:53] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-11-24 14:19:53.803238872 [2023-11-24 14:19:53] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread... 2023-11-24 14:19:55.995242362 [2023-11-24 14:19:55] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2023-11-24 14:20:12.971534027 [2023-11-24 14:20:12] watchdog.birdcam ERROR : Ffmpeg process crashed unexpectedly for birdcam. 2023-11-24 14:20:12.987080852 [2023-11-24 14:20:12] watchdog.birdcam ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-11-24 14:20:12.987101206 [2023-11-24 14:20:12] ffmpeg.birdcam.detect ERROR : [NULL @ 0x558b766e7080] Unable to find a suitable output format for 'preset-record-ubiquity' 2023-11-24 14:20:12.987110986 [2023-11-24 14:20:12] ffmpeg.birdcam.detect ERROR : preset-record-ubiquity: Invalid argument 2023-11-24 14:20:13.833322204 [2023-11-24 14:20:13] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-11-24 14:20:13.833874954 [2023-11-24 14:20:13] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread... 2023-11-24 14:20:23.003874587 [2023-11-24 14:20:23] watchdog.birdcam ERROR : Ffmpeg process crashed unexpectedly for birdcam. 2023-11-24 14:20:23.020641863 [2023-11-24 14:20:23] watchdog.birdcam ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-11-24 14:20:23.020658577 [2023-11-24 14:20:23] ffmpeg.birdcam.detect ERROR : [rtsp @ 0x55dd07c67f40] DTS discontinuity in stream 1: packet 11 with DTS 81641146250828, packet 12 with DTS 81641146254016 2023-11-24 14:20:23.020667740 [2023-11-24 14:20:23] ffmpeg.birdcam.detect ERROR : [NULL @ 0x55dd07cecf40] Unable to find a suitable output format for 'preset-record-ubiquity' 2023-11-24 14:20:23.020675941 [2023-11-24 14:20:23] ffmpeg.birdcam.detect ERROR : preset-record-ubiquity: Invalid argument 2023-11-24 14:20:23.871868736 [2023-11-24 14:20:23] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-11-24 14:20:23.873335948 [2023-11-24 14:20:23] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread...

7 minutes ago, irishjd said:

I made the changes, but am still getting lots of errors:

 

2023-11-24 14:19:49.675441963 [INFO] Starting Frigate... 2023-11-24 14:19:52.412526156 [2023-11-24 14:19:52] frigate.app INFO : Starting Frigate (0.12.1-367d724) 2023-11-24 14:19:52.510022406 [2023-11-24 14:19:52] peewee_migrate INFO : Starting migrations 2023-11-24 14:19:52.546997821 [2023-11-24 14:19:52] peewee_migrate INFO : There is nothing to migrate 2023-11-24 14:19:52.687207281 [2023-11-24 14:19:52] frigate.app INFO : Output process started: 2264 2023-11-24 14:19:52.695841386 [2023-11-24 14:19:52] detector.coral INFO : Starting detection process: 2262 2023-11-24 14:19:52.717823683 [2023-11-24 14:19:52] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2023-11-24 14:19:52.780520737 [2023-11-24 14:19:52] frigate.app INFO : Camera processor started for birdcam: 2268 2023-11-24 14:19:52.799918688 [2023-11-24 14:19:52] frigate.app INFO : Capture process started for birdcam: 2269 2023-11-24 14:19:53.802704985 [2023-11-24 14:19:53] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-11-24 14:19:53.803238872 [2023-11-24 14:19:53] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread... 2023-11-24 14:19:55.995242362 [2023-11-24 14:19:55] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2023-11-24 14:20:12.971534027 [2023-11-24 14:20:12] watchdog.birdcam ERROR : Ffmpeg process crashed unexpectedly for birdcam. 2023-11-24 14:20:12.987080852 [2023-11-24 14:20:12] watchdog.birdcam ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-11-24 14:20:12.987101206 [2023-11-24 14:20:12] ffmpeg.birdcam.detect ERROR : [NULL @ 0x558b766e7080] Unable to find a suitable output format for 'preset-record-ubiquity' 2023-11-24 14:20:12.987110986 [2023-11-24 14:20:12] ffmpeg.birdcam.detect ERROR : preset-record-ubiquity: Invalid argument 2023-11-24 14:20:13.833322204 [2023-11-24 14:20:13] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-11-24 14:20:13.833874954 [2023-11-24 14:20:13] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread... 2023-11-24 14:20:23.003874587 [2023-11-24 14:20:23] watchdog.birdcam ERROR : Ffmpeg process crashed unexpectedly for birdcam. 2023-11-24 14:20:23.020641863 [2023-11-24 14:20:23] watchdog.birdcam ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-11-24 14:20:23.020658577 [2023-11-24 14:20:23] ffmpeg.birdcam.detect ERROR : [rtsp @ 0x55dd07c67f40] DTS discontinuity in stream 1: packet 11 with DTS 81641146250828, packet 12 with DTS 81641146254016 2023-11-24 14:20:23.020667740 [2023-11-24 14:20:23] ffmpeg.birdcam.detect ERROR : [NULL @ 0x55dd07cecf40] Unable to find a suitable output format for 'preset-record-ubiquity' 2023-11-24 14:20:23.020675941 [2023-11-24 14:20:23] ffmpeg.birdcam.detect ERROR : preset-record-ubiquity: Invalid argument 2023-11-24 14:20:23.871868736 [2023-11-24 14:20:23] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-11-24 14:20:23.873335948 [2023-11-24 14:20:23] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread...

preset-record-ubiquity -> preset-record-ubiquiti

It’s always the little things that get me ;-)

 

The errors are gone, but the bird species are still not being identified.

18 hours ago, irishjd said:

The errors are gone, but the bird species are still not being identified.

With such little info I can't help you...

Understood... I guess if you could give me some guidance on what to look for that would be preventing the species identification, I would appreciate it.

38 minutes ago, irishjd said:

Understood... I guess if you could give me some guidance on what to look for that would be preventing the species identification, I would appreciate it.

First of all, look at the logs both in Frigate and WhosAtMyFeeder. Recheck the configuration of WhosAtMyFeeder and the modifications needed on Frigate on each camera setup to work alongside WhosAtMyFeeder. Cheack if the snapshots of frigate are being created properly. Check if bird detections are beeing recieved by WhosAtMyFeeder. If all those things are working, check if the camera resolutions/snapshot resolutions and camera stream formats are yet correct after that upgrade of the camera firmware.

So this is intersting... when I restart Frigate, I don't see any errors for about an hour, and then I get flooded with ffmpeg errors. I have attached the logs as a txt file as it is pretty long. Not sure if this is my identification issue, but it can't be helping.

frigate_errors.txt

35 minutes ago, irishjd said:

So this is intersting... when I restart Frigate, I don't see any errors for about an hour, and then I get flooded with ffmpeg errors. I have attached the logs as a txt file as it is pretty long. Not sure if this is my identification issue, but it can't be helping.

frigate_errors.txt 58.68 kB · 0 downloads

What are the go2rtc logs?

1 minute ago, yayitazale said:

What are the go2rtc logs?

2023-11-27 12:08:09.476530682 [INFO] Preparing go2rtc config... 2023-11-27 12:08:10.481179811 [INFO] Starting go2rtc... 2023-11-27 12:08:10.580649110 12:08:10.580 INF go2rtc version 1.2.0 linux/amd64 2023-11-27 12:08:10.581225710 12:08:10.581 INF [api] listen addr=:1984 2023-11-27 12:08:10.581607540 12:08:10.581 INF [rtsp] listen addr=:8554 2023-11-27 12:08:10.581993904 12:08:10.581 INF [srtp] listen addr=:8443 2023-11-27 12:08:10.582342250 12:08:10.582 INF [webrtc] listen addr=:8555 2023-11-27 12:08:19.577191038 [INFO] Starting go2rtc healthcheck service...

1 minute ago, irishjd said:

2023-11-27 12:08:09.476530682 [INFO] Preparing go2rtc config... 2023-11-27 12:08:10.481179811 [INFO] Starting go2rtc... 2023-11-27 12:08:10.580649110 12:08:10.580 INF go2rtc version 1.2.0 linux/amd64 2023-11-27 12:08:10.581225710 12:08:10.581 INF [api] listen addr=:1984 2023-11-27 12:08:10.581607540 12:08:10.581 INF [rtsp] listen addr=:8554 2023-11-27 12:08:10.581993904 12:08:10.581 INF [srtp] listen addr=:8443 2023-11-27 12:08:10.582342250 12:08:10.582 INF [webrtc] listen addr=:8555 2023-11-27 12:08:19.577191038 [INFO] Starting go2rtc healthcheck service...

Ok, you should ask on github this is out of my knowledge

Thanks for looking at it!

Hi,

I have in my unraid HA, Mqtt and Frigate running. And all work fine. I get the topic frigate/ in mqtt and I can manually add stuff from frigate via mqtt in HA, i.e.:

 # Frigate
  - unique_id: frigate_front_door_pd
    name: "Frigate front door Person Detected"
    topic: "frigate/front_door/person/snapshot" 

 

But I cannot figure out how to autmatically discover the frigate stuff in HA. I know I should install the frigate Integration but I don't know how. Please could someone help me figure this out? In Integrations it doesn't show.