Frigate Mobile App Notifications

Blueprints Exchange
, ,
227

You are sure you have met all the requirements listed above and have the notification event proxy enabled in your integration configuration?

image
image684Ɨ654 24.4 KB

228

I believe so.

the checkmark is checked
frigate: 0.10.0-amd64
ha: 2022.2.9
frigate intergation: v2.2.2
android app: 2022.2.1-full

I had this issue also in previous version of the bp (Frigate Mobile App Notifications - #205 by C.G.B.Spender)

229

Excellent blueprint. Thanks so much.

The issue I have is that I always get notifications, even when the group is marked as ā€˜homeā€™. The notification_device is a single Android device (not a group).

Below is my blueprint configuration:

id: '1646032015087'
alias: Frigate Notification (0.10.0)
description: ''
use_blueprint:
  path: hunterjm/frigate_0.10_notification.yaml
  input:
    notify_device: 7065cb5390285d75bda8cf8c724ef377
    update_thumbnail: true
    camera: front-yard
    cooldown: 60
    presence_filter: group.parents_group

Any ideas?

230

Same issue here

231

Same issue. I have zone filter enabled and the trigger zone and trigger object fields defined, but i get every motion (not only motion in the zone and of a specific object type). This use to work fine with the orginal version of the blueprint, but after the 0.10 updated version it stopped filtering the notifications appropriatly

232

Has anyone managed to get this working with Frigate running on a docker(Unraid), and HASS running on another device/environment(HASS Blue for myself).

Everything works fine, but no matter what I do I can not get the clips/snapshots to load.

233

I didnā€™t tested it (yet) but try to update your local blueprint and replace every url starting with

/api/frigate/notifications/

with

{{base_url}}/api/events/

the api is a little bit different when running via HASS or docker/standalone
check out HTTP API | Frigate

234

There was a bug in the new release for zone filters. I have updated it and hopefully the new logic works as intended.

Since Home Assistant doesnā€™t allow updating blueprints yet you may need to copy the contents of the gist yourself and replace it in the blueprints folder.

2 Likes
235

Thank you SO much, I knew it had to do something with that, or atleast I think I did as I sat there staring at the yaml file and the actual event link that frigate fires off from docker.

I appreciate the help, and hopefully others can learn from my issues as well. Your link helped tremendously for my other issues as well(dont know how I missed that under docs)

236

I updated my blueprint, however, it looks like it does not properly check for the condition of a group being home/away. If I change the Presence Filter to a person it works as expected.

Thanks again for this blueprint, its amazing!

Edit: Let me know if I can gather any debug info for you.
Edit 2: It looks like the presence filter does not work for ā€œpersonsā€ either.

237

For me the presence filter does not work at all - for a person, group or device ā€¦

What logs can I provide to check what Iā€™m doing wrong, or if there is a bug in the blueprint?

238

I started seeing this error in the logs:

Unable to read file /home/user/.homeassistant/blueprints/automation/hunterjm/._frigate_0.10_notification.yaml: 'utf-8' codec can't decode byte 0xb0 in position 37: invalid start byte

Any ideas? Thank you for this blueprint.

239

Can you show me what your blueprint configuration looks like? You can view as YAML by clicking the three dots in the top right and paste it here. The presence filter seems to work for me. Here is my configuration.

alias: Frigate 0.10 - Foyer
description: ''
use_blueprint:
  path: hunterjm/frigate_beta_notification.yaml
  input:
    camera: foyer
    presence_filter: group.family_presence
    cooldown: 90
    notify_group: ios_jk_phones
240

Here is mine where presence seems to be ignored ā€¦

id: '1646032015087'
alias: Frigate Notification (0.10.0)
description: ''
use_blueprint:
  path: hunterjm/frigate_0.10_notification.yaml
  input:
    notify_device: 7065cb5390285d75bda8cf8c724ef377
    update_thumbnail: true
    camera: rear_yard
    cooldown: 60
    presence_filter: person.mark
241

Thank you for updating this, itā€™s working a charm for me!

One question, I am able to set notifications for when an object is stationary (a vehicle, in my use case.)

However, what I want to do is to send a notification when the vehicle is absent (specifically, when the parking space outside my house is empty.)

Is there a way of building something like this using this blueprint? Or will I need to spin together something custom?

242

I think the presence filter is ignored, or the logic is incorrect, when the update_thumbnail option is True (or my understanding of that is incorrect)

Maybe this lineā€™s logic needs to be redone as it appears new_snapshot will override the logic if I am home or not?

{{ loitering or new_snapshot or (not home and zone_filter and (presence_changed or stationary_moved or zone_only_changed or entered_zones_changed)) }}"
243

Mine is notifying me for any person detected rather than the persons in the specified zone. Below is the YAML.

alias: NVR Notification
description: ''
use_blueprint:
  path: homeassistant/frigate_0.10_notification.yaml
  input:
    camera: Entryway
    notify_device: bff7ad27c914eb7f604ab09e70cd0e9d
    base_url: redacted
    update_thumbnail: true
    zone_filter: true
    zones:
      - Close
    labels:
      - person
244

@hunterjm
Iā€™m reposting this request since you now have a new version

Can you add an option to view the live feed?
I used the following for a link to the camera stream and it seems to work pretty well.

<HASS_URL>/api/camera_proxy_stream/camera.{{trigger.payload_json[ā€œafterā€][ā€œcameraā€]}}?token={{states.camera.frontdoor.attributes.access_token}}

Iā€™d rather use a long-lived token but Iā€™ve searched and havenā€™t found a way to do this.
This workaround uses the temporary token so it expires after a few minutes.

EDIT:

I tested with the following to add the stream and it works pretty well.
I copied your blueprint and updated the following section

                          actions:
                            - action: URI
                              title: View Clip
                              uri: "{{base_url}}/api/frigate/notifications/{{id}}/{{camera}}/clip.mp4"
                            - action: URI
                              title: View Snapshot
                              uri: "{{base_url}}/api/frigate/notifications/{{id}}/snapshot.jpg"
                            - action: URI
                              title: Stream
                              uri: https://home.valdeswithans.com:23453/api/camera_proxy_stream/camera.{{trigger.payload_json["after"]["camera"]}}?token={{states.camera.office.attributes.access_token}}
                            - action: "silence-{{ camera }}"
                              title: Silence New Notifications
                              destructive: true

for the URL, I tried inserting {{camera}} instead of my actual camera name but the automation wouldnā€™t load

uri: https://your_url/api/camera_proxy_stream/camera.{{trigger.payload_json[ā€œafterā€][ā€œcameraā€]}}?token={{states.camera.{{camera}}.attributes.access_token}}

it works fine if I use the actual camera name

uri: https://your_url/api/camera_proxy_stream/camera.{{trigger.payload_json[ā€œafterā€][ā€œcameraā€]}}?token={{states.camera.office.attributes.access_token}}

1 Like
245

Iā€™m glad Iā€™m not alone. I am getting the exact same thing but any object!!

Screen Shot 2022-03-05 at 8.28.06 am

246

That is correct - the logic for new snapshot will ignore any presence or zone filters currently. Can you try moving it in the brackets before presence_changed and let me know if that fixes your issue?

Sorry, there is a lot going on here and itā€™s hard to test every situation :slight_smile: