0.12.0 Release Candidate 2 #5771
Replies: 8 comments 49 replies
-
|
I have created a short survey for those that are using the new OpenVINO and TensorRT detectors. It will aid in understanding the expected performance for different devices and help identify other issues that may be occurring. Thanks! Answers can be seen here |
Beta Was this translation helpful? Give feedback.
-
|
Are there any changes from Beta 10 to RC1? |
Beta Was this translation helpful? Give feedback.
-
no i use frigate web interface i stopt the webrtc card for now that works fine i only mentioned that because it works. im using ngnix proxy the frigate webinterface when i go to frigate on 4g it works perfect on local network it stops after 60sec |
Beta Was this translation helpful? Give feedback.
-
|
sorry but i dont know what i should change here for host network. |
Beta Was this translation helpful? Give feedback.
-
|
right, but I need to know which version of the webrtc card you are running to understand the situation better. You can get that information from the HA UI. to set host mode you add |
Beta Was this translation helpful? Give feedback.
-
|
V3.1.0. of the webrtc camera card in home assistant but host seems to fix the issue. ill test some more but thanks for helping. |
Beta Was this translation helpful? Give feedback.
-
|
@DrSpaldo, good question, good to see we moved on from beta versions. |
Beta Was this translation helpful? Give feedback.
-
|
Might need some help here. Warnings at the bottom are of concern. 2023-03-28 11:03:32.634210577 [2023-03-28 11:03:32] frigate.http ERROR : Exception on /Frontdoor/latest.jpg [GET] |
Beta Was this translation helpful? Give feedback.
-
There is also some useful information on this issue here. Nick very kindly built a one off testing build with the cache size increased, but you may have another issue still. I had to change my NAS to use NFS instead of CIFS/SMB/SAMBA shares and that almost but not quite resolved the issue. At least I haven't had any recording losses since in conjunction with Nick's custom Frigate build. Fingers crossed I don't get any and it helps you! Don't ignore it, you might miss out an important recording which is the very least you need in a CCTV solution! |
Beta Was this translation helpful? Give feedback.
-
|
2023-03-30 12:07:44.651076899 [2023-03-30 12:07:44] frigate.record DEBUG : Copied /media/frigate/recordings/2023-03-30/01/Rightside/07.33.mp4 in 0.1135549545288086 seconds. |
Beta Was this translation helpful? Give feedback.
-
|
what does your record config look like? seems like it definitely slowed down how fast it is moving segments, but it is still pretty fast so not sure what the issue is. |
Beta Was this translation helpful? Give feedback.
-
|
record: objects: detect: |
Beta Was this translation helpful? Give feedback.
-
|
You might see this clean up if you set the 24/7 recording retain mode to motion as well. |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 hi, can i ask you about a other problem that i have since i started using frigate and still have. the problem that i have is my zigbee network becomes unreliable stopping frigate container fixes it instantly. i found out that when my 2 wifi ezviz cameras in the backyard have connection issues sometimes just for a sec frigate starts to interfere with my zigbee network. i have tried everything that everyone has suggested over the last couple of months but sill i having issues. i now moved my frigate setup to a other physical machine separating home assistant and frigate and still when the camera connection becomes unreliable frigate starts showing errors in the log and my ZHA network on a other machine becomes unreliable and when i stop the frigate container it fixes ZHA instantly. since moving to a other machine also wont help i dont know what could fix this issue. the only thing i discorverd is that it happens when the camera stream becomes unreliable. |
Beta Was this translation helpful? Give feedback.
-
I also had it on the same machine but i couldn't find the issue so i thats way i moved it but no luck. When the streams are fine there is no issue it works flawless but as soon as frigate has issues with the stream my door wont open lights wont turn on its really strange. maybe i need try moving to z2m its kind of my last hope but it are so much devices in junction boxes to repair 🥵 but thanks for your quick response. |
Beta Was this translation helpful? Give feedback.
-
|
if it was going to cause issues it would be from USB interference which would be constant. If it is related to camera issues then I'd expect the machine running HA can't handle the messages coming in or something unrelated to that. |
Beta Was this translation helpful? Give feedback.
-
|
the usb thing i also tried everything usb powered hub shielded extension i dont think its that dont know but like you say u should expect the problem to be always some times it runs fine for months but now with stormy weather the cameras in the yard sometimes have issues and then the problem starts. and i also thought about the incoming messages but i disabled mqtt in v12 and disabled the frigate integration that should disable messages at least i think so. but also then i have zigbee issues and stopping frigate still fixes it. |
Beta Was this translation helpful? Give feedback.
-
|
Quick question @pbvdven did you check which channels you are running on? Here is a very useful image showing zigbee and 2.4ghz channel overlaps. Also watch out for other non HA zigbee networks such as Philips hue, Ikea etc if you have any of them products too and they are not attached to your HA Zigbee coordinator. Avoid overlaps or being close if you can. Also I believe that sometimes a shielded cable can be worse unless grounded at both ends. Just what I've read. It makes sense as it'd act as a bit of an antenna unless grounded well. |
Beta Was this translation helpful? Give feedback.
-
Yes i did that also zha is on ch15 if I remember correctly and checked all wifi channels. Also used non shielded usb extension before I tried shielded won to see if it would fix the issue. And its only when i run frigate if i don't use it my zigbee network never fails no bad connections. i used blueiris before moving to frigate and then it started to happen a took me a while to figure out that it was related but don't know how even on different machines it still happens. I think im going to make a test setup to see if i still have the issue when using z2m before i move all my devices overz because its been almost year now and tried every possible thing i could think of and others still got no clue where the problem comes from. I thought for sure switching machines would fix it. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a new Frigate Proxy add on available to use with the beta or RC1? I've been running the beta on a separate machine for a while now and want to test out integrating this back into HA |
Beta Was this translation helpful? Give feedback.
-
|
The frigate proxy is not version specific |
Beta Was this translation helpful? Give feedback.
-
|
Amazing, thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Hi all! I've jumped into the 0.12-rc1 build, from 0.11, and I've made the necessary changes to my config file (hopefully correct), but the CPU increase is quite high compared to 0.11. I was able to have average of 5% to 7% of CPU usage per ffmpeg and now it sits at 20% average. I'm running frigate via docker and using HA integration, in a Synology DS918+. Can anyone provide me insights if I am doing anything wrong? FFPROBE output:
|
Beta Was this translation helpful? Give feedback.
-
|
top screenshot: System page screenshot: VAINFO
|
Beta Was this translation helpful? Give feedback.
-
|
Maybe try ffmpeg:
hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420pto see if that makes a difference. I'd also suggest enabling privileged mode for the container or trying to add the CAP_PERFMON capability so you can see the GPU usage as well. |
Beta Was this translation helpful? Give feedback.
-
|
CAP_PERFMON is not available in Synology DSM 7.2 AFAIK. Requires latest version of Docker. Those args were the ones I had before, and are now exploding my CPU when I use them.
|
Beta Was this translation helpful? Give feedback.
-
|
Have you configured docker to use the i965 driver or are you using the default iHD driver? |
Beta Was this translation helpful? Give feedback.
-
|
I feel stupid :S My apologies! I forgot to add that var into the docker-compose file. It went down to 3%!!!! This is a huge improvement!!! Thank you and thank you to the entire Frigate team and contributors!
|
Beta Was this translation helpful? Give feedback.
-
|
Hello I'm getting the famous DTS issue on one of my cams that is a dahua doorbel: I'm using go2rtc. Here is the config: I've tried all sorts of audio codecs without success. Any tips? EDIT: I'm actually getting some timeouts: Complete go2rtc is this: |
Beta Was this translation helpful? Give feedback.
-
|
DTS is a warning not an error. You are getting the stream stopping because the streams fps went way above the expected value which means the camera is sending bad data. |
Beta Was this translation helpful? Give feedback.
-
|
I watched a video on this upgrade indicating a number of config and Docker container changes. I like to upgrade in steps and would prefer just to do a simple upgrade first. I'm on 0.10.1. It looks like I'll have to change the image link to: |
Beta Was this translation helpful? Give feedback.
-
|
go2rtc is not required. The ONLY changes to be concerned with (as far as backwards compatibility goes) are the changes listed under breaking changes. Other than that the same config can be used in 0.12 without issues |
Beta Was this translation helpful? Give feedback.
-
Major Changes for 0.12.0
❗❗Notice❗❗
I want to recognize @NickM-27 for all the contributions he made on this release and all the support he helps provide in the issues. If you have been considering sponsoring this project with either a one time contribution or a recurring contribution, I would request that you do so at his sponsors page.
Link to updated docs: https://deploy-preview-4055--frigate-docs.netlify.app/
Announcement: 0.12.0 will be the last release with support for 32bit ARM. The overhead of maintaining the dependencies is significant, and we are seeing <1% of docker pulls for that architecture.
Changes Since RC1
BREAKING CHANGES
./run: line 7: exec: nginx: not found, then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer ([Support]: Beta11 Can't Find FFMPEG #3223 the database will need to be deleted to roll-back successfully.[Errno 98] Address already in uswhich need to be set back to default to work [Support]: [Errno 98] Address already in use #5444Retention limited by available storage
Frigate now limits its recordings to available storage, if the storage for recordings gets below 1 hour left then Frigate will delete the oldest recording segments to make room for newer ones. Frigate will also not fail if there is no space to save recordings.
go2rtc
go2rtc 1.2.0 has been bundled inside Frigate. The configuration can be set directly inside Frigate's config file nested under the
go2rtcsection. You can follow the guide to setup go2rtc.Due to many issues with RTMP, it is now deprecated in favor of using the bundled go2rtc to provide an RTSP stream. Streams configured in go2rtc can also be used by Frigate to reduce connections to the camera, see the restream docs for more info.
Birdseye restreaming is also now supported at
rtsp://frigate_ip:8554/birdseyeNOTE: Port
8554will need to be mapped in the docker run or docker compose file for the restream to be accessed outside the container.New live stream options
The bundled go2rtc also enables new
MSEandWebRTClive view options in the frontend which enable low-latency full-framerate live views that support audio.NOTES:
The live view options are set in the Frigate WebUI for each camera individually.
New detector types
Frigate now supports new detector types along with the Google Coral TPU.
OpenVINO
The OpenVINO detector type runs an OpenVINO IR model on Intel CPU, GPU and VPU hardware. OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. A supported Intel platform is required to use the GPU device with OpenVINO. The MYRIAD device may be run on any platform, including Arm devices. For detailed system requirements, see OpenVINO System Requirements
TensorRT
NVidia GPUs may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the -tensorrt tag suffix. The TensortRT detector is able to run on x86 hosts that have an Nvidia GPU which supports the 11.x series of CUDA libraries. The minimum driver version on the host system must be >=450.80.02. Also the GPU must support a Compute Capability of 5.0 or greater. This generally correlates to a Maxwell-era GPU or newer, check the TensorRT docs for more info.
NOTE: The link in the docs is for the final release location, for the beta the script is located at https://raw.githubusercontent.com/blakeblackshear/frigate/dev/docker/tensorrt_models.sh
New system page
The
Debugpage has been renamed toSystem. It now includes much more information and links to easily getvainfoandffprobedata.The GPUs section will show each GPU based on the hwaccel args, depending on the type of GPU different information is supported. For example Nvidia GPUs will have the name while others will be generic, also intel does not support memory usage. There is also a
VAINFObutton which will make it easier to diagnose hwaccel issues and verify that the hwaccel driver is being used correctly. Note that this button does not work on all setups, and it doesn't necessarily indicate a problem.Each camera will have their own process CPU & memory usage so it will be easier to see which process is using those resources. There is also an
FFPROBEbutton which will be helpful to understand what each stream is presenting and make it easier to include that in support issues.The debug config has also been removed, the config can be copied using the config page in the WebUI.
New storage page
Frigate WebUI now has a built in storage page which shows the general usage for both storage and memory. It also shows a per-camera storage usage and stream bandwidth. This should make it a lot easier to have a general idea how much storage is being used by each camera.
New logs page
Frigate WebUI now has built in logs, this will make copying and viewing logs much easier. Currently the logs are static meaning the page must be refreshed to view new logs.
New config editor
Frigate WebUI now has a built in config editor with syntax highlighting and schema validation. This means that the config will be validated before it can be saved which will make yaml config much easier to manage.
NOTE: The previous docker-compose or docker CLI may have had the /config.yml set to
:roor read-only. That will need to be removed for the config editor to be able to save the new file.MQTT is now optional
Frigate no longer requires MQTT to function, MQTT is also setup asynchronously so errors will be more clear and frigate won't stop when mqtt is enabled but not setup correctly.
NOTE: MQTT is still required for the Frigate-HomeAssistant Integration
No changes are needed for existing users.
FFMpeg presets
FFMPEG presets for common configurations are now added, making the config cleaner and allowing the underlying args to be changed between releases without being a breaking change. It is highly recommended to update the configuration to use these presets.
See https://deploy-preview-4055--frigate-docs.netlify.app/configuration/ffmpeg_presets for more info on how these should be used.
Example: Enabling Audio In Recordings
before:
after:
This also enables presets for hardware acceleration which will be used to further reduce CPU usage by using the GPU to optimize scaling and other workloads.
Improved events filters
Recordings updates
Recording segments are now stored in UTC to avoid issues with DST. In order to avoid a breaking change, the path of the stored segments has changed from
/media/frigate/recordings/%Y-%m/%d/%H-%s.mp4to/media/frigate/recordings/%Y-%m-%d/%H-%s.mp4.Recordings in the frontend are now shown in the timezone of the device viewing frigate, so the timezone set on the server running frigate is irrelevant.
No changes are needed for existing users.
Images
ghcr.io/blakeblackshear/frigate:0.12.0-rc2ghcr.io/blakeblackshear/frigate:0.12.0-rc2-tensorrtAll Changes
-user_agentforrtmpstreams by @felipecrs in Do not apply-user_agentforrtmpstreams #4596by @felipecrs in Upgrade go2rtc from 1.0.0 to 1.0.1 #5235
{{output}}by @NickM-27 in Add exec docs for{{output}}#5230New Contributors
Full Changelog: v0.11.1...v0.12.0-rc2
Beta Was this translation helpful? Give feedback.
All reactions