0.12.0 Beta 8 #5453
Replies: 30 comments 238 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.
-
|
So I re-tested birdseye again, the restream over webrtc seems to have near the same performance as the native one now. IE it is vastly improved over the beta 7. Going to test it as the primary config for a while to see if any of the visual glitches return but it does seem to be performing better, this also opens up re-using it for homekit etc. |
Beta Was this translation helpful? Give feedback.
-
would you mind sharing a snippet your config - I was trying to work out some webRTC + Birdseye quirks in beta7 never quite got it where I liked it. Hard to tell if I had a bad setting or this was as-good-as-it-gets. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Frigate: In HASS: I have frigate integration v4.0.0=beta4 I also have WebRTC Camera v3.0.2 installed (the direct integration for go2rtc for webRTC I also have Frigate Card v4.0.0 installed My Frigate card config (important parts) |
Beta Was this translation helpful? Give feedback.
-
|
Hmm after letting it run for a while I am getting color / image corruption in the webrtc / restream again.. native jsmpeg still seems to be more reliable but the beta8 change clearly improved performance of the restream version. Looking at logs I am guessing bad input from some cameras corrupts the feed eventually. |
Beta Was this translation helpful? Give feedback.
-
|
Having a couple issues with viewing cameras from the main screen, primarily my wyzecam v2s. The issue has been intermittently present since beta6; was hoping this beta would resolve it. These are the sort of logs I'm seeing: config: I often have the black "No frames have been received" screen from the main page. Sometimes clicking it and selecting Is there a setting that works better for these cameras? Again, they worked fine prior to ~beta6. Thanks for the amazing work!! |
Beta Was this translation helpful? Give feedback.
-
|
Looks like you have my workaround for bad inputs from the previous betas Beta 8 contains go2rtc version 1.1.2 which contains some fixes to ignore bad camera inputs. In beta 8 try the config without the FFMPEG wrapper on the the stream. In my config I still included a second one for audio for webrtc. |
Beta Was this translation helpful? Give feedback.
-
|
Those logs aren't helpful, it's basically just saying that go2rtc can't find a stream. You'd need to show the go2rtc logs when this happens. |
Beta Was this translation helpful? Give feedback.
-
I'm not aware of how to find the go2rtc logs - would you mind showing me how to find them? Sorry for the trouble. |
Beta Was this translation helpful? Give feedback.
-
they are in the webui, just go to the logs section then choose go2rtc in the top right |
Beta Was this translation helpful? Give feedback.
-
|
@bagobones yay! it works great now with those settings; audio too! Thanks for the assistance. |
Beta Was this translation helpful? Give feedback.
-
|
Hey Nick, |
Beta Was this translation helpful? Give feedback.
-
Im running HAOS on a Bmax b2s, has a Intel Celeron N4020C with 6GB DDR4. If I just restart HA and not the whole computer, it will detect coral. |
Beta Was this translation helpful? Give feedback.
-
I'm confused, isn't restarting HA OS the same as restarting the computer in this case? |
Beta Was this translation helpful? Give feedback.
-
Sorry for the confusion. If I goto Settings---System---Restart(Top right corner) It'll restart the OS and the coral will be detected. If I goto Settings---System---Hardware--Top right three dots---Reboot System, it'll restart the computer and coral will not be detected until I unplug and plug it back in. |
Beta Was this translation helpful? Give feedback.
-
|
Oh I see I misunderstood the issue. I'd report that to HA OS then, I don't think frigate can do anything about that |
Beta Was this translation helpful? Give feedback.
-
Will do! Thanks again for the quick response and the work you're doing! |
Beta Was this translation helpful? Give feedback.
-
|
I'm working on switching over to using the go2rtc plugin but when I add what's in the documentation for the go2rtc: section I get the following error ''' I added the section just as it is on https://deploy-preview-4055--frigate-docs.netlify.app/configuration/ Am I missing something? I'm running beta 8 |
Beta Was this translation helpful? Give feedback.
-
That wouldn't make sense, that's what the go2rtc documentation is for. There's no way we could keep it up to date with that.
That's exactly what the guide I linked to does. It also explains at the top what it adds by doing so.
Thanks, looks like we missed that. |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 Sorry I guess I wasn't understanding how go2rtc was being utilized @bagobones comment helped out a lot. So do I add each camera under the go2rtc section that is directly from the camera and then in the camera section use the frigate URL as the stream with the roles. Does that sound correct. Sorry for the misunderstanding and thanks for taking the time to explain! |
Beta Was this translation helpful? Give feedback.
-
So as the guide I linked / docs in general explain, if you want the better live views you need to add your cameras to the go2rtc section. It is optional if you want frigate to also point at the cameras (as they do today) or at the go2rtc stream, but it can help put less stress on the cameras as there are less connections if the go2rtc stream is used. |
Beta Was this translation helpful? Give feedback.
-
Yes. go2rtc ---> camera What you name the camera in go2rtc will be what the URL is for frigate to use. IE Will output a local stream of rtsp://127.0.0.1:8554/camera1 which you can use in frigate or if you wanted in OTHER applications outside frigate. Technically the name of the "Stream/camera" in go2rtc does not need to be the same as the one in frigate so this might make it more clear. Will generate a URL called rtsp://127.0.0.1:8554/reolink_411 Then if the reolink_411 was your kitchen cam you could call the camera in frigate kitchen and point to the reolink_411 stream you created in th go2rtc section. |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha! Thanks that makes way more sense. Let me rewrite my mistakes and try it again. Beautiful work though man! |
Beta Was this translation helpful? Give feedback.
-
|
Just wanted to post another good vibes post that with each beta things seem to keep improving in terms of stability.. Can't thank the frigate and go2rtc project team members enough for the enhancements. I think for quite a few people going from 0.11 to 0.12 stable releases the difference will be noticable.. Once they get through all the config changes.. I am really enjoying the overall speed improvements with restreaming all my cameras over webrtc in homeassistant. |
Beta Was this translation helpful? Give feedback.
-
|
True. My CPU usage has decreased considerably with 0.12. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed. So far it's fantastic! I still haven't been able to convert over to go2rtc, but I think an entire rewrite of my frigate.yaml file is going to really be required for me to figure that out. But the features that have been added and the stability has been top notch. I'm running inside a VM on a Dell PowerEdge and a USB Coral. I gave it 8 CPU cores and 16 gigs of ram and it barely goes over 50% with 4 streams at 7FPS. Once it is fully released, I plan on seeing if I can cram a GPU in that 1U cassis and reload everything from scratch. From what I've been seeing CompreFace is now able to work on other devices like my Jetson Nano. So I now envision Frigate with the Coral on the PowerEdge sending via MQTT to DoubleStack inside Home Assistant also on the PowerEdge and having it be the middle man sending the Frigate posts over to the Jetson Nano for recognition and verification. AA+++ 👍😁 guys! |
Beta Was this translation helpful? Give feedback.
-
|
I have been reading the lasted version of the documentation and I have a question. Port :5000/live/webrtc/ seems redundant as accessing the API port :1984/ also loads the go2rtc web UI. Is there an actual functional difference between http://<frigateserver_ip>:1984/ "the go2rtc API port" and http://<frigateserver_ip>:5000/live/webrtc/ "the go2rtc web interface" ? |
Beta Was this translation helpful? Give feedback.
-
|
Yes. You don't need to expose port 1984 if you don't want. Also, the Frigate 5000 port is proxied through the Home Assistant ingress, which let's you access it from Home Assistant Cloud for example. |
Beta Was this translation helpful? Give feedback.
-
|
I just think it would also be nice to have a button in the Frigate UI to open up go2rtc's UI. |
Beta Was this translation helpful? Give feedback.
-
Port 1984 already needs to be exposed to homeassistant if you want to use the webrtc card integration however. I guess the proxied access is only relevant if you are running it as a HASSOS addon and not on separate docker hosts. |
Beta Was this translation helpful? Give feedback.
-
|
That's true. I meant when running via add-on, it's not needed to forward port 1984. |
Beta Was this translation helpful? Give feedback.
-
|
With beta 8 and newer go2rtc, figured I'd retry the restreaming approach. Still no luck with my Wyze Cams v2/v3/pan variants, go2rtc will die and frigate's feed doesn't come back. go2rtc logs from frigate: I also see a bunch of warnings: "Discarding a corrupt recording segment: wyze-driveway-20230213082201.mp4" When this error occurs, camera remains offline in frigate but I can hit the camera just fine via it's direct RTSP connection, and restarting frigate server works until go2rtc fails again. I'll probably go back to two connections per cam again (one for go2rtc, one for frigate detect/record) as that was stable w/o these errors. Or I can try @bagobones previous workaround of adding frigatedefaults to restream (haven't tried that yet). |
Beta Was this translation helpful? Give feedback.
-
|
@skylarv are you using the dafanghacks firmware for some of your wyzecams? |
Beta Was this translation helpful? Give feedback.
-
|
For clarity I am using the "wyse official beta" firmware on my v3 that is no longer offered. Which might explain differences between my experience and @skylarv |
Beta Was this translation helpful? Give feedback.
-
|
I have one v2 on wz-mini-hacks and then my other v3/v2 cams are on the official beta RTSP firmware. With the one camera I'm testing with my original config above using output_args of preset-record-generic-audio-copy instead of preset-record-generic-audio-aac, it's been holding up. I still see errors in frigate's logs about corrupt video segments or exceeded fps limits and i/o timeouts in go2rtc logs... but camera hasn't died on frigate UI yet for webrtc or jsmpeg and seems to still be recovering/recording events okay. I'll update here if it fully dies again (as in, shows offline and doesn't come back until frigate restart). |
Beta Was this translation helpful? Give feedback.
-
|
Errors are expected at this point from these cameras as it has been determined they put out bad RTSP. The question is if frigate / go2rsp handle the errors or fail. Best solution is to get better cameras but there are no good cameras in this bargain price range. I had high hopes for the tapo cameras as they officially support RTSP but even those put out corrupt streams intermittently. |
Beta Was this translation helpful? Give feedback.
-
|
Just an update from my earlier test with below config - go2rtc started failing for that single camera's stream and wouldn't recover (tried loading it via https://frigate-ip:1984/stream.html too) but I can load the cam just fine via direct RTSP. Will go back to putting entire ffmpeg on single line; if that doesn't work will try @bagobones frigatedefaults workaround: go2rtc logs: frigate logs: |
Beta Was this translation helpful? Give feedback.
-
|
Got hit with go2rtc suddenly crashing again. @NickM-27 We have a watchdog for cameras to restart ffmpeg on failures I wonder how hard it would be to monitor go2rtc and restart it? The go2rtc API / webUI on port 1984 stop responding when this crash happens but over all frigate keeps running with the camera watchdogs constantly trying to reconnect. Frigate related errors (note I am suppressing some FFMPEG errors in my config file): Go2rtc map error dump can be found in this ticket: AlexxIT/go2rtc#213 |
Beta Was this translation helpful? Give feedback.
-
yes that's correct. it is unfortunate that a cheap camera does not adhere to the specs and does not have the hardware to accept multiple main stream connections well |
Beta Was this translation helpful? Give feedback.
-
My Amcrest AD110 doorbell is actually one of the worst.. It gets really slow to respond when it is connected to more than one stream. The processor in it just seems to be slow. It is also the camera I want the most connections to.. I have considered JUST having that one setup with go2rtc and revert the others. |
Beta Was this translation helpful? Give feedback.
-
I have 2 Amcrest AD410s that work real well. Mainly because they are hardwired for power which lets them utilize the 5ghz wifi channels. |
Beta Was this translation helpful? Give feedback.
-
|
The AD110 is pretty bad really compared to the AD410. <3 |
Beta Was this translation helpful? Give feedback.
-
Holding out for the Reolink doorbell to become more widely available to replace it. As for the rest of my cameras I plan on phasing them out for better ones... |
Beta Was this translation helpful? Give feedback.
-
|
Is there a known issue where I can load the individual live streams (sometimes via mse, other times only if I hit "debug"), but from the main screen it says "No frames have been received.."? Restarting seems to work for awhile, but then eventually it dies. I've got two Amcrest cameras that work reliably (AD100 and ProHD) but the AD410 is not collecting detect data, and only displays on the live stream. Also my WyzeCam v2s running DaFang hacks have the same problem. |
Beta Was this translation helpful? Give feedback.
-
|
It's not an "issue" as the live view and detect processes are entirely separate. Would need to see logs and config to offer a suggestion to fix. |
Beta Was this translation helpful? Give feedback.
-
|
relevant logs from go2rtc (it's repeated frequently). Currently (since restarting, only (interestingly, also seeing similar logs from another camera that is functioning correctly), from frigate logs: relevant config: The |
Beta Was this translation helpful? Give feedback.
-
|
I'll add the output of ffprobe on that rtsp url: |
Beta Was this translation helpful? Give feedback.
-
|
This has happened to me a few times but often with other issues so I haven't tried to collect any logs on it as of yet. |
Beta Was this translation helpful? Give feedback.
-
frigate.mp4@NickM-27 does this help shed any light on my issue? it was hard to describe in words |
Beta Was this translation helpful? Give feedback.
-
|
Beta 8 is working very well! No issues and very stable. I was only wondering one thing. When I zoom in chrome I can make the side bar disappear. When I'm not zoomed, I can not do this. See images below:
I would like to have this option always available, no matter if I zoom or not, is this possible? |
Beta Was this translation helpful? Give feedback.
-
|
yes that is possible. Create a feature request and this might be implemented some day. |
Beta Was this translation helpful? Give feedback.
-
|
I believe there is already a feature request for this 👍 |
Beta Was this translation helpful? Give feedback.
-
|
yes, you are correct. This Feature request is very similar to #1891 |
Beta Was this translation helpful? Give feedback.
-
|
So I had my entire frigate host hang yesterday which has prompted me to move all but one of my cameras back to direct detect / recording instead of via go2rtc however I actually don't quite know what happened (couldn't even SSH in to check had to force a reboot). Following the default docker mappings logs are not stored between restarts or stored at all on host storage. I think having a longer term log storage and rotate config with a host mapping would be a good idea as frigate gets more complex. (as it stands even if I remapped the current logs I think they would be wiped on restart of frigate) |
Beta Was this translation helpful? Give feedback.
-
|
It also works well for me. And I have cheap and buggy cameras even! |
Beta Was this translation helpful? Give feedback.
-
Curious how many total cameras you have. I am running 8, 3-5 of which are considered "buggy" by go2rtc if you include my two older reolinks configured over http. The map error in go2rtc is a race condition that has not been figured out yet so it could just randomly kill things and I am guessing is more likely the more cameras you have configured. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately I can't upload any images to this thread, because "Something went really wrong, and we can't process that file." Anyway I assume that sometimes when the WiFi signal of my camera is really weak for some reason and the image becomes pixelated or even cuts out intermittently, go2rtc just crashes at some point and freezes the entire server. So far, the server hasn't crashed when I've directed the Frigate link directly to the camera and haven't used go2rtc at all. At this very moment, apparently the weather conditions are such that the camera is cutting out constantly. |
Beta Was this translation helpful? Give feedback.
-
|
I forgot to say that I don't have any proof for that. :( |
Beta Was this translation helpful? Give feedback.
-
|
Just wanted to let you know that I haven't had any crashes since I ditched go2rtc. |
Beta Was this translation helpful? Give feedback.
-
|
Getting strange clip lengths with download clip from UI and from /api/events vs viewing the clip via the events browser. As far as i know, frigate's only way of broadcasting an event is complete is threw a mqtt event 'end' message. I was working on a script that uses mqtt message to grab the clip from /api/events and save it to a nested folder in cloud storage for backup. This works but its flawed if frigate later starts adding more footage to the same clip that has just been uploaded even after broadcasting event 'end'. Logs are clean: Seems like i can just introduce a 1min delay or so after the final mqtt 'end' event is broadcasted, I'm unsure how this would play out for larger events. |
Beta Was this translation helpful? Give feedback.
-
|
Most likely the clip is requested too soon. Once an mp4 clip is requested it sits in the cache for 5 minutes before being deleted at which point downloading it includes the extra segment. So yes you'll need a longer delay, it should only need to be 10 seconds unless your system is slower at moving segments from cache to storage. |
Beta Was this translation helpful? Give feedback.
-
|
I just noticed that if I switch network on my cell phone while HA or Frigate app with webrtc feed is open, it crashes frigate and I have to restart the frigate docker container. If I close the HA/Frigate app then switch the network, there is no issue (I am testing VPN connection - using wireguard on-demand by turning on/off wifi at home). I assume this is actually go2rtc issue but don't see any error on the UI though |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, I just tried this and I did not have any issues. It is known that go2rtc currently runs each camera stream in the same thread so MSE / webrtc issues can cause isues for the rtsp restream as well. You could make an issue on go2rtc repo |
Beta Was this translation helpful? Give feedback.
-
|
It doesn't happen every time, but mostly when I switch back to LAN from VPN . |
Beta Was this translation helpful? Give feedback.
-
|
Not to hijack your thread, but what is the frigate app? |
Beta Was this translation helpful? Give feedback.
-
|
oh no Frigate app, just HA iOS app |
Beta Was this translation helpful? Give feedback.
-
|
I don't remember seeing these before but now I am getting these errors. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like this is same issue AlexxIT/go2rtc#215 The frigate errors and go2rtc errors timestamp matches
|
Beta Was this translation helpful? Give feedback.
-
|
Not sure if this is new in beta8 because this is the first version I've ever installed (awesome software btw!). The Mask and Zone editor is not working for me. In developer console I see: |
Beta Was this translation helpful? Give feedback.
-
|
What browser are you using? Working for me in chrome. |
Beta Was this translation helpful? Give feedback.
-
|
ugh. nevermind. PICNIC. I didn't realise I needed to click "add" on one of the configs below before I could start drawing masks. The error above is what happens when I click on the camera image immediately after page load. |
Beta Was this translation helpful? Give feedback.
-
|
I'm rotating and re-encoding with go2rtc. When I don't use hardware then all is well (other than CPU usage), but when I do I'm a noob to both golang and frigate/go2rtc but the reason I'm posting here is that my understanding of "write: broken pipe" is that the client (frigate) has closed the connection. I'm not clear why enabling hardware in go2rtc would cause this -- no apparent nvidia-related errors or ffmpeg errors are in the go2rtc log, and frigate receives the stream happily without hardware enabled in go2rtc. This happens with both the The tensorrt detector works great, awesome to have that option. I had errors with tensorrt_models.sh in the pip upgrade and protobuf install steps, in both cases it failed uninstalling previous versions. Inside the container I manually reinstalled latest pip and omitted protobuf since a 4.x version was already installed, and then the rest worked. I don't have those errors anymore but I could go get them again. Thanks for the awesome software!! |
Beta Was this translation helpful? Give feedback.
-
|
I think you misunderstood my point which is that transpose_npp is not included. You'll need to use the normal transpose filter. |
Beta Was this translation helpful? Give feedback.
-
|
You are going to need to adjust it some but this is a command to rotate the stream:
|
Beta Was this translation helpful? Give feedback.
-
|
Works! Thanks!!! |
Beta Was this translation helpful? Give feedback.
-
|
Is this something that makes sense to PR to go2rtc for cuda hardware? |
Beta Was this translation helpful? Give feedback.
-
|
AlexxIt is already aware of it, hardware support is in early stages there. |
Beta Was this translation helpful? Give feedback.
-
|
hello, I also migrated to frigate 0.12.8. unfortunately I stumble on how to properly include my Unifi Protect Cameras in the Restream role,I use HAOS. |
Beta Was this translation helpful? Give feedback.
-
|
There are a lot of issues with unifi cameras and a specific config is needed , I'd suggest reading the go2rtc docs |
Beta Was this translation helpful? Give feedback.
-
|
Looks like it is not documented yet but here's a helpful issue AlexxIT/go2rtc#15 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
wow, thanks @NickM-27 rtspx: did the trick, thank you very much! |
Beta Was this translation helpful? Give feedback.
-
|
Hello, Currently trying to migrate to v12 beta 8 to take advantage of TensorRT detectors, but I can't seem to get it working. Tried to follow all the documentation for getting it set up, but I'm having an issue with Frigate getting stuck in a reboot loop. It seems to decode the first frames from my cameras, then just freezes up and restarts. Everything seems to work fine when using a CPU detector, but whenever I switch to TensorRT detectors, I get a reboot loop. Any help/info would be greatly appreciated. Let me know if any more information is needed. Thanks. Hardware: Config: Logs: |
Beta Was this translation helpful? Give feedback.
-
|
I think it's failing to load the model. I assume you followed the documentation to generate the model folder and have that mapped correctly. I'll check if something was updated in that process recently. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately I dont have a whole ton of experience with docker, currently use Unraid to get by. I was attempting to use a predefined docker container install from the Unraid community store to install the models. I compared it to the script given in the documentation and it looked like it was doing the same thing (the container from the community store was specifically for installing the Tensorrt models for Frigate). It took a lot of finagling but I was able to get them installed. It is very possible that they are corrupted or something tho. I will try to modify the script in the docs to see if I can install them that way. |
Beta Was this translation helpful? Give feedback.
-
|
If you include the docker CLI command that Unraid shows after hitting apply that would be helpful. |
Beta Was this translation helpful? Give feedback.
-
|
I actually was just able to figure out how to use the script in the documentation and that got it up and running. But if it helps at all for the future, here is the docker CLI command from the community apps container that didnt work. Thanks for the help! |
Beta Was this translation helpful? Give feedback.
-
|
I guess I'm just a moron and messed something up the first time because I just tried the models that the community apps container spat out for fun and theyre working now. Anyways, thanks again for the help. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Here is my config: and some logs: |
Beta Was this translation helpful? Give feedback.
-
I use google chrome. When I start playback of a h265 recording from the events list, I always get the following error message:
With segments, you mean the 10s clips under media/recordings/* right? Speaking of timestamps: I discoverd the many of the following error messages in the logs: Has this anything to do with this? |
Beta Was this translation helpful? Give feedback.
-
Google chrome desktop supports h265 as of version 106. You may want to use chrome://media-internals/ to see why playback is failing, h265 playback works great for me in chrome
yes, and 43 mb for a 10s segment is over 150000 mb/hr so it definitely seems like the bandwidth calculation is working as expected.
yes most likely it is the classic reolink issues and the rtsp stream is sending garbage which is causing issues. In the upcoming beta9 release of frigate, you will be able to set manual input args for go2rtc ffmpeg which will likely be useful so you can tell ffmpeg to regenerate the timestamps and maybe that would help |
Beta Was this translation helpful? Give feedback.
-
|
Stupid question. Shouldn't it be possible to just use opus for both webrtc and recording? Mp4 Container should support opus audio nowadays. |
Beta Was this translation helpful? Give feedback.
-
It's less compatible with players so it depends / is not the recommendation but certainly could. |
Beta Was this translation helpful? Give feedback.
-
Thanks for pointing me to chrome://media-internals/. It helped me identify that there seems to be a problem with recorded audio in h265 files from that reolink trackmix camera.
Unfortunately, the reolink trackmix camera does not provide a http/flv or a rtmp stream for the main stream (only for substream). Im limited to use RTSP for the main stream. Thanks so far for all the support. I appreciate it! 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Hi I was wondering when I should use go2rtc and when it bring no benefit. Example with camera TP-Link with SD and HD streams available. I believe that the Lovelace Picture glance card, when set to "live", is taking the jsmpeg anyway, regardless if I have go2rtc in the middle or not. And there will be the same number of connections to the camera in both configs I believe. So although it works well, I fail to understand the benefit for me to have go2rtc added to the config. I am careful with the resources of the Raspberry Pi, not to overload the CPU or memory. As I want to connect 8 cameras to Frigate, detect persons on 5 of them and display 8 cameras in my lovelace dashboard, I prefer to limit to the maximum the unnecessary re-encoding operations, also audio is not necessary. So do I need go2rtc at all? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, ok. I really cannot make any difference between live views when I use go2rtc or not. So it made me think that for standard usage it was not so useful but you say differently. So my setup may be incomplete. What "correct setup" do you mean on go2rtc side? I only have for go2rtc: then on the camera definition and it seems to work well. Is this sufficient to have the better live view in HA? Do you tell the HA card what stream to take or is it automatically providing the better stream? I noted that, for sure, any stream, with or without go2rtc, is better in HA than the direct stream from the camera. But no real difference when it comes from Frigate. |
Beta Was this translation helpful? Give feedback.
-
|
You need to select the live view type in the top right for frigate. You will want to use webrtc or mse, jsmpeg is the old lesser live view. As for HA, you will also need to have the most recent version of the integration |
Beta Was this translation helpful? Give feedback.
-
|
yes no problem with the live view in Frigate, but I'm inserting each camera in a dashboard in Lovelace so my main usage for live view in in a picture glance card. I use integration v4 beta4 |
Beta Was this translation helpful? Give feedback.
-
|
you'll probably want to use https://github.com/AlexxIT/WebRTC which will connect directly to frigate (read the docs) and provide a better quality live view with less latency |
Beta Was this translation helpful? Give feedback.
-
|
thanks, I'll look into this, indeed seems to look like what I need :) |
Beta Was this translation helpful? Give feedback.
-
|
Hello, Im back again. Not sure if you remember, but I was having an issue with installing the beta on my server ubuntu server/casaos. Kept getting error 98. Anyway, Ive been able to install it. I wanted to ask a question, do Frigate still support ONVIF http://ip address:8899/onvif/device_service? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Nothing with ffmpeg changed so the streams that worked before should continue to work |
Beta Was this translation helpful? Give feedback.
-
|
Is there a machanism to restart frigate when ffmpeg process crashes? |
Beta Was this translation helpful? Give feedback.
-
|
That's just a reolink stream crash, not showing go2rtc as crashed. |
Beta Was this translation helpful? Give feedback.
-
|
the go2rtc stream, http://192.168.0.10:1984/stream.html?src=garage, doesn't show the stream so assumed it crashed too. Is there a config to get more logs in go2rtc? |
Beta Was this translation helpful? Give feedback.
-
|
you will see go2rtc reconnecting or showing more errors in the logs. You can enable trace logging. If you are having that issue with reolink continually you may want to use the ffmpeg module for all the stream in go2rtc config |
Beta Was this translation helpful? Give feedback.
-
|
or ask reolink support for a firmware with fixed rtsp and use that |
Beta Was this translation helpful? Give feedback.
-
|
will do. also, I think this started after I used the main stread for detection too, just switched it back to sub_stream. |
Beta Was this translation helpful? Give feedback.
-
|
Ok guys, back at it again. Need some help. Can't get connected to my cameras Frigate logs Go2rtc Config.yml detectors:
cpu1:
type: cpu
num_threads: 3
cpu2:
type: cpu
num_threads: 3
mqtt:
enabled: True
host: 10.0.0.5
database:
path: /media/frigate/frigate.db
logger:
default: info
logs:
frigate.event: debug
#######Global Camera Settings#######
live:
height: 720
quality: 1
detect:
width: 1920
height: 1080
fps: 15
record:
enabled: True
events:
pre_capture: 15
post_capture: 15
retain:
default: 5
mode: active_objects
objects:
dog: 2
cat: 2
go2rtc:
stream:
front_door:
- http://username:[email protected]:8899/onvif/device_service (only works with this url)
- "ffmpeg:front_door#video=h264"
storage_room:
- rtsp://username:[email protected]:88/videoMain
- "ffmpeg:storage_room#video=h264"
############ Cameras!!!##############
######Front Door Camera!!##########
cameras:
front_door:
ffmpeg:
output_args:
record: preset-record-generic-audio-copy
hwaccel_args: preset-vaapi
inputs:
- path: http://127.0.0.1:8554/front_door
input_args: preset-rtsp-restream
roles:
- detect
- record
objects:
track:
- person
- cat
- dog
filters:
person:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.75
mask:
- 523,1080,897,0,0,0,0,1080
cat:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 523,1080,897,0,0,0,0,1080
dog:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 523,1080,897,0,0,0,0,1080
############storage_room Camera#######
storage_room:
ffmpeg:
output_args:
record: preset-record-generic-audio-copy
hwaccel_args: preset-vaapi
inputs:
- path: rtsp://127.0.0.1:8554/storage_room
input_args: preset-rtsp-restream
roles:
- detect
- record
objects:
track:
- person
- cat
- dog
filters:
person:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.75
mask:
- 1920,330,1920,0,0,0,0,343
cat:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 1920,330,1920,0,0,0,0,343
dog:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 1920,330,1920,0,0,0,0,343What am I missing? Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
|
Is the rtsp cam working? Seems like the logs show errors when you're trying to reencode for recordings |
Beta Was this translation helpful? Give feedback.
-
I was able to get it show live. I haven't tried to record anything. So, not sure why it was giving those errors. |
Beta Was this translation helpful? Give feedback.
-
Went back to try it again, and now its not working. Yay me. Back to the drawing board |
Beta Was this translation helpful? Give feedback.
-
|
!!!! I just got it back to working. I had to remove hardware accel and change -codec:v h264_vaapi to -codec:v h264 ....not sure why its not working on this version and it worked on 11. I'm going to test the other camera. |
Beta Was this translation helpful? Give feedback.
-
because the hardware acceleration output format you had and the -c:v vaapi are not compatible. I can tell you how to fix it but you may be better off just getting them working first |
Beta Was this translation helpful? Give feedback.
-
|
I am not sure if this error is similar to the above... but first time seeing it. |
Beta Was this translation helpful? Give feedback.
-
|
So what happens if you just use |
Beta Was this translation helpful? Give feedback.
-
|
When I change it, the camera feeds go dead. ( I did fix the 100% usage of the gpu, uninstall and reinstall drivers) |
Beta Was this translation helpful? Give feedback.
-
Can't believe it. It must have been the driver that had been causing all the issues. I set the preset and the camera cam on without issue! So far, absolutely 0 errors...so far. My GPU even shows up as being used now in the system tab |
Beta Was this translation helpful? Give feedback.
-
|
Ill leave this here just as reference for anyone else using AMD, the driver update is wget https://repo.radeon.com/amdgpu-install/22.40.3/ubuntu/focal/amdgpu-install_5.4.50403-1_all.deb |
Beta Was this translation helpful? Give feedback.
-
|
Just for an update, I switched everything to go2tc is now working. Thanks again. |
Beta Was this translation helpful? Give feedback.
-
|
The issue I'm having is mentioned here before, but sometimes I see some of these entries in the log file: I've been capturing all mqtt events, and this is the last one of this specific event: {
"before": {
"id": "1677315852.215747-i6jzl3",
"camera": "oprit",
"frame_time": 1677318854.583569,
"snapshot_time": 1677315855.709106,
"label": "person",
"sub_label": null,
"top_score": 0.84375,
"false_positive": false,
"start_time": 1677315852.215747,
"end_time": null,
"score": 0.55859375,
"box": [1605, 53, 1625, 127],
"area": 1480,
"ratio": 0.2702702702702703,
"region": [958, 0, 1802, 844],
"stationary": false,
"motionless_count": 0,
"position_changes": 3,
"current_zones": ["zone_straat"],
"entered_zones": ["zone_oprit", "zone_straat"],
"has_clip": true,
"has_snapshot": true
},
"after": {
"id": "1677315852.215747-i6jzl3",
"camera": "oprit",
"frame_time": 1677318856.596609,
"snapshot_time": 1677315855.709106,
"label": "person",
"sub_label": null,
"top_score": 0.84375,
"false_positive": false,
"start_time": 1677315852.215747,
"end_time": 1677318862.334007,
"score": 0.59765625,
"box": [1762, 72, 1802, 231],
"area": 6360,
"ratio": 0.25157232704402516,
"region": [784, 0, 1920, 1136],
"stationary": false,
"motionless_count": 0,
"position_changes": 3,
"current_zones": ["zone_straat"],
"entered_zones": ["zone_oprit", "zone_straat"],
"has_clip": true,
"has_snapshot": true
},
"type": "end"
}I opened the sqlite database and I can confirm that the event is indeed missing in the database. What can be the cause of this? |
Beta Was this translation helpful? Give feedback.
-
|
Frigate has some cleanup logic to avoid duplicate events. For example, you will get 2 events if 2 people walk by together on a walk. This cleanup logic would drop one. |
Beta Was this translation helpful? Give feedback.
-
|
Looked back on the 24/7 recordings, and based on the video your explanation makes sense. When does this cleanup take place? Is it possible to add a flag in the mqtt end event to be notified about this? |
Beta Was this translation helpful? Give feedback.
-
|
It happens every 5 minutes. It's not possible to add a flag in the end event because we won't know about the duplicate yet. |
Beta Was this translation helpful? Give feedback.
-
|
@blakeblackshear when can we expect beta 9? |
Beta Was this translation helpful? Give feedback.
-
|
There's no need to wait for a beta to be cut if you want to have a fix that badly, there's dev images made every commit which you can run if you want to |
Beta Was this translation helpful? Give feedback.
-
|
Getting a bunch of resize errors now: Camera stream is visible. |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone notice that the time on the cameras and the time say in the "logs" seem to be off. I wonder if this is why I get segment out of time error? Its 1200 am actually time in US, OK, but the logs say its 6am. |
Beta Was this translation helpful? Give feedback.
-
|
That is just because you're not passing localtime to the container or your server does not have localtime set. It is purely cosmetic and is not used for anything in 0.12 |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha, Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I'm curious if anyone else is still experiencing the random spinning circle when trying to load a clip or recording? Not seeing anything in the logs, just takes several minutes to load. Just noticed this in the last couple of weeks. |
Beta Was this translation helpful? Give feedback.
-
|
Right, but the network tools will show where the issue is if it is in hardware depending on which call takes the most time |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha, forgive me, when you say network tools is there something in Frigate or you talking in general? |
Beta Was this translation helpful? Give feedback.
-
|
I am talking about browser network tools which shows each network call that is made
|
Beta Was this translation helpful? Give feedback.
-
|
Oh, geez. Okay, yeah I feel dumb. Will do. Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
Things are looking similar to: #4531 (reply in thread) I might try a new drive and see how things go |
Beta Was this translation helpful? Give feedback.
-
|
Quick question on MQTT: However, I can see with MQTT explorer values 0 or 1, and not OFF or ON. Is this a bug? |
Beta Was this translation helpful? Give feedback.
-
|
Can you show a screenshot? I am definitely not seeing that and in general that would break the frigate integration if they were wrong |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for confirming. This was an issue in my home automation scripts, I fixed and now working as expected. Appreciate your quick feedback. Been using frigate for so long now, really love it :) |
Beta Was this translation helpful? Give feedback.
and others
-
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/
Changes Since Beta 7
preset-rtsp-restreamhas been simplified due to various issues. There is a newpreset-rtsp-restream-low-latencypreset which is the same aspreset-rtsp-restreamin beta7preset-vaapirenderDdevices are presentBREAKING 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.Retention 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 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.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.
What's Changed
-user_agentforrtmpstreams by @felipecrs in Do not apply-user_agentforrtmpstreams #4596New Contributors
Full Changelog: v0.11.1...v0.12.0-beta8
Images:
ghcr.io/blakeblackshear/frigate:0.12.0-beta8ghcr.io/blakeblackshear/frigate:0.12.0-beta8-tensorrtThis discussion was created from the release 0.12.0 Beta 8.
Beta Was this translation helpful? Give feedback.
All reactions