hi, no its not.
i upgraded the frigate integration last night so I think thats something to do with it maybe.
not sure - all I know is its not firing the automation when a new event triggers.
Upgraded the integration to what version?
It may have something to do with it. But are your sensors working in the integration?
3.0.0-rc.2
That may be your issue, Iām not on that version so I canāt help.
I get this all the time as well. There has to be a fix for this!
i gave up on getting this to work with the latest integration so I wrote my own automations which work but arent as fully featured. Im pulling the /cameraname/person/snapshot.jpg image from each camera into a generic camera entity, then exposing that entity in the notification. it works and gets around the external url issue.
butā¦the killer feature of this blueprint was its ability to show the event, not just the latest image, havent quite figured out how to do that in yaml yet.
any tips would be welcome!
Hello,
Itās been a long time since I updated frigate and since I updated it I receive the notifications well but the photo is no longer displayed, the same for the video. So I updated the blueprint but the same
Is this still working for people?
Iām on frigate v0.10.1
Home assistant core v2022.6.6
Integration v3.0.0 rc2
Frigate camera is garden (should it be an entity or just the name in the frigate config)
Device is my device in the companion app
Notification group is empty
Base ur is my duckdns URL
Critical notification is on
Update notification is on
Zone filter is off
Trigger zones is blank
Trigger objects is set to - person
- car
Presence filter is blank
The 3 sliders are left at default
Canāt get any notifications to work even when I press run actions manually.
Any help would be great.
The notifications would never work just because you pressed run actions manually as thereās no mqtt information to start with and no additional information to feed the variables.
Iām assuming as youāre the second person with issues on the v3.0.0 rc2 thereās an integration change.
Iām looking at the GitHub release and I donāt see what would have broken it (doesnāt mean itās not there) just not easily noticeable. Itās the integration that provides the proxy when you open the links (image, clips) if Iām not mistaken.
Yes it works, and it also works with 3.0.0-rc.2 integration for me.
However, the same issues persist with about a million notifications coming in a day on average of about 3 per a person in zones I havenāt even asked it to notify me about and with all of the other settings being totally ignored 
1 Like
So I removed the integration and loaded v2.3 instead and notifications are now working so at least for me it was the v3.0.0 that was causing the issue.
I wonder if I update frigate to v0.11 then it would work again.
Iām getting this too, continuous notifications for the same event it would seem, check your binary sensor for the camera motion, mine detects fine but doesnāt seem to clear, maybe this is the issue?
Iām running home assistant core in a docker, mosquito mqtt in a docker, and frigate in a docker. All are connected and working except for notification on iOS with this blueprint. HA is accessed through reverse proxy. HA version is 2022 6.6. Frigate version is 0.10.1, and frigate integration v2.3.
I have no idea what is preventing me from getting notifications. Iāve checked and unchecked the box for āEnable the unauthenticated notification event proxyā without success. The automatons are being triggered. Te last triggered event time correlates to the last recorded clip. So something is broken in the notification part.
Any ideas on what may be the problem?
Thanks but that all looks fine there. Frigate is also detecting the zones perfectly itself.
I think the issue is with the zone filter, but after staring at the code for many more hours I still am no better off. Its got a lot going on 
If I find a fix Iāll be sure to share.
I cannot seem to get the notifications to work for groups. I have tested for a single device and it works fine. Below is the blueprint config, the notify section in my configuration.yaml file, and the trace
Blueprint config:
id: '1656106408096'
alias: Camera 1 Person Detected Notification
description: ''
use_blueprint:
path: hunterjm/frigate_notification.yaml
input:
camera: camera1
notify_group: all_phones
labels:
- person
Notification section from YAML (sanitised names with xxx and yyy)
notify:
- name: all_phones
platform: group
services:
- service: mobile_app_xxx_phone
- service: mobile_app_yyy_phone
EDIT: I found the issue. Itās a bug with HomeAssistant when you rename a device. Please see this post: Updating the name of a phone does not update xxx in notify.mobile_app_xxx
Is anyone having issue gettings notifications to send?
Mine is working but intermittently, I have events in my frigate dashboard that were not sent along to my phone. I have the cooldown set to 0 and I am not getting the alerts any ideas?
notifications stopped working for me recently. i couldnāt figure out the cause
Hi,
Ive added this blueprint by clicking the link that was at the start of this thread.
My Frigate is 0.10.1.
Frigate Integration is 2.3
HASS is 2022.6.4
Iāve created the automation from the blueprint, done nothing other than copy the camera name from Frigate.yaml (including case) to set the camera name and then pick my iPhone as the notification device.
Iāve also checked the Frigate integration has the ticked box on āEnable Unauthenticated Proxyā.
I have tried to trigger a notification, but nothing appears to be happening.
Iāve checked the traces and can see there is activity, a whole flow diagram of stuff is showing, but the Trace Timeline tab shows the following on every item in the flow diagram:
Stopped because of unknown reason ānullā at 2 July 2022, 23:42:32 (runtime: 0.00 seconds)
It seems Iāve fallen at the first hurdle, but I donāt see anything meaningful to help see what Iāve done wrong. Can anyone help?
Thanks
2 Likes
Should I enter the baseurl here or not? I use an IOS device? What is your recommendation?
The file always opens in the browser and not in the app. Which is better?
(Optional) Base URL
The external url for your Home Assistant instance. This will default to a relative URL and will open the clips in the app instead of the browser, which does not work well on iOS.
Well I figured something out.
Basically I updated the blueprint from the older version to the one where it says 0.10, and my notifications stopped working.
Thankfully I copied the old /config/automations.yaml YAML and compared the old code with the new.
It was due to this for me:
labels: person
should be:
labels:
- person
1 Like