Frigate on HA but Notification not firing

[opal crow]

I have frigate up and running on my HA, cameras work, detection is a go, however when I go to use the Frigate Notification (0.10.0) blueprint I can't seem to get it to fire.

Any ideas?

Here is my yml for the automation:

alias: Frigate Notification (0.10.0)
description: ""
use_blueprint:
path: hunterjm/frigate_0.10_notification.yaml
input:
camera: doorbell
notify_device: 2a084bbd69720230f9895855698a29e9
labels:
- person

Frigate is working correctly and reporting events, however the notification never fires. I have tried several things, renaming the camera, removing other detect objects, rewriting my config file

Here is my frigate config:

mqtt:
host: 192.168.86.12
user: mqtt-user
password: mqtt
topic_prefix: frigate
cameras:
doorbell:
ffmpeg:
inputs:
- path: rtsp://homeassistant.local:8554/front-door
roles:
- detect
- snap
- record
objects:
track:
- person
detect:
width: 720
height: 1280
fps: 3
snapshots:
enabled: true
retain:
default: 5
record:
enabled: true
events:
retain:
default: 1
detectors:
cpu1:
type: cpu
num_threads: 3
cpu2:
type: cpu
num_threads: 3

I am running my HA install on a VM on a blade server I have. It has plenty of power for the one camera, can't get my hands on a coral till the chip shortage figures itself out.

[signal dome]

How up to date is the blueprint? Frigate has had some changes so wonder if the format is different than the blueprint expects

[keen light]

The frigate notifications have never worked for me

[signal dome]

Probably easier to just add them directly to an automation

[keen light]

Yeah, I'll try and follow the video you done but I can't seem to find it.

[opal crow]

Ok, I will do a scratch automation and report back thanks !

I was getting a little hung up on sending the most recent snapshot as the notification .

[opal crow]

https://youtu.be/v8fcwhko1k4

[opal crow]

Ok, this is workings locally, of course I need to fiddle with it so it will work outside my network.

alias: Frigate Test
description: Frigate Test
trigger:

• platform: mqtt
  topic: frigate/events
  condition: []
  action:
• service: notify.mobile_app_dan_s_pixel_5a
  data_template:
  message: A {{trigger.payload_json["after"]["label"]}} was detected.
  data:
  image: >-
  http://homeassistant.local:8123/api/frigate/notifications/{{trigger.payload_json["after"]["id"]}}/thumbnail.jpg?format=android
  tag: "{{trigger.payload_json["after"]["id"]}}"
  when: "{{trigger.payload_json["after"]["start_time"]|int}}"
  mode: single

I will dig around in some of the other blueprints I'm sure there is something I can put into the URL field that will push whatever NabuCasa is setting as an external URL.

I could expose my HA direct to the net but I would rather not.

[opal crow]

Yeah, I plugged my nabucasa url in there and it's working, however I think that refreshes pretty regularly, not a permanent fix.

[signal dome]

It should be permanent afaik