Note: See this post for a working fork of this blueprint:
===== Original Post =====
NOTE: See below post if you are on Frigate 0.10.0!
Frigate Mobile App Notification
Works with both Android and iOS (>= 2021.5) mobile apps. It will even work with a notification group targeting both types of devices!
This blueprint will send a notification to your device when a Frigate event for the selected camera is fired. The notification will initially include the thumbnail of the detection, but will update to include actionable notifications allowing you to view the saved clip/snapshot when available, or silence the notification for a configurable amount of time.
With this blueprint, you may send the notification to multiple devices by leaving “Device” blank and instead use a notification group.
The configurability for notifications is top notch. Since this blueprint is meant to used to create one automation per camera, you can specify filters limiting which zones and objects you want notifications for. Not only that, but you can disable notifications based on presence entities being “home” or not. This can be a person, device_tracker or a group combining multiple entities. 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.
Mobile App Device or the name of a Notification Group
Optional features:
You can limit notifications to objects entering any pre-defined zones in Frigate.
You can specify which zones to be notified about. This must be a list (e.g.):
- backyard
You can specify what type of objects to be notified about. This must be a list (e.g.):
- person
- car
You can disable notifications if a presence entity or group is “home”.
You can configure a cooldown for the camera to reduce the number of notifications when back-to-back events occur.
You can 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, like when the kids are playing outside.
Great blueprint for Frigate.
However, is it possible to edit the blueprint for multiple cameras instead of just one?
Have 9 cams running and creating 9 identical automations seems a bit overwhelming.
The automation created by this blueprint is designed to take advantage of the “single” run mode to support cool down and silence actions. You will also likely get to the point where you want to configure different options for each camera. For example, I use the presence filter on my indoor cameras but not my outdoor cameras, and the zone filter on my backyard camera but not my driveway camera.
Creating separate automations per camera increases your one time setup, but enables features you wouldn’t otherwise get and gives you greater flexibility to fine tune notifications per camera.
Not sure what you mean here. The notification stays in my tray until I view or dismiss it. Persistence is handled by the way notifications work on the device. Nothing that I can change in this blueprint as far as I know.
Is it normal that if I click on the clip link as soon as I get it I get an error as if the clip is not ready yet and if I then click or refresh the browser page a few minutes later it works?
Yes. There is a known delay between when the event ends and the clip being written to disk. Should be less than 30 seconds. Frigate doesn’t tell us when it is done writing the file though.
This looks great!
I’d love to get this working, but I run frigate on a dedicated Rpi4 (running Home Assistant OS, with frigate add-on). My main HA instance is on a NUC, would it be possible to run this blueprint from my main NUC HA instance? So far I’ve got the iOS notification working, but it needs tweaking to load the clip/ snapshot from the separate Rpi, as I get “Failed to load attachment Response status code 404”.
