Skip to content

0.11.0 Beta 7

Pre-release
Pre-release
Compare
Choose a tag to compare
@blakeblackshear blakeblackshear released this 20 Jul 11:59
· 43 commits to release-0.11.0 since this release
v0.11.0-beta7
3c46a33

Major Changes for 0.11.0

Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

Changes since beta 6

  • Removed logging when recording segments are discarded as these are a false warning in many cases

Changes since beta 5

  • Note new breaking change! Switch to ffmpeg 5 (I know, I know...)
  • Fixed arm32 compatibility (for now, but this is hanging by a thread)
  • Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)
  • Recordings playback no longer resets when switching windows
  • Experimental timeline UI improvements (#3298)
  • Improve logging if recording segments are discarded when the cache falls behind

BREAKING CHANGES

  • Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
  • Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME_JELLYFIN=i965 to get similar hardware acceleration performance to previous builds.
  • Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
  • This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
  • Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
  • The max_seconds config setting under events has been removed as it no longer has any effect

Frigate+ Integration

With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

image

Here is the roadmap for Frigate+:

  • Launch web version allowing manual upload of training examples and labeling
  • Integrate submission in Frigate
  • Launch Frigate optimized models
  • Launch individually optimized models
  • Integrate labeling and suggestions in Frigate

Updated Events View

  • Speed. The events view has been completely revamped and should be much faster than it was before.
  • Slightly larger thumbnails.
  • You no longer have to refresh the page to see the latest events.
  • You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
  • Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

Updated Recordings View

  • Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
  • Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
  • 16x playback was added for browsers other than Firefox.

Updated Dockerbuild

  • Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

Experimental Timeline UI

Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

Other changes

  • MQTT sensors for any object type #2908
  • Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
  • Added a new ratio filter for object filters #2952
  • Camera recordings always in sidebar #2846
  • Enable and set mode per camera for birdseye #3083
  • Customize order and hide cameras from the UI #2981
  • Enable improve_contrast via MQTT #3011
  • Enable/disable motion detection independent of object detection via MQTT #3117
  • MQTT topic for motion detection #3152
  • Batch deletes of recordings when more than 100,000 recordings need to be deleted
  • Switch to jellyfin ffmpeg
  • Improve cache handling for thumbnails and snapshots of completed events
  • Fixes hwaccel issues for Raspberry Pi users
  • Updates to debian 11 as a base image
  • Consolidate Dockerfile to enable multiarch images
  • Birdseye icno can now be customized #2979
  • Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
  • Initial implementation of mypy and type checking
  • Images from backend now have appropriate cache headers

Full Changelog: v0.10.0...v0.11.0-beta7

Image: blakeblackshear/frigate:0.11.0-beta7

Assets 2
Loading