Skip to content

Releases: blakeblackshear/frigate-hass-integration

v5.0.0-beta.1

11 Sep 02:31
57cdcd3
Compare
Choose a tag to compare
v5.0.0-beta.1 Pre-release
Pre-release

Changes

πŸš€ Features

🐞 Fixes

πŸ“š Documentation

πŸ“¦ Dependencies

v4.0.0

12 Apr 02:26
dedae97
Compare
Choose a tag to compare

Frigate v0.12: This release is intended as a partner to the Frigate v0.12 release. Please ensure you are using an updated backend along with this updated integration.

Changes

πŸ’₯ Breaking Changes

  • Change Frigate api and ws_api to multi selection instead of single selection. Would break (currently unknown) external API users. (#416) @dermotduffy

πŸš€ Features

🐞 Fixes

πŸ“š Documentation

  • Add translations for RTSP template configuration option (#391) @NickM-27

πŸ”¨ Refactoring

🐎 Performance

  • Change Frigate api and ws_api to multi selection instead of single selection (#416) @dermotduffy

🚨 Testing

πŸ“¦ Dependencies

v4.0.0-rc1

25 Mar 22:22
4986c85
Compare
Choose a tag to compare
v4.0.0-rc1 Pre-release
Pre-release

Frigate v0.12: This release is intended as a partner to the Frigate v0.12 rc1 release. Please ensure you are using an updated backend along with this updated integration.

Changes since v4.0.0-beta4

Changes

πŸš€ Features

  • Allow API callers (e.g. the card) to search via sub_labels (#444) @dermotduffy

🚨 Testing

πŸ“¦ Dependencies

v3.0.1

17 Feb 04:00
705fbef
Compare
Choose a tag to compare

Changes

New-release of the v3 codebase (intended for Frigate v0.11) to incorporate fixes for latest HA version.

πŸš€ Features

🐞 Fixes

πŸ“š Documentation

πŸ“¦ Dependencies

v4.0.0-beta4

28 Jan 23:07
8b80b6b
Compare
Choose a tag to compare
v4.0.0-beta4 Pre-release
Pre-release

Frigate v0.12: This release is intended as a partner to the Frigate v0.12 beta release. Please ensure you are using an updated backend along with this updated integration.

Changes since v4.0.0-beta3

πŸ’₯ Breaking Changes

  • Change Frigate api and ws_api to multi selection instead of single selection. Would break (currently unknown) external API users. (#416) @dermotduffy

πŸš€ Features

🐞 Fixes

🐎 Performance

  • Change Frigate api and ws_api to multi selection instead of single selection (#416) @dermotduffy

πŸ“¦ Dependencies

v4.0.0-beta3

19 Jan 03:25
0f22d93
Compare
Choose a tag to compare
v4.0.0-beta3 Pre-release
Pre-release

Frigate v0.12: This release is intended as a partner to the Frigate v0.12 beta release. Please ensure you are using an updated backend along with this updated integration.

Changes since v4.0.0-beta2

Changes

🐞 Fixes

πŸ“¦ Dependencies

v4.0.0-beta2

07 Jan 22:58
6e43ad7
Compare
Choose a tag to compare
v4.0.0-beta2 Pre-release
Pre-release

Frigate v0.12: This release is intended as a partner to the Frigate v0.12 beta release. Please ensure you are using an updated backend along with this updated integration.

Changes since v4.0.0-beta1

🐞 Fixes

  • Use the HA timezone setting for requesting recordings, provide timezone to event summary (#397) @NickM-27

πŸ”¨ Refactoring

πŸ“¦ Dependencies

v4.0.0-beta1

02 Jan 19:04
b929870
Compare
Choose a tag to compare
v4.0.0-beta1 Pre-release
Pre-release

Frigate v0.12: This release is intended as a partner to the Frigate v0.12 beta release. Please ensure you are using an updated backend along with this updated integration.

Changes

πŸš€ Features

πŸ“š Documentation

  • Add translations for RTSP template configuration option (#391) @NickM-27

πŸ”¨ Refactoring

  • Rewrite recordings media source to use Recordings Summary API (#389) @NickM-27
  • Support Frigate v0.12 UTC based recording paths (#384) @NickM-27

πŸ“¦ Dependencies

v3.0.0

23 Sep 00:13
08da9b9
Compare
Choose a tag to compare

Frigate v0.11: This release is intended as a partner to the Frigate v0.11 release. This integration release will function with prior Frigate server versions but new functionality available through the integration (e.g. true motion sensors) will not yet be functional.

Warning: This release renames some commonly used Frigate entity ids, so you will likely need to update dashboards, automations and templates manually that use the old entity ids. In addition, new Frigate integration installations will see a different mix of entities disabled/enabled by default to better match actual usage and reduce entity pollution.

Example old names Example new names
binary_sensor.kitchen_person_motion binary_sensor.kitchen_person_occupancy
(No such entity) binary_sensor.kitchen_motion
sensor.front_door_person sensor.front_door_person_count
sensor.front_door_all sensor.front_door_all_count

Motivation: The original names included _motion despite not being motion sensors (they are occupancy sensors). This created a light stream of user confusion and support load. As this release includes actual motion sensors (as distinct from occupancy), this was the trigger to finally fix this misnomer.

Changes since v2.3

πŸ’₯ Breaking Changes

  • πŸ’₯ Rename the object count entities for clarity (#259) @NickM-27
  • πŸ’₯ Support for general motion sensor (#248) @NickM-27

πŸš€ Features

🐞 Fixes

🐎 Performance

🚨 Testing

πŸ“š Documentation

πŸ”₯ Removals and Deprecations

  • Remove the HTTP view for recordings API (WS still available) (#299) @dermotduffy
  • Update entities to respect new enable/visibility principles (#273) @dermotduffy

πŸ“¦ Dependencies

v3.0.0-rc.4

03 Sep 23:18
1c96743
Compare
Choose a tag to compare
v3.0.0-rc.4 Pre-release
Pre-release

Prepare for Frigate v0.11: This pre-release is intended as a partner to the upcoming Frigate v0.11 release (or the latest v0.11 beta). This integration release will function with prior Frigate server versions but new functionality available through the integration (e.g. true motion sensors) will not yet be functional.

Warning: This release renames some commonly used Frigate entity ids, so you will likely need to update dashboards, automations and templates manually that use the old entity ids. In addition, new Frigate integration installations will see a different mix of entities disabled/enabled by default to better match actual usage and reduce entity pollution.

Example old names Example new names
binary_sensor.kitchen_person_motion binary_sensor.kitchen_person_occupancy
(No such entity) binary_sensor.kitchen_motion
sensor.front_door_person sensor.front_door_person_count
sensor.front_door_all sensor.front_door_all_count

Motivation: The original names included _motion despite not being motion sensors (they are occupancy sensors). This created a light stream of user confusion and support load. As this release includes actual motion sensors (as distinct from occupancy), this was the trigger to finally fix this misnomer.

Changes since v3.0.0-rc.3

Changes

πŸ’₯ Breaking Changes

  • Use new-style HA entity naming (renames sensor.frigate_detection_fps, sensor.frigate_[detector] entities) (#309) @NickM-27

πŸš€ Features

  • Add icons for bicycle, cow, and horse, and change car and person icons (#317) @felipecrs
  • Allow setting an expiration time for unauthenticated notification events (#169) @gmrandom
  • Update VodSegmentProxyView to allow mp4/m4s files (#331) @uvjustin
  • FEAT: Allow threshold and contour_area to be set from Home Assistant (#316) @NickM-27
  • Add icon for motorcycle entities (#315) @felipecrs
  • FEAT: Add support for coral temp sensor entities (#313) @NickM-27
  • Allow favorite_event to be configured from UI (#301) @felipecrs

πŸ”₯ Removals and Deprecations

  • Remove the HTTP view for recordings API (WS still available) (#299) @dermotduffy

🐞 Fixes

🐎 Performance

🚨 Testing

  • Use debugpy hass integration in devcontainer (#302) @felipecrs
  • Improve devcontainer experience (e.g. adds python debugging, improves port forwarding) (#300) @felipecrs

πŸ“š Documentation

πŸ“¦ Dependencies