v3.0.0-rc.3

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.2

🚀 Features

• Add service to 'favorite' an event (#296) @NickM-27
• Add recordings WS endpoint (#297) @dermotduffy
• Add a websocket API to the integration for event retain (#295) @dermotduffy
• Support built in motion detection read / set (#271) @NickM-27
• Add a server status sensor (#278) @NickM-27

🐞 Fixes

• Prevent assert from cors library on preparing response to cors request (#291) @dermotduffy

🚨 Testing

• Allow setting specific HA/Frigate versions in devcontainer (#289) @dermotduffy
• Improve devcontainer preconfig (#288) @felipecrs
• Improve devcontainer environment (#287) @dermotduffy
• Rename the devcontainer Frigate camera (#285) @dermotduffy
• Bump docker-compose forwarded ports (#284) @felipecrs
• Preconfigure HA and Frigate in devcontainer (#280) @felipecrs

📦 Dependencies

• Bump version to 3.0.0-rc.3 . (#298) @dermotduffy
• Update actions (#281) @wrt54g

v3.0.0-rc.2

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

🐞 Fixes

• Fix entity rename for unusually named entities (#276) @dermotduffy

v3.0.0-rc.1

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

💥 Breaking Changes

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

🚀 Features

• Proxy the new Frigate recordings API (allows the card to support recordings) (#267) @dermotduffy
• Ability to disable media browser (#262) @NickM-27
• Support for general motion sensor (#248) @NickM-27

🔥 Removals and Deprecations

• Update entities to respect new enable/visibility principles (#273) @dermotduffy

📦 Dependencies

• Bump version to v3.0.0-rc.1 (#274) @dermotduffy
• Remove deprecated HACS manifest values (#263) @Vaskivskyi

v2.3

Changes

• HACS Action fixes (#242) @NickM-27

🚀 Features

• Add diagnostics to make issue reporting easier (#254) @NickM-27
• Add support for motion detection switch (#241) @NickM-27
• Add an 'update' entity to report new versions of the Frigate backend (#237) @NickM-27
• Add an improve_contrast switch (#230) @hawkeye217
• Add support for entity categories (#228) @dmyoung9
• Add support for device configuration URLs (#229) @dmyoung9
• Add all object sensor to camera and zone devices (#224) @NickM-27
• Attach the raw Frigate event to the BrowseMediaSource (will improve the card experience) (#225) @dermotduffy

🐞 Fixes

• #232: Camera state not updating when toggling recordings (#233) @NickM-27
• Fix issue with superfluous 'all' sensor being created (#227) @NickM-27

📚 Documentation

• Rename Brazilian Portuguese Translation (#221) @LeandroIssa
• Add Brazilian Portuguese translations (#216) @LeandroIssa

📦 Dependencies

• Bump version to v2.3 . (#255) @dermotduffy
• Fix the build after improve_contrast switch (#245) @dermotduffy
• Fixes for HA 2022.4.5 (#243) @dermotduffy

v2.2.2

Changes

🐞 Fixes

• MQTT change to support >= HA 2022.3.0 (#213) @dermotduffy
• use retain=False for command topic (#204) @blakeblackshear
• Make async_sign_path backwards compatible (#208) @balloob

📦 Dependencies

• Bump up to v2.2.2 (#214) @dermotduffy

v2.2.1

Changes

🚀 Features

• Support more states for main camera entity (#201) @NickM-27

🐞 Fixes

• Only add camera objects to zones if that zone defines that object (#195) @NickM-27

📚 Documentation

• Update Frigate Lovelace card screenshot (#184) @dermotduffy

📦 Dependencies

• Bump version to v2.2.1 . (#202) @dermotduffy
• Update the HACS github action (#196) @dermotduffy

v2.2.0

Changes

🚀 Features

• Remove devices no longer found on the Frigate server (#173) @dermotduffy

🔥 Removals and Deprecations

• Use the new async_camera_image interface to avoid logspam (#172) @dermotduffy
• Do not specify loop parameter to remove deprecation logspam (#171) @dermotduffy

🐞 Fixes

• Fixes for HA 2021.12 (#183) @dermotduffy
• Fixes to support in-progress events (Frigate 0.10+) (#178) @dermotduffy

📚 Documentation

• Fix broken links in readme to main Frigate documentation (#156) @clavery
• Include link to HACS project (#160) @srlowe

💄 Style

• Use http.HTTPStatus instead of const.HTTP_* (#162) @scop

📦 Dependencies

• Bump version to v2.2.0 . (#182) @dermotduffy

v2.1.0

ONLY FRIGATE SERVER v0.9.0+ IS SUPPORTED FROM v2.0.0 ONWARDS
YOU MUST UPGRADE YOUR FRIGATE SERVER TO >= 0.9.0
FRIGATE v0.9.0 INVOLVES FRIGATE CONFIGURATION CHANGES, SEE Release Notes

Changes

💥 Breaking Changes

• Retire 'camera_image_height' option. (#145) @dermotduffy

🚀 Features

• Add a websocket proxy to support JSMPEG on the Frigate Lovelace card (#144) @dermotduffy
• Retire 'camera_image_height' option. (#145) @dermotduffy

📚 Documentation

• Update README.md to show mqtt dependency (#142) @dermotduffy

📦 Dependencies

• Bump version to v2.1.0 . (#152) @dermotduffy

v2.0.0

Changes

ONLY FRIGATE SERVER v0.9.0 IS SUPPORTED FROM THIS RELEASE ONWARDS
YOU MUST UPGRADE YOUR FRIGATE SERVER TO >= 0.9.0
FRIGATE v0.9.0 INVOLVES FRIGATE CONFIGURATION CHANGES, SEE Release Notes

💥 Breaking Changes 💥

• Breaking change: Update integration to work with Frigate 0.9.0 (#110) @hunterjm

🐞 Fixes

• Put server URL in warning message for users with multiple servers. (#135) @dermotduffy
• Strengthen upgrade error message since we are giving the user no choice. (#134) @dermotduffy

📚 Documentation

• Add new Lovelace card to documentation (#133) @dermotduffy

📦 Dependencies

• Bump version to v2.0.0 . (#136) @dermotduffy

v1.1.2

Changes

🐞 Fixes

• Unsubscribe from mqtt topic on unload to resolve log spam on entity disable (#131) @dermotduffy
• Fix subtle int validation bug impacting browsing of recordings at 00:XX:YY (#127) @dermotduffy

📚 Documentation

• Update installation instructions now that we're in HACS default. (#129) @dermotduffy
• Add Frigate logo to README.md (#125) @dermotduffy
• Minor doc fixes to sync README and HACS info.md (#109) @dermotduffy

📦 Dependencies

• Bump version to v1.1.2 (#132) @dermotduffy
• Use lady_beetle instead of beetle as the bug emoji (#122) @dermotduffy