Frigate Mobile App Notifications 2.0

Blueprints Exchange
1810

Same error like before

1811

in general that is kind of the idea, fewer updates so it only updates when something the user has configured as interesting has occurred

1813

I keep getting repeated notifications despite having pressed “silence”. The automation is showing as ‘off’ and last triggered 20mins ago
 but I’m getting notifications every minute or even less.

image
image1653×97 5.7 KB

Manually turning the automation on and then off again seems to have stopped the notifications, but when that was done from the actionable notification button, it didn’t work to silence them.

1814

Looks like it’s tracking a stationary car. Doesn’t gel well with this blueprint. You can silence existing events only future ones.

Frigate has some guides on avoiding tracking cars parked in your driveway.

1815

Yep, that’s the case.

I don’t understand why it kept sending them with the automation ‘off / disabled’ though (only via blueprint) and then stopped sending the notifications once I manually enabled and re-disabled the automation.

1816

Because it wasn’t a new event. It was still ongoing for the whole 20+ minutes.

1817

But wouldn’t the automation being disable shut of any notifications? I guess I just don’t know how the notification system is being handled in the background

1818

That was my understanding before I saw how the original blueprint was implemented.

But no, if it’s already been triggered, disabling the automation does not terminate the existing run.

I’m wondering if we could do a simple kill message though.

1819

Interesting. I did some searching a week ago about stopping a different automation and had concluded that the way to do so was to disable it, but never connected the dots that it doesn’t work like that with this one.

1820

Here’s what I found from my prior search.

It appears that a PR was merged some time ago that made the functionality of stopping an automation by calling automation.turn_off.

I’m not familiar enough yet with this BP to know if there’s some reason it isn’t effected by this, but it doesn’t seem to be. (I did observe an active trace that was silenced during recent debugging and realized that’s how the silence feature works). Perhaps something in that thread stands out to either of you.

1821

Hi there,

I noticed that the notification channel seems to be ignored when customized. I did check some of the notifications at the app and despite me setting the channel to “surveillance” in the blueprint the reported channel in history of the app was still “alarm_stream”. Anyone else had something similar?

1822

The automation has to keep running as the way the silence function itself works is to run, disable the automation, wait for the specified time and then reenable itself.

1823

This might be expected with android but alarm stream usually indicates you are using critical. Is that right?

1824

should your „latest“ version now work
. Got the same error message like before if I’m useing your posted link


1825

That link is to a particular version of the file.

Check the pull requests on GitHub, I think it’s #216

1826

@SgtBatten I tried importing the 0.14 beta blueprint (pull request #216) into HA, but it gave the following errors.

Failed to load blueprint: while parsing a block mapping: line 1325, column 35 expected , but found ‘{’ in “/config/blueprints/automation/SgtBatten/Frigate014_beta.yaml”, line 1326, column 43

Failed to load blueprint: invalid key: “{‘title’: None}” in “/config/blueprints/automation/SgtBatten/Frigate014_beta.yaml”, line 1142, column 0

I tried correcting these typos
 but when I try to use the blueprint and save the automation in HA I get the following error:

Message malformed: template value should be a string for dictionary value @ data[‘action’][0][‘choose’][2][‘sequence’][5][‘repeat’][‘sequence’][5][‘choose’][0][‘sequence’][0][‘default’][0][‘data’]

1827

I did not set anything intentionally. Where do I have to check for that?

1828

Like a few on here, I’m getting issues with "Failed to Load Attahment: on both my notifications on my IOS device and on my Apple Watch.

When I click to view the clip or the snapshot its fine. I get this whether i’m on the same network as HA or remotely through HA Cloud. Any ideas where I’m best to look first please?

1829

Just share your config please.

Also please share yours @spammeh

1830 
alias: Frigate Notifications Person Detected
description: ""
use_blueprint:
  path: SgtBatten/Beta.yaml
  input:
    camera: camera.front_doorbell
    notify_device: 1215068044ae6bf1f721e1f4632a96fc
    base_url: https://xxx.ui.nabu.casa
    message: A Person was detected at the Front Door
    labels:
      - person
    update_thumbnail: true
    attachment: ""
    cooldown: 30
    tap_action: >-
      {{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/{{camera}}/clip.mp4
    button_1: View Clip
    update_sub_label: true
    debug: true

Let me know if you need anything more, thanks :slight_smile: