In 2022, a home assistant release caused issues with the original blueprint. It seems @hunterjm has not visited that thread in some time. I have updated the blueprint and added dozens of new features. I am continuing to do so and the mods have split the thread here to make things simpler. Thank you very much Hunterjm for the foundational blueprint which has taught me a great deal and made this possible.
Please feel free to visit Github for the latest releases or use the import buttons below which will automatically stay up to date.
Please checkout GitHub for bug reports, feature requests and config support. I will also provide support in this thread.
- Frigate 0.11 or newer (including 0.12)
Frigate integration (v3.00+ for 0.11 and v4.00+ for 0.12)
- “Enable the unauthenticated notification event proxy” must be ticked during install/configuration
- Home Assistant 2022.2 or newer
- An MQTT broker such as the Mosquito Broker Addon connected to HA and Frigate
This blueprint will send a notification to your device when a Frigate event for the selected camera is generated. The notification will include a thumbnail of the event which can be updated with better images as the event progresses. The notification also has customisable action buttons which you can use to view the saved clip/snapshot when available, or silence the notification for a configurable amount of time. You may also configure an action button to open frigate, or visit a webpage or even open an app on your phone.
With this blueprint, you may send the notification to multiple devices by leaving “Mobile Device” blank and instead send to a notification group or even an Android/Fire TV
Since this blueprint is used to create one automation per camera, you can specify filters limiting which zones and objects you want notifications for. You can disable notifications based on the state of another entity (a door locked or a person home (or not). You can also configure a cooldown which will limit the amount of back-to-back notifications you receive for that camera. Additionally, you can silence notifications for a particular camera for a predetermined and configurable amount of time.
There are really only two things you need to do to get started. Pick a camera and pick the device you are notifying. Every thing else is optional and most have good defaults and lots of examples for inspiration.
- Easily select the camera entity or mobile device using a drop down menu.
- Send notifications to an Android or IOS mobile device or a TV.
- or a group containing any combination of the above.
- Configure the title and message of the notification.
- Dynamically handle things like object type, zones and face detection from doubletake.
- Automatically handle some common errors like case matching and bad urls etc.
- Optionally send the notification as a critical alert. (Critical)
- Optionally limit the playing of audio for secondary notification updates, and on IOS, customise the sound. (Alert Once)
- Choose whether or not to update the notification with new thumbnails as they become available.
- Customise the notification colour and icon.
- Optionally send a live view to IOS.
- Configure custom notification channels on Android.
- Specify which [zones] to be notified about. (Zone Filter)
- Choose between enforcing all required zones simultaneously or any one zone
- Specify what type of [objects] to be notified about. (Object Filter)
- Disable notifications if a presence entity or group is “home”. (Presence Filter)
- Limit notifications based on the state of another entity. (State Filter)
- Limit notifications to certain hours of the day. (Time Filter)
- Configure a cooldown for the camera to reduce the number of notifications when back-to-back events occur.
- Silence future notifications for a defined amount of time through actionable notifications. This is helpful in situations where you know you will be triggering detections for an extended period of time. i.e. kids playing outside.
- Set a loitering timer to notify you of stationary objects that remain for a set period of time.
- Configure what happens when you tap the notification (Tap Action)
- Configure 3 action buttons to open almost anything (defaults are: View Clip, View Snapshot and Silence New Notifications)
- Configure the size, transparency, position and duration of TV notifications.
- Debug option to help troubleshooting
- Handle capitilisation in inputs properly
- Handle trailing slash in base urls properly
- Support for multiple Frigate instances by specifying the ClientID and MQTT topic
Android options: Sticky and Channel
Add 10s delay to final notification update to ensure frigate has time to save snapshot edits (crop, bounding box etc) if update thumbnail is enabled.