Frigate Mobile App Notifications 2.0

Frigate is running correctly now, go2rtc is working, Live view working, MQTT is listening to frigate, Frigate UI opens from sidebar, all good but I cant get any notifications at all from the SgtBatten blueprint.

If reviews are enabled in frigate, the trigger is extremely simple. Check the trace in the blueprint. If no traces, something is still not setup properly.

Do you have something like this in your Frigate config file:

review:
  alerts:
    labels:
      - car
      - cat
      - dog
      - person

and for cameras:

    record:
      enabled: true
      alerts:
        retain:
          days: 30
          mode: motion

I remember that mine stopped sending the alert after one of the updates because I didn’t have recording setup since my cameras are recorded by a standalone NVR.

‘’’
mqtt:
enabled: true
host: 192.168.1.129
port: 1883
topic_prefix: frigate
client_id: frigate
user: user
password: password

detectors:
coral:
type: edgetpu
device: usb

go2rtc:
streams:
gate:
- rtsp://admin:[email protected]:554/h264Preview_01_main

cameras:
gate:
ffmpeg:
inputs:
# go2rtc restream (recommended)
- path: rtsp://127.0.0.1:8554/gate
roles:
- record
- detect

detect:
  enabled: true
  width: 640
  height: 360
  fps: 5

objects:
track:
- person
filters:
person:
min_area: 5000
min_score: 0.5
threshold: 0.6

record:
enabled: false

snapshots:
enabled: true
timestamp: true
bounding_box: true
crop: false
retain:
default: 1

version: 0.17-0

yes, I am missing reviews, and alerts thank you, I will try again.

in my frigate logs I am still getting the error below. I have installed the Frigate FA again and connected using the link sparkydave suggested
http://ccab4aaf-frigate-fa:5000. That is the correct one for FA and completes the intergation for me.

2026-04-08 21:31:07.474003209 127.0.0.1 - - [08/Apr/2026:22:31:07 +0100] “” 400 0 “-” “-” “-” request_time=“0.000” upstream_response_time=“-”
2026-04-08 21:31:08.897599449 2026/04/08 22:31:08 [error] 211#211: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: “GET /api/version HTTP/1.1”, subrequest: “/auth”, upstream: “http://127.0.0.1:5001/auth”, host: “127.0.0.1:5000”
2026-04-08 21:31:08.897604647 2026/04/08 22:31:08 [error] 211#211: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: “GET /api/version HTTP/1.1”, host: “127.0.0.1:5000”
2026-04-08 21:31:09.616060681 2026/04/08 22:31:09 [error] 209#209: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.1, server: , request: “GET /api/stats HTTP/1.1”, subrequest: “/auth”, upstream: “http://127.0.0.1:5001/auth”, host: “ccab4aaf-frigate-fa:5000”

I still have no notifications after my amendments

this is my frigate config

mqtt:
enabled: true
host: 192.168.1.129
port: 1883
topic_prefix: frigate
client_id: frigate
user: user
password: password!

detectors:
coral:
type: edgetpu
device: usb

ffmpeg:
hwaccel_args: preset-vaapi

go2rtc:
streams:
gate:
- rtsp://admin:[email protected]:554/h264Preview_01_main
- ffmpeg:gate#audio=opus
roles:
- detect
cameras:
gate:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/gate
roles:
- record
- path: rtsp://127.0.0.1:8554/gate
roles:
- detect

detect:
  enabled: true
  width: 640
  height: 360
  fps: 5

objects:
  track:
    - person
  filters:
    person:
      min_area: 5000
      min_score: 0.5
      threshold: 0.6

snapshots:
  enabled: true
  timestamp: true
  bounding_box: true
  retain:
    default: 1

record:
  enabled: false
  alerts:
    retain:
      days: 1
      mode: motion

review:
alerts:
labels:
- person

notifications:
enabled: true

version: 0.17-0

this is my automation ymal

alias: Gate Door Bell Camera
description: “”
mode: single
use_blueprint:
path: SgtBatten/Stable.yaml
input:
camera: camera.gate
notify_device: 53187d74f953be370d6d7605311351ff
title: Person at the gate
message: Someone is at the gate
attachment: snapshot
tap_action: clip
event_type: alert
labels:
- person
cooldown: 30

I think I have it nearly sorted. Once I enabled record I started receiving notifications. I was under the impression that enabeling snapshots was all that was required as I don’t need recording.
cameras:
gate:
ffmpeg:
inputs:
- path: rtsp://…
roles:
- detect
- record

The only problem I have now is when I tap on the notifications I am taken to a url that does not display on my iphone. Its a black screen with the play arrow crossed out.

I have attached my trace of the automation
thanks

Does everyone else get the options when the notification appears. I am getting no options. I only have a choice to open the URL that takes me straight to the snapshot.
When I get the notification in iOS, I don’t have the option of seeing a live stream, a video clip, or a snapshot of the event. On the lock screen of my iPhone the notification appears with a little tiny snapshot. Then I press the notification and it asks me to open the URL and then it shows the snapshot. No options. Any ideas how I can improve?

Long press on iOS to see the three action buttons.

Check your tap action settings for the issue with when you just tap.it.

1 Like

Nice one, Thanks a mill. I’ve got, view clip, view snapshot & silence notifications. excellent,
It opens a new page in safari. Is it possible to stay in HA?

I have iOS Critical selected and it is no longer sending Critical Notifications. I get the notification just doesn’t come across as critical. Frigate, the Blueprint are all on latest. I turned on debug and I see it has option set for critical. I checked iphone and its set to allow Critical Nofifications from HA app. This was working up until recently I noticed it hasn’t been working and decided its now time to troubleshoot the problem.

Thank you for your work on this!

Is there a way to “save” the image attached to the notification (e.g. cropped snapshot with bounding box) to my /media folder? I would like to have it also show on my dashboard as the “last person detected” image.

Thanks!

Frigate integration already does that. An image entity is created for each zone / camera and object. So therefore you have image.person and image.dog etc. I used a horizontal stack card and picture cards to show the last image for each of the objects and zones. And the final embellishment is that card is only visible when I am away.

Thanks for your reply.

Somehow for me, when I look at the image entity provided by the frigate integration in HA, it does not always correspond to the snapshot I recevied on my phone. It seems to be updated somewhat more frequently, sometimes detecting some stationary object thinking it’s a person, although it did NOT trigger any notifications on my phone or update the snapshots in the Advanced Camera Card.

Yes good question. Now I look at it, I can see image.person is indeed a low probability blue id rectangle around my bin! Luckily that does not even show up media/clips or as a notification to my phone …… which is a good thing.

I have not looked at all this and I suspect it has been answered before. This question is not really about the blueprint but about Frigate / Frigate integration.

The blueprint will have a cool off period to stop 10 notifications in 2 mins.

The image.person image seems to be a verbose product of Frigate…… possibly many updates a minute … .some of them false. That probably is the correct way round.

Edit: someone can correct me

I posted the question on reddit and Nick replied that the image entity “updates very quickly on a new detected object, while the snapshot is slower to update to get the best image”

I worked around this by taking a snapshot of the image whenever the notification is triggered:

Notification Blueprint > Action Buttons and URLS > Custom Action (Auto Trigger)

action: image.snapshot
metadata: {}
target:
  entity_id: image.{{ camera }}_person
data:
  filename: /media/frigate/frigate-{{ camera }}-img.jpg

The snapshot image is now locally saved, and I can then add it to my HA dashboard.

Did you ever get this working? I’ve been trying to get the same thing working (to get different notifications for different cats), but I don’t seem to be getting review updates either (despite having sub label updates enabled) and so resulting sub_labels is always empty.