Frigate Mobile App Notifications 2.0

You can try setting the action button url to blank or none in yaml mode but it might not be possible to delete them.

First let me say; this blueprint is GREAT ā€“ I started manually making a notification when I bumped into this just in time. Extremely flexible and convenient.

The only question I have is; is there a way to get just the clip notification (which I believe has to be final since the clip isnā€™t ready until then, but not the intial? Or better question ā€“ is there a way to turn off the initial notification?

Custom filter
Something like

"{{type == 'end'}}"

Should do it.

You will need to enable final update and play with the final delay timer possibly.

1 Like

At the moment Iā€™m having a problem with the notification again. At the moment no attachment is being added, but if I click on the VideoClip or Snapshot button I can open both things. It worked fine for a while, but I have no idea why itā€™s not working anymore. Do you have any idea what the problem could be? Do you need a trace for this?

Check your attachment options. If you updated to 0.14 versions it changed and you need to reselect them

It worked and I updated it again afterwards. I checked it again and one attachment is activated. Here is the configuration as yaml. I donā€™t see any errors.

alias: Frigate Notifications (0.14.0.2u)
description: ""
use_blueprint:
  path: SgtBatten/Beta.yaml
  input:
    presence_filter:
      - ""
    camera:
      - camera.einfahrt
      - camera.haustuer
    notify_device: e1651d4801d3560ee8e9f5d11a2cf9dc
    notify_group: familie
    review_severity:
      - alert
    debug: true
    base_url: ***
    title: Kamera
    message: "{{ label }} detected - {{ camera_name }}"
    video: >-
      {{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/{{camera}}/clip.mp4
    final_update: true
    color: "#f44336"
    tv: true
    tv_interrupt: true
    sticky: true
    alert_once: true
    attachment: >-
      {{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/snapshot.jpg?bbox=1
    attachment_2: >-
      {{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/snapshot.jpg?bbox=1
    tv_position: bottom-right
    tv_transparency: 25%
    tv_duration: 5
mode: parallel
trace:
  stored_traces: 20

TV true changes the way snapshots work and prioritises the TV.

If you actually have TVs in that notification group as well as mobiles then you will need to setup two automations and split the group.

Thank you now it works. I donā€™t know this.

My notifications stopped working again. I had set the cooldown to 60 seconds but even when manually triggering the automation I donā€™t receive any notifications. Itā€™s like Iā€™m going to have to try to sign out and delete and reinstall the Home Assistant app again. Is there a way to work out why I am seeing 4 entries in my HA for a mobile app? I only have one mobile (iPhone15) yet I see several devices.

Iā€™ve also tried updating the Blueprints also.

You canā€™t trigger it manually.

As for your devices, you definitely need to resolve this. As to how, I donā€™t know

I have a docker container running frigate:0.15.0-rc1. This communicates with HA via MQTT. I have the frigate integration installed on HA. Iā€™m using Frigate Notifications (0.12.0.6). Iā€™m attempting to get notifications when a person is present in a couple of frigate zones. One zone includes a driveway. If a person walks up the driveway I get a notification on my android phone. If a person drives onto the driveway and then gets out of the car I do not get a notification. Looking at the trace, when the notification works the step ā€œNotification enabled for object labelā€ is true. When a car starts the event this step is false. Iā€™m guessing the MQTT message indicates a car, which doesnā€™t match person and so the event is ignored. I donā€™t notify on car because the driveway is very short and cars that donā€™t turn on to the driveway sometimes are actually detected as being on the driveway. Any thoughts on how I can get people getting out of cars to kick off a notification?

Maybe have a bolean template sensor for a car that only shows as true if the car is there for more than 30 seconds? And how come the person getting out of the car is not then detected as a person again?

Looking at the automation it appears it only looks for ā€œnewā€ events, and I can see that frigate also sends ā€œupdateā€ events. Iā€™m suspecting that ā€œpersonā€ is added in the ā€œupdateā€ event.

I might have figured it out. The blueprint has a default filter cooldown of 30 seconds. I set this to 0 and did a quick test, I drove around the block. Upon getting out of the car I got a notification. I guess I need to drive around the block a few more times to verify this really fixed the issue.

Ok Iā€™ve gone through the process of deleting all those mobile app instances (which incidentally removed Home Assistant from the mobile) and re-downloaded and the notifications are now working. Must have been some weird thing that has occurred upon upgrading IOS versions.

FYI - you may need to adjust the letter case on your zones names in the blueprint.

I had just gotten version 0.12.0.6 working with frigate 0.15.0-rc1. So what do you do when things are working, check for updates. Frigate now has 0.15.0-rc2 out and this blueprint has been updated to 0.14.0.2w. I updated both and it broke the alerting. I spent a few hours trying to figure it out.

I use both lower and upper case letters in my frigate zone names. With the previous software versions, in order to make notifications work, in the blueprint the zone names had to be entered as just lower case letters. With the updated versions the letter case is maintained. So to make things work with the newer versions I had to make the letter case in the blueprint match the letter case in the frigate zone names.

There is a pull request to handle case mismatch

Would be great if you could test it

I just did a search on my HA file system and saw your Stable.yaml.
I poked around github the 3e version of the beta code that included the lower case patch. I put the patched beta code in the same directory with your Stable.yaml. I used the beta blueprint to re-create my 3 automations that work with three cameras. The zones for the three automations were entered in lowercase and they successfully worked and alerted as expected.

Running Frigate .15rc2, and Notification Blueprint 14.3d.

For Base URL I put my nabu casa external URL. I have thumbnail set for Initial attachment, and Clip m3u8 (iOS) set for Video. None set to Subsequent attachment.

I get the notification on my mobile device, but the ā€œscreenshotā€ it shows is ā€œfailed to load attachmentā€ Response status code was unacceptable: 502"

If i take some clip url and try to access it via my nabu casa URL

xxxx.ui.nabu.casa/api/frigate/notifications/1738794149.044802-3aamaq/driveway/clip.mp4.

it loads on computer. Wonā€™t load on iPhone safari/chrome browser (i assume safari can play an mp4 in a browser).

What could be causing this issue?

EDIT: I have also tried Review GIF for the initial attachment, but I still get a 502 error"

Seems to be an IOS issue on browser. I have no idea what exactly but some people donā€™t have the issue and others do. I wish I had some clue.

Edit: and by IOS issue i donā€™t necessarily mean itā€™s not the fault of the BP somehow, but i donā€™t know what to change to even test