April 3, 20242 yr 14 hours ago, yayitazale said: You are missing the usb passtrough. I suggest you to start again with a clean template without deleting this: Also, I see in the config file that you are trying to use a yolo model with the coral and that is not posible. As you can read in the docs, the best option is to use the default model that is just fine, so you should comment or delete this part: model: path: /config/model_cache/tensorrt/yolov7-320.trt input_tensor: nchw input_pixel_format: rgb width: 320 height: 320 Yolo models are great for nvidia or openvino detectors, but the coral is a different chip that has its own requirements to create a model. If you want to use another custom modelwith the coral, it must be a tflite model. You can find here most of the pretrained models. It was the model I had configured for when I was using the GPU. I commented this part out and its working! Thanks very much for your help
April 3, 20242 yr --gpus=all --shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=100000000 --restart unless-stopped Can someone explain what the --gpus=all part does of the above Extra Parameters? When is it necessary / useful as its not in the default ?
April 4, 20242 yr 18 hours ago, yayitazale said: Frigate template is pointing to the "latest" tag so yo you should check if you have change that. Any way, you should reads the changelog and the updated docs to find out what changes you need to make to your settings has there are many new things. Also it is recommended to ensure that you are using all the required new variables in the template or reinstall it from scratch deleting you actual container. Thanks, you're right. It turns out my Community Apps didn't update, which then caused the Docker page to show everything uptodate when they are not.
April 4, 20242 yr Author 12 hours ago, awediohead said: --gpus=all --shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=100000000 --restart unless-stopped Can someone explain what the --gpus=all part does of the above Extra Parameters? When is it necessary / useful as its not in the default ? That parameter is the proposed one to launch frigate with docker-run with a nvidia gpu pass-trough: https://docs.frigate.video/configuration/hardware_acceleration#docker-run-cli---nvidia-gpu As we are on Unraid, there is a more "standar" way to pass-trough defined on the nvidia driver plugin, and it is the one implemented on the template: Edited April 4, 20242 yr by yayitazale
April 4, 20242 yr Thanks for clarifying and confirming it's not something I need for now. It had been suggested to me as necessary previously, hence my question to double check. Cheers
April 14, 20242 yr On 4/4/2024 at 1:59 PM, yayitazale said: That parameter is the proposed one to launch frigate with docker-run with a nvidia gpu pass-trough: https://docs.frigate.video/configuration/hardware_acceleration#docker-run-cli---nvidia-gpu As we are on Unraid, there is a more "standar" way to pass-trough defined on the nvidia driver plugin, and it is the one implemented on the template: Actually I have a question regarding this as frigate in my case seems to "grab" all GPUs available and this is what i do NOT want. I have some dedicated GPUs for VMs and if frigate uses those GPUs the VMs won't start, therefore I want to limit frigate to just one GPU. But somehow this seems impossible to me: here's my Frigate Docker Config: docker run -d --name='frigate' --net='host' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Server" -e HOST_CONTAINERNAME="frigate" -e 'TCP_PORT_5000'='5000' -e 'TCP_PORT_8554'='8554' -e 'FRIGATE_RTSP_PASSWORD'='***' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-bd161e6e-9b15-d71a-ec49-8c085ea02ad1' -e 'NVIDIA_DRIVER_CAPABILITIES'='compute,utility,video' -e 'TCP_PORT_8555'='8555' -e 'UDP_PORT_8555'='8555' -e 'TCP_PORT_1984'='1984' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5000]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/yayitazale/unraid-templates/main/frigate.png' -v '/mnt/user/appdata/frigate':'/config':'rw' -v '/mnt/user/Media/frigate':'/media/frigate':'rw' -v '/etc/localtime':'/etc/localtime':'rw' --device='/dev/bus/usb/006/002' --runtime=nvidia --shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --restart unless-stopped 'ghcr.io/blakeblackshear/frigate:stable' 440515ff723a15052068c74656fef26f189832b762fe93eb1766155f8130e599 The command finished successfully! The only way is to start the VMs before I start frigate - this is not an option for me. With this config and one VM started before frigate, frigate still shows up 2 GPUs: Please how can i remove the rtx 3060? Or in other words how can i limit frigate to the 1030? The 1030 has the GPU id mentioned above in the frigate docker config. Thank you for your advice!
April 18, 20242 yr On 4/3/2024 at 4:12 AM, slashgob said: It was the model I had configured for when I was using the GPU. I commented this part out and its working! Thanks very much for your help Good looking out! I bet this was my issue all along.
April 21, 20242 yr Author On 4/14/2024 at 10:41 PM, Zeze21 said: Actually I have a question regarding this as frigate in my case seems to "grab" all GPUs available and this is what i do NOT want. I have some dedicated GPUs for VMs and if frigate uses those GPUs the VMs won't start, therefore I want to limit frigate to just one GPU. But somehow this seems impossible to me: here's my Frigate Docker Config: docker run -d --name='frigate' --net='host' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Server" -e HOST_CONTAINERNAME="frigate" -e 'TCP_PORT_5000'='5000' -e 'TCP_PORT_8554'='8554' -e 'FRIGATE_RTSP_PASSWORD'='***' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-bd161e6e-9b15-d71a-ec49-8c085ea02ad1' -e 'NVIDIA_DRIVER_CAPABILITIES'='compute,utility,video' -e 'TCP_PORT_8555'='8555' -e 'UDP_PORT_8555'='8555' -e 'TCP_PORT_1984'='1984' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5000]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/yayitazale/unraid-templates/main/frigate.png' -v '/mnt/user/appdata/frigate':'/config':'rw' -v '/mnt/user/Media/frigate':'/media/frigate':'rw' -v '/etc/localtime':'/etc/localtime':'rw' --device='/dev/bus/usb/006/002' --runtime=nvidia --shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --restart unless-stopped 'ghcr.io/blakeblackshear/frigate:stable' 440515ff723a15052068c74656fef26f189832b762fe93eb1766155f8130e599 The command finished successfully! The only way is to start the VMs before I start frigate - this is not an option for me. With this config and one VM started before frigate, frigate still shows up 2 GPUs: Please how can i remove the rtx 3060? Or in other words how can i limit frigate to the 1030? The 1030 has the GPU id mentioned above in the frigate docker config. Thank you for your advice! Did you tried with privileged = false?
April 23, 20242 yr So after running both the Coral with 12th Gen Intel QSV and Nvidia Quadro RTX 4000 for Frigate processing for some time, the Coral/Intel setup significantly uses less power and generates much less heat than the Nvidia method. Overall, this resulted in 100watt less power usage and Quadro RTX 4000 is no longer running a constant 60C. Unrelated to unRAID but kind of wondering how the HA Yellow/RP4 would handle Frigate with Coral attached, I know others are doing it but just unsure about how many cameras and what not they are able to handle. Edited April 23, 20242 yr by BrandonG777
April 23, 20242 yr Quick question. I have removed my gpu as I do not needit anymore. Removed the gpus all and device object from the container config. All working fine. I have an amd 3400g. Will it use the integrated graphics of this cpu automatically or do I need to add an extra parameter? error-gpu There was an error getting usage stats. This does not mean hardware acceleration is not working. Either your GPU does not support this or Frigate does not have proper access to get statistics. This is expected for the Home Assistant addon. UPDATE: Fixed. Added variable radeonsi amd-vaapi GPU %Memory % 2.50%19.27% Edited April 23, 20242 yr by only-university6482
April 24, 20242 yr Quick question. I have removed my gpu as I do not needit anymore. Removed the gpus all and device object from the container config. All working fine. I have an amd 3400g. Will it use the integrated graphics of this cpu automatically or do I need to add an extra parameter? error-gpu There was an error getting usage stats. This does not mean hardware acceleration is not working. Either your GPU does not support this or Frigate does not have proper access to get statistics. This is expected for the Home Assistant addon. UPDATE: Fixed. Added variable radeonsi amd-vaapi GPU %Memory % 2.50%19.27%You will need to change your config though I’ve not worked through getting an AMD cpu/gpu setup with Frigate. However, there are example config you can copy from the frigate site. I believe what you are looking for is VAAPI or something like that. Sent from my iPhone using Tapatalk
April 27, 20242 yr Hi! I had frigate running with a reolink doorbell with no problems and today out of nowhere the setup broke and now I can't get it to work on frigate but in the app it's fine. Here's the config that I had: go2rtc: streams: doorbell: - "ffmpeg:http://192.168.50.19/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&xxxxxxxxxxxx=password#video=copy#audio=copy#audio=opus" - rtsp://192.168.50.19/Preview_01_sub doorbell_sub: - "ffmpeg:http://192.168.50.19/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&xxxxxxxxxxxx=password" cameras: doorbell: ffmpeg: inputs: - path: rtsp://frigate:[email protected]:554/h264Preview_01_sub input_args: preset-rtsp-restream roles: - detect - path: rtsp://frigate:[email protected]:554/h265Preview_01_main input_args: preset-rtsp-restream roles: - record logs: 2024-04-27 15:03:11.017068884 [2024-04-27 15:03:11] frigate.video ERROR : doorbell: Unable to read frames from ffmpeg process. 2024-04-27 15:03:11.017109822 [2024-04-27 15:03:11] frigate.video ERROR : doorbell: ffmpeg process is not running. exiting capture thread... 2024-04-27 15:03:20.843099157 [2024-04-27 15:03:20] watchdog.doorbell ERROR : Ffmpeg process crashed unexpectedly for doorbell. 2024-04-27 15:03:20.843155865 [2024-04-27 15:03:20] watchdog.doorbell ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-04-27 15:03:20.843184840 [2024-04-27 15:03:20] ffmpeg.doorbell.detect ERROR : [tcp @ 0x5581eaf5fe40] Connection to tcp://192.168.50.19:554?timeout=5000000 failed: Connection refused 2024-04-27 15:03:20.843212273 [2024-04-27 15:03:20] ffmpeg.doorbell.detect ERROR : rtsp://*:*@192.168.50.19:554/h264Preview_01_sub: Connection refused 2024-04-27 15:03:20.855825405 [2024-04-27 15:03:20] ffmpeg.doorbell.record ERROR : [tcp @ 0x5625c0c0ef40] Connection to tcp://192.168.50.19:554?timeout=5000000 failed: Connection refused 2024-04-27 15:03:20.855858357 [2024-04-27 15:03:20] ffmpeg.doorbell.record ERROR : rtsp://*:*@192.168.50.19:554/h265Preview_01_main: Connection refused 2024-04-27 15:03:20.855894266 [2024-04-27 15:03:20] watchdog.doorbell INFO : Terminating the existing ffmpeg process... 2024-04-27 15:03:20.855928000 [2024-04-27 15:03:20] watchdog.doorbell INFO : Waiting for ffmpeg to exit and now the changes that still don't work: go2rtc: streams: doorbell: - "ffmpeg:http://192.168.50.19/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=xxxxxxxxxx#video=copy#audio=copy#audio=opus" - rtsp://192.168.50.19/Preview_01_sub doorbell_sub: - "ffmpeg:http://192.168.50.19/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=xxxxxxxxxxx" cameras: doorbell: ffmpeg: inputs: - path: rtsp://192.168.50.233:8554/doorbell_sub input_args: preset-rtsp-restream roles: - detect - path: rtsp://192.168.50.233:8554/doorbell input_args: preset-rtsp-restream roles: - record logs: 2024-04-27 14:57:04.420341977 [2024-04-27 14:57:04] frigate.video ERROR : doorbell: Unable to read frames from ffmpeg process. 2024-04-27 14:57:04.420386843 [2024-04-27 14:57:04] frigate.video ERROR : doorbell: ffmpeg process is not running. exiting capture thread... 2024-04-27 14:57:23.356757523 [2024-04-27 14:57:23] watchdog.doorbell ERROR : Ffmpeg process crashed unexpectedly for doorbell. 2024-04-27 14:57:23.356818930 [2024-04-27 14:57:23] watchdog.doorbell ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-04-27 14:57:23.356867863 [2024-04-27 14:57:23] ffmpeg.doorbell.detect ERROR : [rtsp @ 0x558cb0f31c40] method DESCRIBE failed: 404 Not Found 2024-04-27 14:57:23.356909863 [2024-04-27 14:57:23] ffmpeg.doorbell.detect ERROR : rtsp://192.168.50.233:8554/doorbell_sub: Server returned 404 Not Found 2024-04-27 14:57:23.376084347 [2024-04-27 14:57:23] ffmpeg.doorbell.record ERROR : [rtsp @ 0x563b3bcbfd80] method DESCRIBE failed: 404 Not Found 2024-04-27 14:57:23.376185961 [2024-04-27 14:57:23] ffmpeg.doorbell.record ERROR : rtsp://192.168.50.233:8554/doorbell: Server returned 404 Not Found 2024-04-27 14:57:23.376231718 [2024-04-27 14:57:23] watchdog.doorbell INFO : Terminating the existing ffmpeg process... 2024-04-27 14:57:23.376264420 [2024-04-27 14:57:23] watchdog.doorbell INFO : Waiting for ffmpeg to exit gracefully... don't really know If the first config was fine and something else happened, can anyone help? Edited April 28, 20242 yr by renk1
April 28, 20242 yr On 4/21/2024 at 8:14 PM, yayitazale said: Did you tried with privileged = false? That solved it! Thank you. Another thing: When I look at the frigate container in doozle it uses ~150% of the CPU while basically all other containers use less than 10%. Can I reduce the cpu thirst of frigate
April 28, 20242 yr 2 hours ago, Zeze21 said: When I look at the frigate container in doozle it uses ~150% of the CPU Frigate uses CPU for its motion detection. Perhaps use masks to cover leaves, branches etc that could be triggering it.
April 29, 20242 yr That solved it! Thank you. Another thing: When I look at the frigate container in doozle it uses ~150% of the CPU while basically all other containers use less than 10%. Can I reduce the cpu thirst of frigateDid you setup a substream (720p 5fps or lower resolution) I see around 20% constant usage on my i5-12500 but I have 8 cameras being monitored and also using a Coral USB. Also something to think about, your wifi doorbell will have a constant video stream running across your wifi which could adversely affect wifi performance. I originally did this with my Amcrest/Wyze doorbells. Ended up just adding another analog camera through my Amcrest DVR for $25. This also prevents a blind spot for my packages being put directly under the doorbell cams. When I started this project I thought I had to convert all my cams to POE digital cams but analog video at 720p still works great and pricing on a good analog DVR is less than $100 these days. Highly recommend Amcrest but full disclosure, I’ve reviewed their devices for years which they have provided at no cost.Sent from my iPhone using Tapatalk
May 8, 20242 yr has anybody else been having trouble with their home assistant integration failing to connect to their frigate instance hosted on their unraid server? i triple-checked and made sure that everything's updated. this stopped working a couple weeks (ish?) ago and i haven't been able to figure out what broke it.
May 8, 20242 yr 8 hours ago, computergreek said: has anybody else been having trouble with their home assistant integration failing to connect to their frigate instance hosted on their unraid server? i triple-checked and made sure that everything's updated. this stopped working a couple weeks (ish?) ago and i haven't been able to figure out what broke it. Nope not here - Integrates with homassistant without issues
May 8, 20242 yr 4 hours ago, only-university6482 said: Nope not here - Integrates with homassistant without issues Other than the occasional push notification that fails to send the attached image, it works much better than RTMP streams.
May 12, 20242 yr Hi i been struggling with one of my Reolink cameras keeps on crashing out since recent updates.The other 3 cameras work fine with exactly the same settings Quote 2024-05-12 16:27:04.028133288 [2024-05-12 16:27:04] watchdog.garage INFO : Terminating the existing ffmpeg process... 2024-05-12 16:27:04.028171590 [2024-05-12 16:27:04] watchdog.garage INFO : Waiting for ffmpeg to exit gracefully... 2024-05-12 16:27:14.045188548 [2024-05-12 16:27:14] watchdog.garage ERROR : No new recording segments were created for garage in the last 120s. restarting the ffmpeg record process... Any ideas what the issue is ?
May 28, 20242 yr I'm having a daily problem with my frigate where it starts to have problems with generally two cameras (RUA ESQUERDA and POSTE), both cameras have FFMPEG errors I believe, it must be something in the configuration that I don't know how to do correctly. RUA ESUQUERDA is a Hikvision 4k camera model DS-2CD2387G2-LU and POSTE is a Sony 5MP PTZ camera. Could anyone give me a hint as to why every day when I look at the logs and config I have these errors? The Frigate even restarts itself to correct errors. I would greatly appreciate it if anyone could give me some suggestions to correct this problem that affects my recordings every day. LOG: 2024-05-27 21:34:18.688780742 [2024-05-27 21:34:18] ffmpeg.rua_esquerda.detect ERROR : [rtsp @ 0x560f8d6d1e40] method DESCRIBE failed: 404 Not Found 2024-05-27 21:34:18.688787678 [2024-05-27 21:34:18] ffmpeg.rua_esquerda.detect ERROR : rtsp://127.0.0.1:8554/rua_esquerda_sub: Server returned 404 Not Found 2024-05-27 21:34:18.697986332 [2024-05-27 21:34:18] ffmpeg.rua_esquerda.record ERROR : rtsp://127.0.0.1:8554/rua_esquerda?video&audio#?video=copy&audio=copy: Invalid data found when processing input 2024-05-27 21:34:18.697999926 [2024-05-27 21:34:18] watchdog.rua_esquerda INFO : Terminating the existing ffmpeg process... 2024-05-27 21:34:18.698012297 [2024-05-27 21:34:18] watchdog.rua_esquerda INFO : Waiting for ffmpeg to exit gracefully... 2024-05-27 21:34:20.315024489 21:34:20.314 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1, dial tcp 192.168.0.26:554: connect: no route to host" stream=rua_esquerda 2024-05-27 21:34:21.790244449 21:34:21.790 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, dial tcp 192.168.0.26:554: connect: no route to host" stream=rua_esquerda_sub 2024-05-27 21:34:21.791386603 [2024-05-27 21:34:21] frigate.video ERROR : rua_esquerda: Unable to read frames from ffmpeg process. 2024-05-27 21:34:21.791412414 [2024-05-27 21:34:21] frigate.video ERROR : rua_esquerda: ffmpeg process is not running. exiting capture thread... 2024-05-27 21:34:25.426033835 21:34:25.425 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:34:28.705357314 [2024-05-27 21:34:28] watchdog.rua_esquerda ERROR : Ffmpeg process crashed unexpectedly for rua_esquerda. 2024-05-27 21:34:28.705455689 [2024-05-27 21:34:28] watchdog.rua_esquerda ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-05-27 21:34:28.705458298 [2024-05-27 21:34:28] ffmpeg.rua_esquerda.detect ERROR : [rtsp @ 0x563d10856e40] method DESCRIBE failed: 404 Not Found 2024-05-27 21:34:28.705459532 [2024-05-27 21:34:28] ffmpeg.rua_esquerda.detect ERROR : rtsp://127.0.0.1:8554/rua_esquerda_sub: Server returned 404 Not Found 2024-05-27 21:34:28.714526347 [2024-05-27 21:34:28] ffmpeg.rua_esquerda.record ERROR : rtsp://127.0.0.1:8554/rua_esquerda?video&audio#?video=copy&audio=copy: Invalid data found when processing input 2024-05-27 21:34:28.714559048 [2024-05-27 21:34:28] watchdog.rua_esquerda INFO : Terminating the existing ffmpeg process... 2024-05-27 21:34:28.714580085 [2024-05-27 21:34:28] watchdog.rua_esquerda INFO : Waiting for ffmpeg to exit gracefully... 2024-05-27 21:34:30.535760855 21:34:30.535 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: no route to host, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:34:40.887557403 21:34:40.887 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1, dial tcp 192.168.0.26:554: connect: no route to host" stream=rua_esquerda 2024-05-27 21:34:40.887585019 21:34:40.887 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:225 > error="write tcp 127.0.0.1:8554->127.0.0.1:55526: write: broken pipe" 2024-05-27 21:34:45.997629452 21:34:45.997 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:34:51.106756813 21:34:51.106 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:34:59.291877286 21:34:59.291 WRN [streams] json locked 2024-05-27 21:35:01.326830025 21:35:01.326 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: no route to host, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:06.436519295 21:35:06.436 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:06.436542498 21:35:06.436 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:225 > error="write tcp 127.0.0.1:8554->127.0.0.1:56054: write: broken pipe" 2024-05-27 21:35:11.547261036 21:35:11.547 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: no route to host, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:21.766576106 21:35:21.766 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: no route to host, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:26.876060191 21:35:26.875 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: connection refused, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:26.876092691 21:35:26.876 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:225 > error="write tcp 127.0.0.1:8554->127.0.0.1:39170: write: broken pipe" 2024-05-28 05:11:23.852439638 [2024-05-28 05:11:23] frigate.record.maintainer WARNING : Discarding a corrupt recording segment: /tmp/cache/[email protected] 2024-05-28 05:11:29.207705993 [2024-05-28 05:11:29] watchdog.poste INFO : poste exceeded fps limit. Exiting ffmpeg... 2024-05-28 05:11:29.207798735 [2024-05-28 05:11:29] watchdog.poste INFO : Waiting for ffmpeg to exit gracefully... 2024-05-28 05:12:00.000561366 05:11:59.991 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url=ffmpeg:rtsp://admin:[email protected]:554/1/h264major#video=copy 2024-05-28 05:12:00.463240751 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466337848 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466560764 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466563639 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466564850 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466565866 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466566922 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466567954 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466569045 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466570070 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466658345 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466659555 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466662726 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466663813 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466664850 [2024-05-28 05:12:00] frigate.video ERROR : poste: ffmpeg process is not running. exiting capture thread... 2024-05-28 05:12:09.667740257 [2024-05-28 05:12:09] frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for poste. Keeping the 6 most recent segments out of 7 and discarding the rest... 2024-05-28 05:12:10.466555950 [2024-05-28 05:12:10] watchdog.poste ERROR : Ffmpeg process crashed unexpectedly for poste. 2024-05-28 05:12:10.466707241 [2024-05-28 05:12:10] watchdog.poste ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-05-28 05:12:10.466709198 [2024-05-28 05:12:10] ffmpeg.poste.detect ERROR : [out_0_0 @ 0x563d23336a00] 100 buffers queued in out_0_0, something may be wrong. 2024-05-28 05:12:10.466710244 [2024-05-28 05:12:10] ffmpeg.poste.detect ERROR : [out_0_0 @ 0x563d23336a00] 1000 buffers queued in out_0_0, something may be wrong. 2024-05-28 05:12:10.466718538 [2024-05-28 05:12:10] ffmpeg.poste.detect ERROR : [out_0_0 @ 0x563d23336a00] 10000 buffers queued in out_0_0, something may be wrong. 2024-05-28 05:12:14.667533615 [2024-05-28 05:12:14] frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for poste. Keeping the 6 most recent segments out of 7 and discarding the rest... 2024-05-28 05:12:19.668149232 [2024-05-28 05:12:19] frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for poste. Keeping the 6 most recent segments out of 7 and discarding the rest... 2024-05-28 06:13:10.561090443 [2024-05-28 06:13:10] watchdog.poste ERROR : No new recording segments were created for poste in the last 120s. restarting the ffmpeg record process... CONFIG: mqtt: host: 192.168.0.50 port: 1883 user: admin password: admin detectors: coral: type: edgetpu device: usb birdseye: enabled: false ffmpeg: hwaccel_args: preset-vaapi go2rtc: streams: #------------------ porteiro: - ffmpeg:rtsp://admin:[email protected]:554/h264/ch01/main/av_stream - "ffmpeg:porteiro#audio=opus" #------------------ poste: - "ffmpeg:rtsp://admin:[email protected]:554/1/h264major#video=copy" poste_sub: - rtsp://admin:[email protected]:554/1/h264minor #------------------ rua_esquerda: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 - "ffmpeg:rua_esquerda#audio=opus" rua_esquerda_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ telhado: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 - "ffmpeg:telhado#audio=opus" telhado_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ quintal: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 quintal_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ corredor: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 - "ffmpeg:corredor#audio=opus" corredor_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ quintal_atras: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 quintal_atras_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ fundos: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 - "ffmpeg:fundos#audio=opus" fundos_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ webrtc: candidates: - 192.168.0.50:8555 - stun:8555 ports: - 8555:8555/tcp # WebRTC over tcp - 8555:8555/udp # WebRTC over udp - 5000:5000 - 1935:1935 - 8554:8554 cameras: #-------------------------------------------------------------------------------------POSTE poste: ffmpeg: output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/poste input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/poste_sub input_args: preset-rtsp-restream roles: - detect onvif: host: 192.168.0.20 port: 8999 user: admin password: password detect: width: 720 height: 576 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - car - person filters: car: mask: - 720,0,0,0,0,119,331,116,366,202,720,389 person: mask: - 0,114,0,0,720,0,720,167,422,104,358,195,335,118 zones: calçada_poste: coordinates: 0,576,720,576,720,156,412,97,354,198,338,115,0,120 motion: mask: - 0,114,330,116,359,198,410,103,720,172,720,0,0,0 ui: order: 1 #-------------------------------------------------------------------------------------PORTEIRO porteiro: ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/porteiro?video=copy&audio=copy input_args: preset-rtsp-restream roles: - record - detect detect: width: 1280 height: 720 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person filters: person: mask: - 1194,415,1134,409,1147,539,1188,528 - 105,501,57,498,60,442,98,442 zones: frente_porteiro: coordinates: 0,720,1280,720,1280,320,0,169 motion: mask: - 1280,381,1280,0,0,0,0,249 ui: order: 2 #-------------------------------------------------------------------------------------RUA_ESQUERDA rua_esquerda: ffmpeg: output_args: record: preset-record-generic-audio-copy inputs: - path: rtsp://127.0.0.1:8554/rua_esquerda?video&audio input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/rua_esquerda_sub input_args: preset-rtsp-restream roles: - detect detect: width: 1280 height: 720 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person - car - motorcycle - bicycle filters: car: mask: - 1280,158,1280,0,0,0,0,124,957,93,985,150 - 828,204,864,190,859,137,815,147 - 168,418,469,314,428,283,166,362 person: mask: - 1280,0,1280,157,975,147,957,0 - 658,134,666,209,627,231,616,135 zones: ruaesquerda_frente: coordinates: 1280,166,836,93,543,108,0,256,0,720,1280,720 motion: mask: - 794,95,771,193,737,198,702,89,0,245,0,0,1280,0,1280,161,936,154,937,90 ui: order: 3 #-------------------------------------------------------------------------------------TELHADO telhado: ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/telhado?video=copy&audio=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/telhado_sub input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person - car filters: car: mask: - 640,0,640,480,510,370,358,0 person: mask: - 437,401,506,441,618,223,580,131 zones: telhado_entr: coordinates: 640,480,640,126,575,0,0,0,0,480 motion: mask: - 474,0,484,24,579,23,640,121,640,0 - 528,480,640,480,640,391 ui: order: 4 #-------------------------------------------------------------------------------------QUINTAL quintal: ffmpeg: output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/quintal?video=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/quintal_sub?video=copy input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person filters: person: mask: - 640,0,640,480,640,306,227,99,150,0 zones: quintal_frente: coordinates: 0,480,0,64,217,0,245,107,640,305,640,480 saida_de_pessoas: coordinates: 0,480,640,480,640,309,473,226,0,310 motion: mask: - 640,0,151,0,245,123,640,320 ui: order: 5 #-------------------------------------------------------------------------------------CORREDOR corredor: ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/corredor?video=copy&audio=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/corredor_sub input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person zones: corredor_lateral: coordinates: 640,221,0,0,0,480,640,480 casa_vizinho: coordinates: 640,230,640,0,118,0,69,61 ui: order: 6 #-------------------------------------------------------------------------------------QUINTAL_ATRAS quintal_atras: ffmpeg: output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/quintal_atras?video=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/quintal_atras_sub?video=copy input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person zones: quint_at: coordinates: 0,480,0,194,225,0,640,0,640,480 motion: mask: - 0,0,0,207,261,0 ui: order: 7 #-------------------------------------------------------------------------------------FUNDOS fundos: ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/fundos?video=copy&audio=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/fundos_sub input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person zones: fundos_mato: coordinates: 640,0,0,97,0,480,640,480 motion: mask: - 640,0,640,45,117,36,0,114,0,0 - 363,279,135,412,98,252,94,62,241,0 - 401,480,640,480,640,309,534,319,474,342 ui: order: 8 Edited May 28, 20242 yr by Krypto5 change
June 11, 20242 yr Is there a dev alias for beta releases or is the only way to point to the 14.X branch with a specific release like? ghcr.io/blakeblackshear/frigate:0.14.0-beta2 Currently, I'm using ghcr.io/blakeblackshear/frigate:stable Would maybe like to try the new UI.
June 13, 20242 yr Author On 6/11/2024 at 5:54 AM, foo_fighter said: Is there a dev alias for beta releases or is the only way to point to the 14.X branch with a specific release like? ghcr.io/blakeblackshear/frigate:0.14.0-beta2 Currently, I'm using ghcr.io/blakeblackshear/frigate:stable Would maybe like to try the new UI. You can test it installing a new instance and changing the the branch manually, but I suggest you to copy the config folder, this is my actual test template: I have already prepared a new template that will be published when v14 is published as stable: https://gitlab.com/yayitazale/unraid-templates/-/merge_requests/7 This will require a app reinstall to meet the new port mapping.
June 13, 20242 yr 3 hours ago, yayitazale said: You can test it installing a new instance and changing the the branch manually, but I suggest you to copy the config folder, this is my actual test template: I have already prepared a new template that will be published when v14 is published as stable: https://gitlab.com/yayitazale/unraid-templates/-/merge_requests/7 This will require a app reinstall to meet the new port mapping. Thanks, this is exactly what I did. I created a frigate14 instance and frigate14 dirs by copying from the previous dirs. Looking forward to when this becomes stable. One other quick Q: In V13, there was a diagnostic view that displayed XGB/Hr from each camera. I don't see this in V14, will it return eventually? It was useful to dial in some settings when some Cams were 2GB/hr and some 1GB/hr.
June 14, 20242 yr hello, trying to install frigate but it wont start ok the problem is that im stupid Edited June 14, 20242 yr by VolzanIT
June 14, 20242 yr I aming have problem starting Frigate NV after installing Tapo cameras. The streams work on VLC , however when i add a rtsp i receive errors in config.yml. Could some advise where the error is in config. please see logs and current logs; config.ymlconfig.yml_frigate_logs (1).txt.crdownload Any help would be appreciated as i have looking for days and i must be missing something.
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.