Are you getting traces? MQTT? It starts with detection in Frigate and gets sent to this Blueprint via MQTT. Any part of the chain could be broken. Need to know more.
the blueprint isnt being triggered, i have to manually trigger it and when i do it doesnt give any traces. i installed mqtt left everything default like normal have mqtt credentials inside frigate config not sure if mqtt is listing to frigate and not sure how to tell if it is or not.
Use MQTT explorer to watch your MQTT broker to see if Frigate is posting them correctly. If so, itās on the Home Assistant side.
Triggering the notification wonāt create a trace. The only way to trigger the blueprint is using a MQTT message which you can do from MQTT explorer once you have observed and copied a MQTT message that triggers the blueprint.
The presence of the topic only means that it was posted to in the past as the broker holds history.
I believe you should have a frigate/events topic that will update every time frigate makes a detection or alert. This topic is what the blueprint normally listens to. You need to make sure this topic is getting an update every time Frigate makes a detection.
In your OP you said the blueprint used to work, any ideas what you changed since then?
once i saw this i was able to verify that the mqtt host ip changed and needed to change that in the config once i changed that the notifications were working perfect.
i ended up copy pasting config from previous setup sense it was working and then modified what needed to be modified with the new setup
Thanks all for the help
Youāre welcome. 
Glad you figured it out.
1 Like
II use the beta 16ā¦ Runs so far TOP - faces are recognized and also displayed in the push message. Now Iām thinking about how I can use face recognition as mqtt to trigger an action when a face is recognizedā¦ Does anyone have an idea? Donāt figure it out.
@fisch55 I have Frigate installed in a container seperate to HA. I also have the Frigate proxy addon running and have installed the Frigate integration. The integration for the given camera has a āLast Recognized Faceā sensor which changes very well on face recognition:
This way you wont need to setup more sensors and it is all out of the box.
Also have a look at face detection to trigger automation in home assistant? Ā· blakeblackshear/frigate Ā· Discussion #18049 Ā· GitHub
1 Like
Where do you setup facial recognition within Frigate? Or are you using DoubleTake and it comes through in the Frigate settings area?
It looks like itās a part of 0.16 beta. 
License plate recognition too!
1 Like
I made the mistake of starting up the Beta version without first saving a copy of my firgate.yml file 
Be sure to read the Beta notes more thoroughly than I did.
Now downloading my latest backup with fingers crossed I can recover the file.
Frigate automatically creates a backup on version upgrade
Except that I didnāt do a version upgrade as such, I ran the beta which completely cooked things.
Anyway, Iāve since restored the file and all is good again.
1 Like
Thanks for the heads up and glad you got it sorted. Iāll check it out soon. Right now Iām just glad things are somewhat reliable (moved Frigate to itās own mini PC a few weeks ago and had to track down random shutdowns that appear to have been caused by a c-state bios setting).
If you had an existing config and you ran the beta, then it creates a backup config file before migrating it
1 Like
Does anyone have custom sounds in the iOS Home Assistant app working for automations created in this blueprint? And if so, is there a specific format the filename needs to be in?
When I get alerts on the iOS app, it just uses the default notification on the phone that Home Assistant uses when I donāt specify a file in other automations, but this is happening only for the Frigate notifications.
Under āNotification Customizations > Notification Sound - IOS only (Optional)ā I have it set to: US-EN-Alexa-Motion-In-Garage.wav
And when I view the YAML the line is like so:
sound: US-EN-Alexa-Motion-In-Garage.wav
I have plenty of other custom-built automations using both the built in app sounds and ones imported from IOS, and they all work fine, so it seems like something unique to how the Frigate notification is sending these alerts to the app?
Home Assistant Version: 15.2
Core Version: 2025.4.4
Supervisor Version: 2025.05.1
Frigate Notification Blueprint Version: 0.14.0.2w
Frigate HA Integration Version: 5.8.0
Frigate Server Version: 0.15.0-6cb5cfb
iOS Version: 18.5
iOS App Version: 2025.3 (2025.1205)
Just posting this here because it was an issue for me and took me a bit to figure out what was causing it.
I has been behind on upgrades for quite a while, so finally upgraded to most recent stable version and updated all automations so they should work.
However, when it was picking up someone/thing it was giving me the alarm notification vs my standard/default notification I used to always get.
After digging/playing with it for a bit, it was the critical notification. This has always been on in the past, but with current build of you have it on it plays your alarm notification sound. If you have it off, it plays your default notification sound, at least on my android.
Just wanted to post incase someone else had the issue, itās possible itās posted somewhere and I just missed it when I was searching.
2 Likes
Has anyone found the optimum configuration to minimise delays from the first object detection in the single zone specified?
My inference time is only a few ms.
Currently I am running blueprint version 0.14.0.3h.
Many thanks
Iāve only recently found this blueprint, and itās great. Iām having one problem though.
Iāve got two esp32cams running esphome firmware, both rigged up in Frigate using go2rtc.
For one of them, notifications with Tap Action URL set to View Stream donāt work.
Theyre sent without any token and I end up looking at a 404 when I click the notification (same if I copy the URL to another browser).
URL for non-working notification:
https://domain.duckdns.org:8126/api/camera_proxy_stream/camera.garden?token=None
URL for working notification:
https://domain.duckdns.org:8126/api/camera_proxy_stream/camera.front?token=47b7c1d702cb890baed0bc6f5cd0fa2dda76cd6697f1242addeed7c04ffcdd8f
Iāve copied the camera config for Front over the config for Garden within Frigate and still get the same.
Both cameras are set in and using the same automation created by the blueprint.
Iāve removed and reinstalled the Frigate integration.
Iāve set the blueprints debug option and can see it mention the URL with the missing token, but I canāt see why thatās happening.
Can anyone suggest what might be causing the difference between the two please?
edit:
Iāve found that it was because the garden cam had an underscore in its entity ID. Changed it from camera.garden_2 to camera.garden and the view stream tap action works a treat just like my others. Issue raised here.