0.9.0 Release

[blakeblackshear]

NOTICE
This version is not compatible with the current version of the Home Assistant integration for clips in notifications or the media browser. You will need to use the v2.0.0 pre-release of the integration.

Major Changes for 0.9.0

There are quite a few significant changes to the config for this release. Updated config reference is available here.

BREAKING: Clips have been merged into Recordings

Frigate now records footage from the camera one time. You define retention settings to determine what you want to keep. You can set it to retain all footage for the number of days you want and/or have a different retention setting for recorded footage that contains detected objects. When you view footage for an event, you are viewing the recorded footage for the time where the event occurred. The "Download Clip" button on the event view will dynamically create an mp4 from the recordings for download.

Separating events and recording this way has significant benefits. Overlapping events no longer mean that the same video footage is stored multiple times on disk. Also, the issue with the cache expiring for long running events is eliminated.

If I used clips without 24/7 recording before, does this mean I have to now record 24/7?

No. If you only want to store footage of events, the following config should be used:

record:
  enabled: true
  retain_days: 0
  events:
    retain:
      default: 10

BREAKING: width/height/fps moved under detect

Due to regular confusion about which input the height/width/fps applied to, these settings have been moved under the detect section of the config. Here is an example of a simple config:

cameras:
  back:
    ffmpeg:
      inputs:
        - path: rtsp://viewer:{FRIGATE_RTSP_PASSWORD}@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2
          roles:
            - detect
    detect:
      width: 1280
      height: 720
      fps: 5

Recordings Viewer

There is now a way to view recorded footage directly in the WebUI. Browse your recordings and events with a collapsible timeline view.

Fullscreen	Desktop (Collapsed)

Mobile	Mobile Fullscreen

Birdseye

A live, dynamic grid view of all cameras with activity. It has 3 modes:

• objects: includes any cameras with detected objects
• motion: includes any cameras with detected motion
• continuous: all cameras all the time

It is designed to minimize the bandwidth used, so when there are no active cameras, you just get a black screen with the frigate logo.

Live View

When selecting a camera, the live view now uses JSMpeg, which results in about an 80% reduction in bandwidth required vs mjpeg. This view does not support adding overlay information. Tapping on the feed supports full screen viewing on some devices. The mjpeg debug view with overlays is still available at the top right.

Other changes

