0.15.0 Beta 4 #15644
Replies: 20 comments 43 replies
-
|
Hmm updated and all my cameras stopped working that used the rtsp URL rtsp://user:[email protected]:554/cam/realmonitor?channel=1&subtype=0 Reverted back to Beta 3 and all back to normal. NVR was logs were showing incorrect authentication |
Beta Was this translation helpful? Give feedback.
-
Huh! Strange. Did you "let it settle" for 10 minutes? Sometimes it takes minutes for ffmpeg to sync up. Especially if you use WIFI cams (that can be glitchy) ive noticed. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for beta4! After upgrading I sorted through the false positives and noticed that it did not go trough to the frigate+ site. Renewed the API key and it all worked fine. Merry xmas! |
Beta Was this translation helpful? Give feedback.
-
|
Everything is ok for me ! TY for the job guys ! Merry Xmas !!! |
Beta Was this translation helpful? Give feedback.
-
|
mqtt no longer works for me. If I go back to stable it starts working again. I'm getting this in the logs. |
Beta Was this translation helpful? Give feedback.
-
|
are you running multiple instances of frigate at the same time? That is usually the isue |
Beta Was this translation helpful? Give feedback.
-
|
all OK here (via docker compose): |
Beta Was this translation helpful? Give feedback.
-
|
Nice :) what is your hardware ? |
Beta Was this translation helpful? Give feedback.
-
|
It's a thirteen year old PC (dual Xeon with a lot of RAM, outperformed by a current i3 or i5 in most instances!) with a modern Radeon RX580 graphics card and I have an m.2 to PCI adaptor which mounts a Coral accelerator. I run this manually day by day to play with and learn from. (I have another "24/7" Frigate instance which is permanently set to 0.13.2 because the NAS it runs on doesn't seem to work with 0.14 or later due to high CPU demand - still trying to find out why, exactly). |
Beta Was this translation helpful? Give feedback.
-
|
thank you so much |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Green means it has been reviewed |
Beta Was this translation helpful? Give feedback.
-
|
Is anyone else getting more errors relating to genAI? Mine seemed to be fine using beta 3, but now I get dozens of these errors/warnings a day? I'd say its 50:50 whether a event gets a genAI description or not. If I click regenerate, it usually generates one correctly. |
Beta Was this translation helpful? Give feedback.
-
|
Frigate is just passing your requests to the Gemini API. This error indicates Gemini is just unavailable or unwilling to process your request. Frigate can't do anything about this. |
Beta Was this translation helpful? Give feedback.
-
Ah ok, strange that I'm getting it more frequently. is it possible to be anything to do with any DNS adblocker (pihole) or any firewall rules that make things time out? Not sure I want to run a model locally, on a gpu I don't even have, and currently gemini isn't overly helpful. |
Beta Was this translation helpful? Give feedback.
-
|
Adblockers and firewalls typically block connections completely, so it seems unlikely that it's your pihole. If you have not seen this tip regarding Semantic Search and Generative AI, check it out. The other main devs and I no longer use GenAI as we have not really found much value from it. While some users may still find benefit from GenAI, Semantic Search (all local) has outperformed our expectations. |
Beta Was this translation helpful? Give feedback.
-
|
Ah ok good point. Yeh I think semantic search is great when wanting to find certain clips, but my use for genAI is to provide a description for notification in home assistant on a doorbell push, or an intruder in the garden for example. I do hope that genAI isn't overlooked or dropped support for if the devs don't use it anymore. |
Beta Was this translation helpful? Give feedback.
-
|
There's no plans to drop support for it, we just introduced it in 0.15. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I have just installed Beta 4 and since then the front door camera has stopped working. It is a Reolink Video Dorbell POE. In Frigate the message no frames have been received... is displayed. It still worked with Beta 2. The go2rtc stream works, it is displayed in HomeAssient and it also works via VLC. |
Beta Was this translation helpful? Give feedback.
-
|
Need to see go2rtc logs |
Beta Was this translation helpful? Give feedback.
-
|
Yes here the g2rtc logs |
Beta Was this translation helpful? Give feedback.
-
|
The logs show the camera stops streaming. We have had some users report that the doorbell starts to fail if there are too many connections to it |
Beta Was this translation helpful? Give feedback.
-
|
I guess I don't have that many connections to the camera and it worked well with the old beta. I also restarted the camera once but immediately had the error. |
Beta Was this translation helpful? Give feedback.
-
|
Nothing would have changed between the betas that would cause a difference, ffmpeg, go2rtc, etc. are all the exact same. I also have a reolink doorbell without any issues |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I found the error. I find it very strange but it looks as if the update to Beta 4 changed my configuration. Because instead of admin&password it now says Administration min&password for the go2rtc sub stream of the front door. Although I haven't changed anything. It might be helpful if anyone else has this problem. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, so you have no idea what I could do either? |
Beta Was this translation helpful? Give feedback.
-
|
Try stopping other connections with the doorbell, like temporarily disabling home assistant integration, VLC, etc. |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't seem to be the problem, I've deactivated the reolink integration and don't use anything else. I only used VLC once for testing. |
Beta Was this translation helpful? Give feedback.
-
|
Just wanted to pop in and say no issues yet, looks like things are starting to get stable. |
Beta Was this translation helpful? Give feedback.
-
|
Hello just wanted to say that my 8MP Reolink camera seems to work all the time now with the 4th beta. |
Beta Was this translation helpful? Give feedback.
-
|
Updated docker image to |
Beta Was this translation helpful? Give feedback.
-
|
You must be running Proxmox. This has something to do with how Proxmox virtualizes and manages threads related to Semantic Search features. Other users have reported this and it doesn't seem to be causing any issues. |
Beta Was this translation helpful? Give feedback.
-
|
Ok. Thank you |
Beta Was this translation helpful? Give feedback.
-
|
This has been a bug for a while in Frigate regardless of version but thought I'd report it here. Basically 70% of the time when you load a clip the whole UI moves upwards and the only way to center it again is it click the settings icon on the bottom. Something similar happens when you go into settings and click the right most option (users) the UI shifts all the way to the left. This only happens on iOS phone devices and not on iPad or computers.
|
Beta Was this translation helpful? Give feedback.
-
|
See #13199 |
Beta Was this translation helpful? Give feedback.
-
|
Anyone else finding that frigate's genai stops functioning after several hours and requires restarting frigate? I have a separate dedicated machine serving ollama with a dedicated gpu that is able to process and quickly respond to every frigate request and frigate runs in its own separate dedicated hardware. I was testing frigate with genai running beta3 and now beta4 with docker image to frigate:0037154-tensorrt and am finding a recurring issue after approx 6 to 8 hours of frigate running that it stops performing the genai function. A restart of frigate resolves the issue and for the next 6 to 8 hours descriptions are generated for tracked objects, and then repeat again after ~8hours the descriptions stop. The ollama server continues running no issue and no intervention required and has all the recommended variables passed to it and is running the model always in memory. I do not see anything in the frigate logs regarding this issue. I will start performing packet captures from frigate to ollama. Is there anything else I could search for to find more information on what may be occurring? |
Beta Was this translation helpful? Give feedback.
-
|
Upgraded from 0.15-beta3 to 0.15-beta4 and Frigate won't start. Segfault when loading ONNX. I'm running dual RTX 4070 GPUs and have split the detect role across them. Rolled back to beta3 and everything is working again. 2024-12-29 04:23:00.617286543 [2024-12-28 21:23:00] detector.onnx_0 INFO : Starting detection process: 457 Relevant config - detectors: model: |
Beta Was this translation helpful? Give feedback.
-
|
One difference is Proxmox has its own kernel |
Beta Was this translation helpful? Give feedback.
-
Exactly. And this is likely the cause of the messages from onnxruntime |
Beta Was this translation helpful? Give feedback.
-
A VM emulates the host hardware and runs the guest kernel, an LXC is a container using the host kernel. Hardware pass through / sharing in ether can cause issues.. but LXC seems to be extra quirky that is why I ask. Edit: and in both cases you are NESTING virtualization so it may not work on some older CPUs that don't support nesting. |
Beta Was this translation helpful? Give feedback.
-
|
I've seen that issue. Because the messages don't appear for any other platform other than Proxmox, and the fact that there is no evidence of performance or functionality loss for Proxmox users, there's no point in putting in effort to work around whatever Proxmox is doing differently. |
Beta Was this translation helpful? Give feedback.
-
I still want to know / confirm it is an LXC issue not a VM issue. I am currently considering virtualizing the LAST of my home setup and frigate is the only bare metal system currently. I have a STRONG suspicions this is not a VM issue but a LXC container issue. Stuffing docker inside an LXC is NOT recommended by the proxmox devs with good reason but a bunch of home lab guys do it anyway. |
Beta Was this translation helpful? Give feedback.
-
|
I am getting no information on the 'Storage Stats' page with beta4.
|
Beta Was this translation helpful? Give feedback.
-
|
Can you provide the output of |
Beta Was this translation helpful? Give feedback.
-
|
After a reboot, i am able to see the storage now. Not sure why it was not working before. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm I have been running for a few days without touching the system then today I got 3 false positive notifications.. Trying to log in I realize that the logs had been cleared and frigate had restarted. Going to see if I can pull anything from the host or syslog but it looks like I had a string of 3 unexpected frigate restarts about 25 ish min appart. |
Beta Was this translation helpful? Give feedback.
-
|
pre_capture correct for preview animated clip on dashboard and in /review but when opening the event it does NOT start at the pre-capture time. IE if I hover over the review / alert item I can see the garbage truck approaching my house pickup the bin and then leave, but if I click on the event it is about mid way through that when it starts playing. |
Beta Was this translation helpful? Give feedback.
-
So does pre_capture influence recording the object or when the alert starts? |
Beta Was this translation helpful? Give feedback.
-
|
it affects the recording of the alert, it does not affect the time of the alert itself. |
Beta Was this translation helpful? Give feedback.
-
Hmm, in 0.13 the events where based on the object detection correct? I don't recall them starting essentially the MOMENT a zone was touched I could swear they included the pre_capture showing the approach of the object. Obviously if the objects recording includes the pre_capture we can roll back the time but this is a little jarring watching some alerts based on required zones. |
Beta Was this translation helpful? Give feedback.
-
|
Correct, but that is the difference between review items and objects. Review items are periods of activity that you care about, not objects that you care about. The flip side of that is if you have a zone on the edge of a camera frame then it will take longer for the object to be visible in the recordings. |
Beta Was this translation helpful? Give feedback.
-
|
@bagobones when you click on a review item (alert/detection) there is an associated timestamp that matches up to when it became an alert/detection. The start time of playback is a fixed number a few seconds (either 2 or 4) prior to that timestamp. It can't be configured. This was discussed during 0.14 beta when the review system was introduced. However, a review item starting playback a little later than you'd like doesn't mean that the recording doesn't start a bit earlier, as you already noticed. The review system is just an easy way to quickly look over recordings of interest, and I find myself rarely even watching the full res videos. The preview playbacks typically suffice unless something truly noteworthy happens. |
Beta Was this translation helpful? Give feedback.
-
|
Live view using detect stream for some cameras Not sure if this a 15 Beta 4 specific issue but I noticed that the interface live view is displaying the detect stream for some cameras even though the configuration is the same and no The doc mentions
But all streams use go2rtc (see config below) Relevant config, in this example the |
Beta Was this translation helpful? Give feedback.
-
that is correct, the ratio issue is a known issue only affecting some users in chrome |
Beta Was this translation helpful? Give feedback.
-
Beta Documentation: https://deploy-preview-13787--frigate-docs.netlify.app/
Images
ghcr.io/blakeblackshear/frigate:0.15.0-beta4ghcr.io/blakeblackshear/frigate:0.15.0-beta4-standard-arm64ghcr.io/blakeblackshear/frigate:0.15.0-beta4-tensorrtghcr.io/blakeblackshear/frigate:0.15.0-beta4-tensorrt-jp4ghcr.io/blakeblackshear/frigate:0.15.0-beta4-tensorrt-jp5ghcr.io/blakeblackshear/frigate:0.15.0-beta4-rkghcr.io/blakeblackshear/frigate:0.15.0-beta4-rocmghcr.io/blakeblackshear/frigate:0.15.0-beta4-h8lChanges since Beta 3
pre_captureandpost_capturework correctly with refactored alerts/detectionsrecordconfigtls_insecurefor onvif camerasMajor Changes for 0.15.0
Breaking Changes
There are several breaking changes in this release, Frigate will attempt to update the configuration automatically. In some cases manual changes may be required. It is always recommended to back up your current config and database before upgrading:
frigate.dbfileshm_sizeis too low then a warning will be printed in the log stating that it needs to be increased.recordconfig has been refactored to allow for direct control of how longalertsanddetectionsare retained. These values will be automatically populated from your current config, but you may want to adjust the values that are set after updating. See the updated docs here and ensure your updated config retains the footage you want it to.hwaccelpreset they are using (preset-vaapimay need to now bepreset-intel-qsv-h264orpreset-intel-qsv-h265) if camera feeds are not functioning correctly after upgrading. This may need to be adjusted on a per-camera basis. If aqsvpreset is not working properly, you may still need to use apreset-vaapior revert to the previous ffmpeg version as described below.path: "5.0"in yourffmpeg:config entry. For example:ffmpegis no longer part of$PATH. In most cases this is handled automatically.execstreams will need to add the full path for ffmpeg which in most cases will be/usr/lib/ffmpeg/7.0/bin/ffmpeg.bin: ffmpegdefined, it needs to be removed.Explore
The new Explore pane in Frigate 0.15 makes it easy to explore every object tracked by Frigate. It offers a variety of filters and supports keyword and phrase-based text search, searching for similar images, and searching through descriptive text generated by AI models.
The default Explore pane shows a summary of your most recent tracked objects organized by label. Clicking the small arrow icon at the end of the list will bring you to an infinitely scrolling grid view. The grid view can also be set as the default by changing the view type from the Settings button in the top right corner of the pane.
The Explore pane also serves as the new way to submit images to Frigate+. Filters can be applied to only display tracked objects with snapshots that have not been submitted to Frigate+. The left/right arrow keys on the keyboard allow quick navigation between tracked object snapshots when looking at the Tracked Object Details pane from the grid view.
AI/ML Search
Frigate 0.15 introduces two powerful search features: Semantic Search and GenAI Search. Semantic Search can be enabled on its own, while GenAI Search works in addition to Semantic Search.
Semantic Search
Semantic Search uses a CLIP model to generate embeddings (numerical representations of images) for the thumbnails of your tracked objects, enabling searches based on text descriptions or visual similarity. This is all done locally.
For instance, if Frigate detects and tracks a car, you can use similarity search to see other instances where Frigate detected and tracked that same car. You can also quickly search your tracked objects using an "image caption" approach. Searching for "red car driving on a residential street" or "person in a blue shirt walking on the sidewalk at dawn" or even "a person wearing a black t-shirt with the word 'SPORT' on it" will produce some stunning results.
Semantic Search works by running an AI model locally on your system. Small or underpowered systems like a Raspberry Pi will not run Semantic Search reliably or at all. A dedicated GPU and 16GB of RAM is recommended for best performance.
See the Semantic Search docs for system requirements, setup instructions, and usage tips.
Generative AI
GenAI Search employs generative AI models to create descriptive text for the thumbnails of your tracked objects, which are stored in the Frigate database to enhance future searches. Supported providers include Google Gemini, Ollama, and OpenAI, so you can choose whether you want to send data to the cloud or use a locally hosted provider.
See the GenAI docs for setup instructions and use case suggestions.
Improved Tools for Debugging
Review Item Details Pane
A new Review Item Details pane can be viewed by clicking / tapping on the gray chip on a review item in the Review pane. This shows more information about the review item as well as thumbnails or snapshots for individual objects (if enabled). The pane also provides links to share the review item, download it, submit images to Frigate+, view object lifecycles, and more.
Object Lifecycle Pane
The Recordings Timeline from Frigate 0.13 has been improved upon and returns to 0.15 as the
Object Lifecycle, viewable in the Review Details pane as well as the new Explore page. The new pane shows the significant moments during the object's lifecycle: when it was first seen, when it entered a zone, became stationary, etc. It also provides information about the object's area and size ratio to assist in configuring Frigate to tune out false positives.Native Notifications
Frigate now supports notifications using the WebPush protocol. This allows Frigate to deliver notifications to devices that have registered to receive notifications in the Frigate settings, delivering them in a timely and secure manner. Currently, notifications will be delivered for all review items marked as alerts. More options for native notifications will be supported in the future.
See the notifications docs.
New Object Detectors
ONNX
ONNX is an open model standard which allows for a single model format that can run on different types of GPUs. The
default,tensorrt, androcmFrigate build variants include GPU support for efficient object detection via ONNX models, simplifying configuration and support more models. There are no default included ONNX models for object detection.AMD MiGraphX
Support has been added for AMD GPUs via ROCm and MiGraphX. Currently there is no default included model for this detector.
Hailo-8
Support has been added for the Hailo8 and Hailo-8L hardware for object detection on both arm64 and amd64 platforms.
Other UI Changes
Other Backend Changes
This discussion was created from the release 0.15.0 Beta 4.
Beta Was this translation helpful? Give feedback.
All reactions