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