• Remove tmpfs_cache_size setting as it is no longer needed for hassos
• Delete events from the UI
• Code cleanup and refactors
• Convert config to pydantic to support future config editor
• Support for self signed certs and key auth with MQTT
• has_clip and has_snapshot added to events mqtt topic payload
• snapshot_time added to events mqtt topic to determine if an updated snapshot is available
• Clean PNG snapshots alongside jpg for future training purposes
• Ability to customize timestamp drawn on snapshots and the debug video feed
• Dynamic motion detection defaults based on resolution (Motion detection defaults don't work well for low resolution substreams #1176)
• Adds option to specify jpeg quality on various http endpoints and in config (0.8.2 worse snapshot jpeg quality, possible to configure better? #821)
• Trigger a restart from WebUI or via MQTT
• Labelmap can now be customized via config (How do you edit coco labels.txt in HassOS addon? #507)

Changes since RC3:

Breaking Changes:

• Replace clip_ready event type with a has_clip attribute in the data on the end event

Other Changes:

• Fix global live config option
• Add version to the logs on startup
• Fix bug with expiration of recordings that caused some segments to expire within events in certain scenarios
• Improve reliability of restart handling

Images:

• x86: blakeblackshear/frigate:0.9.0-rc4-amd64
• x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.9.0-rc4-amd64nvidia
• Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.9.0-rc4-armv7
• Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.9.0-rc4-aarch64

[thelefty]

Thank you for adding the clip-ready event! So excited for that!

[itkfilelor]

Are clips not at all generated with the current beta? I know the above states they are not compatible with HA atm but I can't seem to even find them on my HDD in the usual place, or are they buried somewhere? Or am i entirely missing the point? 😁

Thanks for adding the zone specific object filters 😄 haven't had the opportunity to test them out just yet, but I already had some filters drawn out and frigate at least loads with them included.

[jasonpstokes]

Using a large tmpfs may stop the writing to your SSD if there is no event?

[blakeblackshear]

Using a large tmpfs may stop the writing to your SSD if there is no event?

It won't at the moment, although that will likely be incorporated soon after.

[blakeblackshear]

I just assumed from reading a couple of other posts that it was going to retain 24 hours

Where did you see it? I will delete those posts.

[kwanm84]

I think I just made incorrect assumptions, can't seem to find anything that backs it up now. I actually did some testing and only records 5-6 minutes ongoing at about 125mb @4k (lucky its doing h265). Which is 10tb per camera per year, not including events, which isn't going to be too destructive to an ssd. So if i wasn't doing 10 cameras it would be fine, so its a bit of an edge case, but 100tb in just the cameras would be an issue in a few years i think. Will pick up a usb hdd to record onto i think. And even if it can be fixed, i'll just retain a couple of days as a bonus.

[mattheys]

Ahh, looks like I might have to mount an NFS share or my poor SD card isn't going to last long.

[lawm]

Q1: What happens if you retain 10 days of clips, but 5 days of recordings. Does it cut up the recording into individual clips after 5 days? I wanted to try it out, but encountered the next issue.
Edit: I found the answer to it in the new docs
"Clips are also created off of these recordings. Frigate chooses the largest matching retention value between the recording retention and the event retention when determining if a recording should be removed." link

Q2: How does the JSMpeg work: Does it send the original raw stream to the browser and the browser decodes it with Javascript?
Edit: I found the answer: The frigate server will transcode from the original format to mpeg1, then send that to the browser. The browser decodes mpeg1 itself in Javascript.

I ask because I'm having problems playing H.265 clips now. I created an issue for it: #1515

[itkfilelor]

Since updating to the beta, i factory reset my doorbell ( this was on account of me soft bricking it messing with the API) so I have been monitoring the logs to see if my config sticks on the db and (for giggles) my cpu usage. I have experiences 0 errors since the doorbell was reset on any of my cameras(currently 4 running). and my cpu avg usage has dropped ~4.5% and my peaks are down about 11% ( meaning for eg from 14 down to 9.5 and 33 to 22 respectively). The only changes I have made to config.yml was to add per zone box params and clear out all of the clip configs. I like the way this release is heading =)

1x mini-pcie coral with a 4xpcie adapter
6core ryzen 5 (2600? idr haha)
dual NVIDIA 1030's
32 gb ram
2tb hdd NVR drive
cat6e onboard gigabit connection to router

cpu is per camera. all streams h264
oops! also added the birds-eye config

[esmoyer]

Curious if the Live View or Birdseye View are supposed to work yet over Nginx? They seem to both work great on network, but when accessed remotely, they are blank. The Debug view does work remotely; which is weird.

[esmoyer]

I have noticed uBlock causing some issues too. Once disabled, is working great.

[mitchross]

No luck.

[mitchross]

@esmoyer are you able to connect to the web socket over subdomain?

[esmoyer]

It appears so, I found that Nginx Proxy Manager actually has a toggle that enabled Websockets support (that I completely overlooked), once I enabled that and disabled uBlock on the domain it all works now!

[mitchross]

I have web sockets enabled on cloudflare and nginix... What about going into postman with that URL, does it connect?

[esmoyer]

Yep, (once I turned of authentication), it connected and started pulling binaries

[mitchross]

Is your domain pulling over https?

[blakeblackshear]

Mine is. Also note that the frigate container has it's own nginx proxy that handles the websockets too.

[esmoyer]

Yes I use HTTPS for everything

[mitchross]

My flow is unraid->
Frigate docker image running
Cloudflared docker image (argo tunnel)
Nginix Reverse Proxy

Cloudflared config ingress points to nginix reverse proxy ( this is so I don't have to open any ports on router )

Its just so weird this suddenly broke last week. I'm suspect of the WebSockets and JSMpeg Player. In the chrome dev tools I see the websocket related to jmpeg player is disconnecting and retrying over and over.

[ozett]

birdseye stays a bird, no cams to see.
what do you want for debug? what can i do more? Do i need additional config-options for birdseye?

defaults come from debug 0.9.0-3340952 :

{
  "birdseye": {
    "enabled": true,
    "height": 720,
    "mode": "objects",
    "quality": 8,
    "width": 1280
  },

edit:
after waiting 2-3 min. the split-view showed up. than jumped to camera1 in fullscreen....not back again to splitscreen,
(looking how to get more log-info)

[pjfian]

Sounds like you worked it out, but just in case.

birdseye:
  mode: continuous

will do what you want.

[ozett]

found it now also in the docs:
https://github.com/blakeblackshear/frigate/blob/release-0.9.0/docs/docs/configuration/index.md#birdseye

[jasonpstokes]

Take3!

The Birdseye view is cool in continuous mode. But the quality drops a lot when configured for 4:3 camera streams, even with quality: 1?

This is the default settings (1280x720), and the date and time is readable on my screen:

vs this is a mess:

birdseye:
  mode: continuous
  width: 640
  height: 480
  quality: 1

[blakeblackshear]

The height setting in birdseye sets the resolution for the entire birdseye stream, not the resolution for each camera. Now all your cameras are being squished into a 640x480 stream. Try setting to 1280x960.

[jasonpstokes]

Thanks Blake. I'd tried multiplying the frame width by 3 but hadn't thought to use double for both.

Given the empty row:

...it would be amazing to be able to have one large camera with the others wrapped around it. :-) (Plus choosing the order of the cameras, as per #813 ).

Regardless, thanks for what you've created with Frigate - incredible work.

[stephengolub]

Question as to is there is a plan to expose the birdseye view as a camera back to HomeAssistant (obviously through the integration, but didn't know if there was work needed on this side).

[blakeblackshear]

It will require a custom Lovelace card because it does not work anything like the other camera streams.

[pavolholes]

Do you know if such Lovelace card exists, please? Google didn't help me. Thanks!

[ozett]

i am missing the clips now in DEBUG 0.9.0-3340952
i took the config-options from 08x. but i dont see clips anymore.
do they options needed to be modified?
i have this new record-options additionally configured, but no clips visible in the event-list as in 0.8x.

      "record": {
        "enabled": true,
        "events": {
          "enabled": true,
          "max_seconds": 300,

what am i doing wrong?

--edit:
i now have clips. maybe because i fiddeld with recording-settings?
but clips dont play anymore, and download works only for snapshots as image now, but not for clips. they come as clip.htm....

[ozett]

seems related to that issue: #1515

[ozett]

just for the record of beta-testing:
i set recordings on "True" additionally to only "Events:True" in that section,
And on the recordings-Tab of the cam a new menu was found..
but no clip was playing in edge ... i go on fiddling with the beta...

[HIT2022]

Anecdotal, but I've been on 9.* (taking each new tag as it is released) for the last month, and my CPU use has remained consistent:

[blakeblackshear]

@HITChris what are your record settings?

[HIT2022]

5 day retain for record w/ 4 cameras @ 1080/20, 7 for events. Retention is working (storage is consistent)

[esmoyer]

Hmmm...CPU is still in the 70s. Storage appears to be clearing. I'll keep monitoring the next few days.

[esmoyer]

@HITChris do you use audio on your recordings? I am wondering if that is maybe what is causing the higher CPU usage? Though for me it's the python process that keep spiking 75-100% back and forth. Going to look through my config a little close to see if something is maybe weird. @blakeblackshear how does the clean-up process work? Is it a scheduled process or is it kind of continuous?

[anwik]

I normally run Frigate through the add-on for Home Assistant but wasn't sure if it was possible to install the beta version using that method, so I setup a separate container just to test it out.

I noticed that I was able to use the rtsp streams for my Reolink 410 cameras in this version! If I use the rtsp stream in my add-on Frigate I get these error messages every time Frigate attempts to create a clip:

[h264 @ 0x55d5bc77bd00] left block unavailable for requested intra4x4 mode -1
[h264 @ 0x55d5bc77bd00] error while decoding MB 0 113, bytestream 12614

The rtmp stream works OK in the add-on, besides that the video stutters every couple of seconds, not sure why.

[sandstormkeshav]

I get the stutters as well on the rtmp stream, do they still occur for you in the rtsp stream, and are you using any settings for it?

[sandstormkeshav]

Actually the rtmp stream seems to stutter even more on this version than the stable, I am not sure why. I have not changed any of the ffmpeg settings. I am also running rlc-410s

[anwik]

I actually got got the rtsp stream working on the add-on install. I had to modify my input_args since I had them configured to the Reolink recommendations, according to the Frigate docs. Those input_args are most likely tailored to the rtmp stream (guessing).

The particular setting that fixed the errors that I mentioned in my original comment was this:

  - -rtsp_transport
  - tcp

This are the full config I'm using for ffmpeg now:

input_args:
  - -avoid_negative_ts
  - make_zero
  - -fflags
  - nobuffer
  - -rtsp_transport
  - tcp
  - -flags
  - low_delay
  - -strict
  - experimental
  - -fflags
  - +genpts+discardcorrupt
  - -r
  - "30" # <---- this is set to 3 as default according to the new beta docs, I modified it to 30 to test some stuff 
  - -use_wallclock_as_timestamps
  - "1"

For good measure, these are the paths I'm using for the streams:

rtsp://supersecret:[email protected]:554//h264Preview_01_sub
rtsp://supersecret:[email protected]:554//h264Preview_01_main

I hope it works for you!

[sandstormkeshav]

Thank you so much! I will try it out. How has your experience been, has there been less stutters than the rtmp stream?

[anwik]

Thank you so much! I will try it out. How has your experience been, has there been less stutters than the rtmp stream?

No problems! Yes, the stutters are pretty much gone. I also noticed that the audio and video is much more in sync.

[rocksolidsr]

So I ran out of room on my storage and deleted all the old mp4 files but now I can't view it in the viewer, the cameras are still capturing events and I can view just the event but can't view any of the recordings, is there a way to reset that so I can view it again

[blakeblackshear]

Are you asking how to view the files you deleted? I don't understand. The events playback from the mp4 files in the recordings folder.

[rocksolidsr]

no those files are gone but i've restarted frigate and it still thinks the files are there and won't load them, but new files are being loaded and I can't view them in the recordings viewer

[blakeblackshear]

The timeline is built from the events in the database. It does not read the file system to see what files exist. Removing the underlying mp4 files won't change this timeline. You should adjust your retain config, and frigate will clean up the events and the files if they still exist. I'm not sure why this would impact the new recordings though. It would be best if you open a proper issue to troubleshoot.

[shred86]

Just upgraded to RC5 but this is a question/issue that is likely not RC5 specific. I have a 2 TB HDD I'm recording all of my Frigate media to and it just filled up. It appears this is causing a "disk I/O" error resulting in Frigate to continuously restart. I just assumed once the drive got full, it would just start deleting old media but that doesn't seem to be the case.

[blakeblackshear]

There is an existing feature request for this already. Just haven't gotten to it.

[shred86]

Just read through the latest documentation on https://docs.frigate.video and here's some feedback:

• On the "Camera setup" page, make the 4k size example background light gray so it doesn't blend in with the white background of the entire page.
• On the "Avoiding stationary objects" page, I'm a bit confused starting with the third paragraph and down ("For example..."). Are you refering to "entered_zones" as something that comes across with an MQTT event for setting up notifications in Home Assistant, or did you mean to say "required_zones" as it pertains to the Frigate config.yml? Or perhaps both just depending on which paragraph you're reading?
• On the "Advanced Options" page, I think having an example for customizing the labelmap would be beneficial. Example:

model:
  labelmap:
    2: vehicle
    3: vehicle
    5: vehicle
    7: vehicle
    15: animal
    16: animal
    17: animal

• On the "Zones" page, I think it's helpful to clarify that by specifying required_zones: and objects:, this only inhibits the recording of a clip. It seems to still create an event with a snapshot. I'm not sure if this is the intended behavior as it mentions "...when events/snapshots are saved." but snapshots appear to still be saved along with the event.
  As always, thanks for all the work @blakeblackshear!

[blakeblackshear]

Thank you for reading through the new docs. I will take another look.

[blackgold9]

I'm in the same boat. I realize I've become somewhat confused about what concepts apply to recordings, snapshots, mqtt event generation, and then consuming those mqtt events on the HA side. E.g. I only wanted to record an event if the number of zones was > 1, but that's on the HA side.

In general, I'm still a bit lost as to the best way to set up my zones. For instance, how would I set it up to have car events only record if they went from the road zone to the driveway zone, have dogs only recorded if they are on my lawn, but have people recorded if they are in any of the non-road zones?

[blakeblackshear]

@blackgold9 if you want help with this, i would suggest opening a support issue.

[ozett]

would be great to see some solutions for the new vod-api with nodes like this node-red-contrib-ui-mp4frag
or other nodes for live-streaming

[rlrl]

went from RC1 to RC5 and the clips api is broken...
http://xxx:5000/api/events/1632861707.749234-oad3l3/clip.mp4

in the log i see:
2021-09-28T21:02:13.888136631Z [concat @ 0x556a573800] Impossible to open 'pipe:/media/frigate/recordings/2021-09/28/13/f2/41.05.mp4'

reverting to RC4 & all is good.

[blakeblackshear]

Are others experiencing this? Seems odd that running nginx as root would cause a permissions error, but that's the only change I can think of that would cause this.

[rlrl]

i nuked my media directory & re-started frigate and it works again

[memphisdj]

Hi @blakeblackshear , from the change notes i can see the - "snapshot_time added to events mqtt topic to determine if an updated snapshot is available "

I've been testing the latest beta addon in home assistant, playing around in node red.
I can see the event's snapshot_time changing, however, when i poll the public endpoint passing the event id, i always get the same image back. ( I'm referring to the snapshot endpoint).

Also, i set the best_image_timeout from 60 to 5, but this didn't help with the problem above.

One more thing, the has_clip and has_snapshot is only true in the 'end' event. I do understand it for the clip, but why for the snapshot.

If I'm totally wrong with something, please point me in the right direction.

Thanks in advance and for all the hard work, I've been on board since the very beginning, when i had to rebuild the container image to support older CPUs, even before the coral was a thing.

[blakeblackshear]

Just to make sure I am clear, are you referring to this endpoint? https://docs.frigate.video/integrations/api#get-apieventsidsnapshotjpg

[memphisdj]

Hi, I'm referring to the one below, specifically the snapshot endpoint.

https://docs.frigate.video/integrations/home-assistant#notification-api

[blakeblackshear]

I can't see how that would be possible. That endpoint is a direct pass through to the one I posted, and it looks up the frame from the cache with the same identifier sent in the snapshot_time value. Maybe there is some kind of caching issue somewhere in your setup?

One more thing, the has_clip and has_snapshot is only true in the 'end' event. I do understand it for the clip, but why for the snapshot.

This represents whether or not the snapshot is stored on disk as a part of the retention policy. All events have a snapshot while in progress from memory, but it may not get saved to disk on end.

[memphisdj]

Thank you for investing the time to explain. I will try and debug a possible caching issue.

Also, now I understood about the has clip and snapshot. That wasn't the case before. Thanks again !

[TheQue42]

I've just started testing with RC5 (from the official 0.8.4 that was working fine), but I am having problems with recordings not being accessible or even being saved. With debug logging turned on, I can see the very sparse:

[2021-10-01 22:51:59] frigate.http                   ERROR   : ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9 (Ubuntu 9.3.0-17ubuntu1~20.04)
  configuration: --disable-debug --disable-doc --disable-ffplay --enable-shared --enable-avresample --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-gpl --enable-libfreetype --enable-libvidstab --enable-libmfx --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxcb --enable-libx265 --enable-libxvid --enable-libx264 --enable-nonfree --enable-openssl --enable-libfdk_aac --enable-postproc --enable-small --enable-version3 --enable-libzmq --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-libopenjpeg --enable-libkvazaar --enable-libaom --extra-libs=-lpthread --enable-vaapi --extra-cflags=-I/opt/ffmpeg/include --extra-ldflags=-L/opt/ffmpeg/lib
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
pipe:: Invalid data found when processing input

But that doesnt say much to me at least. The cameras are (seem to) work fine via the WebUI, its just when I turn on recording that I start getting errors.
Following a link to a clip on an mqtt notification, results in
"Could not create clip from recordings for fr_vardagsrum.", and the media browser via HA shows NO recordings saved, and when I click a clip in the clips directory, it just hangs.

I've got recording config configured for:

record:
  retain_days: 0
  events:
      max_seconds: 180
      pre_capture: 5
      post_capture: 5
      objects:
        - person
      retain:
        default: 2
        objects:
          person: 2

And I have on occasion noticed mp4 files in the recordings directory, but watching the debug log, it looks like they are quickly cleaned away :-(

I'm not sure if I should start filling in more debugging info here or open a custom ticket, so I'll end with saying that I have tried cleaning out the media-directory (it was brand new when I started), with no difference.

[blakeblackshear]

Please open a proper issue. Thanks!

[TheQue42]

Will do.....naturally, after sitting here and testing and trying to find useful troubleshooting info, you can probably guess what happend just AFTER I wrote this, and tested just ONE more time, with minor tweaks... It started working a lot better!!

[ozett]

thanks for putting out rc6.
pulled it an doing a stress test.
so far working perfectly like rc5 before...
thanks.

[PullenTech]

Amazing update, but I had found one issues, I used to record 24/7 with low quality then record/detect (clip) at 4K, but from the new update I don't seem to be able to do this anymore, if this still possible? or has this been removed from Frigate now?

[blakeblackshear]

It is no longer possible to record in two resolutions. I may find a way to add it back in the future. If you would like, you could add the same camera to frigate again and record the lower resolution. It will do double duty decoding the video stream, but it may be a workaround.

[alexdelprete]

@blakeblackshear I'm still on beta RC6 because the official version of the HA addon is still at v1.14, so I can't install 0.9.1 through it. Did I miss something or you're working on it?

I know I can install it manually, but I prefer the addons because they allow me to quickly check things and start/restart.

Thanks a lot for the release.

[rtenklooster]

Hi thanks again for doing such a great job in developing this awesome product.
I have a couple of small suggestions that might benefit others as well.

1. It would be great if the event filter could be modified. Allowing to select multiple event types, instead of all, or one specific event. So for example, Cats, dogs and birds. The same applies to camera's. Show birds, dogs and horses for Cam A en B, but not C and D.
2. I don't know how the motion detection works, but maybe add "motion" events in the timeline and event list as well.
3. It might be helpfull if the debugging values where a bit expained. What is a good interface speed, what does it mean if it's high, or low. What are skipped frames etc.
4. I don't know if this is even possible, but maybe include some CPU usage in the debug info. See the screenshot below. The CPU seems to be busy, but what's causing this load?
   

Another nice to have feature would be the possibility to play multiple streams simultaneously, controlled by 1 timeline. Just like the birdseye, but for selected camera's in a given timeframe. One timeline with pins for all events for all selected camera's 👯‍♂️
This would come in handy when you have to investigate.

The last thing that came to my mind is including a automation blueprint in the examples / repo. I think the blueprint of @hunterjm is great, however the new events clip_ready /has_clip might come in handy.

The latest version is running great

[blakeblackshear]

Thanks for the thoughtful feedback. I think these are all captured in existing feature requests or the list in my head.

I'm guessing the CPU usage is related to the camera with 100+ fps.

[hunterjm]

The way the new clips are built on the fly, they will almost always be ready by the time the end event notification is finished. Even if it isn't, you'll be missing the last couple seconds of the clip if you pull it up too soon instead of getting a 404. clip_ready was removed during the refactor of how clips/recordings work because it was always fired at the same time as end was.

[bacon-avenger]

As a new user of this awesome recording package, I would like to pass along my thanks for creating and continuing to improve it. Even using only CPU for detection (can't find a coral for love nor money right now), it's performing surprisingly well!

I was looking forward to having the ability to scrub through any recordings when I first saw it referenced a while ago. But I do wish that there still was a way to use the substream for detection and 24/7 recording (saves space) and have the higher quality main stream only record when an object is detected. With the new architecture in 0.9.0, this doesn't seem to be possible any longer

[langejos]

Same here, can't figure out how to tell if my coral is detected and used. Doesn't look like it. This is what the log shows:

frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. <
and the Debug window shows "cpu" as detector

[blakeblackshear]

@langejos this means it is not being used. By default, 0.9.0 uses CPU detectors.You will need to configure a detector for your Coral if you have one.

[langejos]

Perfect, thank you! Just what I needed to put me on the right track. All good now :-)

[colin715]

I too am interested in 24/7 recording and detection using the substream and using the main stream for recording events. Will this functionality exist in the future?

[tonyhardcode]

Just upgraded to the latest version of frigate and the new features are great. Awesome job blakeblackshear!

A feature I would like to see is frigate to be able to stream birdseye as a standalone rtsp/rtmp so I can load up it up into other clients.

[biggen1684]

So I'm looking to upgrade to the newest version. Quite a bit has changed it appears since the last official version.

The first post says, "this version is not compatible with the current version of the Home Assistant integration for clips in notifications or the media browser. You will need to use the v2.0.0 pre-release of the integration". In the old days, one had to copy the custom_components/frigate folder manually to HA. Is that no longer needed to be done?

Looking at the hass-integration repo, it appears that the version is now 2.1.0. Is it now really as simple as doing a HACS -> Explore & Add Repositories -> Frigate to add the integration??

[blakeblackshear]

You can replace that folder by downloading the zip of the version from here: https://github.com/blakeblackshear/frigate-hass-integration/releases

Some people use HACS to manage custom_components. If you do, its available in the default repos there. Also check out the new lovelace card.

[TheSleepySlee]

EDIT: Found this, so will wait for future release: #1942

Hi Blake,
I'm trying v0.9.1 for the first time. Was using 0.8.4 before.
I have removed the clips configuration in yml, frigate starts nicely.
I have added the record config as described on top of this page

One question is about the size of the /media folder, where recording are put.
I have 5 cams, and roughly 5 minutes after starting frigate, I have 1GB of recordings there, altough there is no motion.
Is that expected? (seems it continuously records)
If yes, what is the size needed? Can I put this into /tmpfs to avoid continuously writing to disk?

thanks