My branch of this plugin is only modified to add TTS. I investigated the trace and it always fails where it checks for {{ not labels|length or object in labels }}, even though the variables passed in should check out:
object: car
label: Car
initial_home: false
initial_entered_zones:
- driveway
title: ''
message: Car detected on the Front Porch camera
button_1: View Clip
button_2: View Snapshot
button_3: Silence New Notifications
custom_url: /api/frigate/notifications/1706136021.859487-w5406z/snapshot.jpg
icon: mdi:home-assistant
I tried capitalizing the label in the blueprint but that didnât change anything.
What could cause frigate notifications to come through without any screenshot or seemingly any linked events at this time? It can happen up to 10 times a day. Itâs the same issue on all devices.
I am using frigate 13 RC but I think Iâve had this issue on and off over the last year or so.
I think itâs related to false positives?? But Iâm not certain. Perhaps frigate starts an event and then cancels it?
I am using the latest stable blueprint.
The setting is set to thumbprint and update attachment is enabled.
Okay Iâm not sure what happened but the notifications seem to be working now. Config is the same, except I removed the street zone and now I only get driveway notifications (which is what I originally wanted, although a list should work?). Perhaps this was a timing issue that removing alert_once would have fixed? Iâll keep an eye on how reliable the automation is.
Iâm testing the latest stable branch now, and Iâm getting an error in my Home Assistant logs:
Template variable warning: 'loitering' is undefined when rendering 'A {{ label }} {{ 'is loitering' if loitering else 'was detected' }} on the {{ camera_name }} camera{{ ' in the ' + entered_zones if entered_zones else '.'}}'
Template variable warning: 'entered_zones' is undefined when rendering 'A {{ label }} {{ 'is loitering' if loitering else 'was detected' }} on the {{ camera_name }} camera{{ ' in the ' + entered_zones if entered_zones else '.'}}'
Fibetv: android tv box
65_tcl_roku_tv: Roku TV (roku integration)
Chome_alone: Google Chromecast
kitchen_display: Google nest
The first 3 are all in the same TV, just different devices. So I pause the android box if itâs playing, cast to the Chromecast on the same TV which automatically switches inputs, as well as the kitchen display, and switch inputs back on the roku to whatever it was before, resume the android box if it was playing before. If the roku was off then it just shuts the TV back off at the end instead.
I use HAOS on Intel NUC w/ the most recent HA update, Frigate, and this Blueprint. I am having trouble receiving group notifications. Everything works great notifying devices individually.
I have the device set in the Blueprint and the group name filled in.
When I start Frigate I get an error:
" Frigate Notifications (0.12.0.2) uses an unknown service" The automation âFrigate Notifications (0.12.0.2)â (automation.frigate_notifications_0_12_0_2 ) has an action that calls an unknown service: notify.all_devices .
I hope I provided enough info, any help would be greatly appreciated. I am surprised I made it this far!
Instead of service: notify.all_devices you should set it to service: all_devices in the blueprint config. I got stuck on this very thing today as well. This fixed it for me.
I was going from memory and working off of the content of the reply. I should have been more clear. In the frigate notification blueprint, under Notification Group, simply type the name of the notification group, not the notify.groupname.
Hello. I found this Blueprint today and it seems great. Iâve installed it and setup notifications for my cameras but when I walk out and stand in front of the cameras I get no notifications on my phone. Iâm probably doing something wrong.
Using Home Assistant OS with Frigate and MQTT installed. Iâm using a Pixel 4 XL phone.
Here is the YAML version of my settings for one camera. Its the same for the others.
alias: AC Side Camera Notification
description: Something Was Detected On The AC Side Yard
use_blueprint:
path: SgtBatten/Stable.yaml
input:
camera: camera.rear_corner_ac_side
notify_device: f7601e5c6661aa47a2b4da047ca088af
critical: "true"
attachment: snapshot
labels:
- person
- dog
title: Something Was Detected In The AC Side Yard
message: "Default: e.g A Person was detected on the AC Side camera."
state_filter: false
state_entity: input_boolean.turn_on_camera_notifications
update_thumbnail: true
state_filter_states:
- "On"
debug: false
@SgtBatten Any ideas on why Iâm getting the loitering and entered_zones warnings above? I donât have a loitering timer defined but I would like zone notifications and Iâm not sure why that information wouldnât be coming through.
The parameters arenât defined at the time itâs being rendered, just as it says.
Change the message so it doesnât included loitering (unsure why thatâs not working but donât have time to check)
The entered_zones one might be different now without the underscore from memory. Did you start from scratch or upgrade an existing blueprint/automation?
