Thanks you very much for this blueprint, super easy to configure.
I have two issues (probably some noob stuff):
Snapshot with bounding box isn’t included in the outgoing notification. There is no image attached, just text “A xxx has been detected on the yyy camera”.
The 3 links below (or just tapping on the notification) ends up with a 502 Bad Gateway in the browser on the phone. It looks like no token is provided. Shouldn’t it open the Home Assistant companion app instead?
Answering my own post: I found the issue and it was related to the notification blueprint. I was using authenticated Frigate endpoint (8971) instead of the regular 5000 port. Snapshots and clips weren’t accessible from Home Assistant in the first place…
Now it works and back to GenAI to see if how the message could be improved
Is there an easy, preferred way to setup notifications using this blueprint to alert on Known_Plates in the frigate config ? Have a list of known plates in that section of Frigate config that I would like to be notified on, specifically certain plates in that section
First of all I want to say that I hav been using this blueprint for more than a year and i love it!!
I discovered the LLM Vision integration and managed to install and use it and i came up with a thought…
Would it be possible to add the LLM Vision setup in that Blueprint?
My thinking is to reduce false positives by running it by AI, so the workflow would be something like the below:
Trigger the Automation
Run LLM Image Analyzer
If AI detects a person, the response could be something like “Person Seen”
If response is “Person Seen” then continue with the notification blueprint, otherwise dont notify
I have tried cloning and adding the relevant options in the current blueprint but it is simply impossible to do that with my current level of knowledge.
Thank you and I hope my idea sparks a new blueprint !!!
I have been for a while receiving incorrect snapshots of events, the issue is intermittent. I have 3 instances of the blueprint configured, each of them for different objects and zones .
Car
driveway and street (loitering)
Person
porch & lawn
Dog
porch
The most recent notification I received was for a dog. However the snapshot that came through was for a vehicle. The dog event in frigate occurred at 5:06 pm and the vehicle event at 5:22 pm. The single notification was received at 5:24 pm.
So what I make of this is the dog notification BP likely fired immediately, but due to my HomeAssistant app notification settings (delivered via Google) was received 18 minutes later and the image loaded was not based on the actual event at the time the BP triggered but was from one of the more recent events in frigate (the car was not loitering so it didn’t actually trigger the Frigate Blueprint Vehicle instance).
I’m going to try changing my notification settings to use always persistent (uses more battery according to docs) to see if it helps the situation.
The issue happens quite frequently so I should likely be able to tell within the week if it has helped.
Despite this issue the blueprint is still great btw, thanks for it!
Not sure if it works yet but i’ve been trying to put {{ recognised_license_plate }} in the subtitle box. Not quite what you’re asking for, but might work?
Quick update, the persistent notification delivery did not help. I still have mismatched snapshots being delivered for other objects. It appears to be a bug with the blueprint.
Does anyone else have multiple instances of the blueprint, each with different objects and zones?
Just a tip rather than an issue and more for people searching the forum. If the Blueprint does not send you video clips or images as part of the notification It’s potentially because the integration has two servers listed and you can only have one to get clips working.
I could get them to play in the web browser on android in the media section of HA eliminating codec issues etc but never from the notification.
I deleted the old frigate server from the integration and it worked instantly. This isn’t a fault of the blueprint as far as I can see unless it would be possible to select the server during setup if the API exposes that detail.
I want to know if there’s any way to update the blueprint to make notifications for Android persistent (not able to be swiped away) during the initial update all the way until the final update.
I basically want the notification to be persistent until the final update is complete, only then can you swipe away the notification.
I’ve enabled alert once and that’d working fine. However, if I swipe away the initial notification, I’ll get another notification with sound for the final update.
In the newer versions of android all notifications (even persistent ones) can be swiped away. Setting a notification as persistent, only prevents swiping it away from the lock screen unfortunately.
@SgtBatten : did i see it correct and you removed the priority:high and ttl:0 ? i am pretty sure you had it in the old Blueprints to make the notification delivery faster and more reliable
EDIT: I took a look into the yaml and saw that you made it a “default”.
Is it possible that the “Timeout” in the Timer Settings is the issue of the delay?
As far as i understand it waits in default configuration 2 Minutes till it sends out the notification because there could be an updated MQTT information.
Thanks for your very useful work!
I’ll appreciate any guidance please as I’m losing hairs trying to get a video clip to embed in a notification on iOS.
GIFs and static images work inside the notification
m3u8 video links play inside the browser (chrome on iOS), but the same m3u8 video url won’t play inside a notification. Current config showing “Failed to load attachment. The given URL was invalid.”
Frigate 0.16. As an addon on HA on a Mac through VMware Fusion
Bridged networking.
Frigate Ports: 8553 (instead of 8555) for WebRTC over TCP and UDP
rest of ports disabled
Frigate reporting on MQTT
Frigate integration configured on :5000
Frigate-native WebRTC enabled
Unauthenticated notification event proxy enabled
Media browser enabled
Currently abroad so testing only with remote Nabu Casa address.
Cameras tested:
Ring cam > Scrypted FFmpeg (UDP) restream > Frigate (detected video/audio codecs by scrypted: h264/opus, detected H264 oddities: {“fuab”:true,“stapb”:true,“mtap16”:false,“mtap32”:true,“sei”:true,“reserved0”:true,“reserved30”:true,“reserved31”:true})
Reolink directly to frigate
Frigate config:
mqtt:
host: 192.168.50.XXX #Insert the IP address of your Home Assistant
port: 1883 #Leave as default 1883 or change to match the port set in yout MQTT Broker configuration
topic_prefix: frigate
client_id: frigate
user: XXXXXXXX #Change to match the username set in your MQTT Broker
password: XXXXXXXX #Change to match the password set in your MQTT Broker
stats_interval: 60
tls:
enabled: false
go2rtc:
streams:
inside:
- ffmpeg:http://192.168.XX.XXX/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=frigate&password=XXXXXXX
inside_sub:
- ffmpeg:http://192.168.XX.XXX/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=frigate&password=XXXXXXXX
ringentrancecam:
- rtsp://192.168.50.XXX:41763/XXXXXXXXXXX #SAME IP AS HA - REBROADCAST LINK FROM SCRYPTED
cameras:
inside: #Change this to a name of the camera that makes sense to you
lpr:
enabled: False
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/inside
input_args: preset-rtsp-restream
roles:
- record
- detect
motion:
enabled: true
threshold: 49
contour_area: 10
improve_contrast: true
detect:
enabled: true
fps: 5
record:
enabled: true
retain:
days: 0 #The number of days a recording will be kept for after a motion is detected.
mode: motion
alerts:
retain:
days: 20
detections:
retain:
days: 30
review:
alerts:
labels:
- person
- knife
detections:
labels:
- person
- knife
objects:
track:
- person
- knife
ringentrancecam: #Change this to a name of the camera that makes sense to you
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/ringentrancecam
input_args: preset-rtsp-restream
roles:
- record
- detect
detect:
enabled: true
height: 720
width: 1280
fps: 5 #This is the frame rate for detection, between 5-10 fps is sufficient.
record:
enabled: true
retain:
days: 0 #The number of days a recording will be kept for after a motion is detected.
mode: motion
alerts:
retain:
days: 20
detections:
retain:
days: 30
objects:
track:
- person
- car
- motorcycle
- knife
review:
alerts:
labels:
- car
- motorcycle
- person
- knife
required_zones:
- maresfieldboundaryzone
detections:
labels:
- car
- motorcycle
- person
- knife
required_zones:
- maresfieldboundaryzone
zones:
maresfieldboundaryzone:
coordinates: XXXX
inertia: 3
loitering_time: 0
version: 0.16-0
semantic_search:
enabled: true
reindex: false
model_size: small
detect:
enabled: true
record:
enabled: true
retain:
days: 0
mode: motion
alerts:
retain:
days: 20
detections:
retain:
days: 30
face_recognition:
enabled: true
model_size: small
lpr:
enabled: true
classification:
bird:
enabled: true
detectors:
cpu1:
type: cpu
cpu2:
type: cpu
I really don’t know but ever since this iOS video thing happened it’s probably not possible to send the video like you used to. However the gif is pretty awesome on android so is it not suitable for you?
Also sending a video will be a huge drain on data. I have mine set to send a photo normally and a gif when on wifi