Ah apologies, I overlooked it. I think ‘Notification Customisations’ heading should be above, so it aligns with the rest to make it a bit more clearer?
I believe it opens in the companion app. Don’t see a URL, just this black screen with scroll bars. Is there an option to fit to screen?
There is no way to have a heading on its own line. It’s a hack to get them there at all.
do you have external access configured and the ability to use a base url?
Yes, I do, via reverse proxy.
are you not using it in the blueprint?
I am. Everything works great. Notification shows the snapshot (which I’ve configured with bounding boxes). The issue is just the ‘View Snapshot’ link which opens the Snapshot extra large.
Really interested in getting this working with generative ai. I have this blueprint working fine and my generative ai notifications working. I’m just really confused how to get them both working together. Any help would be really appreciated.
1 Like
Hi all,
Question about Critical Notification - is it expected that his option, once enabled, triggers actual sound alarm on devices to which the notification is sent? I thought, looking at the description (quoted below) this is rather a prioritization and override for silent mode of phone i.e. phone not allowing for notifications to appear while in that mode.
Send as a critical notification to the mobile device. This will ignore silent/vibrate modes.
You can choose to limit critical notifications to certain times using a template (some examples are provided but you can enter your own as long as it outputs true or false)
Since upgrading from 0.12 to 0.13 my notifications have stopped triggering quite often, the issue seems to be related to having zones enabled as required in the blueprint automation. Did anyone else notice that? I’ve tried in both STABLE and BETA blueprints. I have decreased the inertia for the zone to 1 but it did not change anything. I can see those events being caught correctly and marked as in zone in Frigate itself, the issue seems to be with the Blueprint. Any tips on how to troubleshoot the trace? It’s quite complicated and I struggle figuring out which step to look at…
Here’s my frigate config:
mqtt:
enabled: true
host: 192.168.0.172
port: 1883
user: XXX
password: XXX
detectors:
ov:
type: openvino
device: AUTO
model:
path: /openvino-model/ssdlite_mobilenet_v2.xml
model:
width: 300
height: 300
input_tensor: nhwc
input_pixel_format: bgr
labelmap_path: /openvino-model/coco_91cl_bkgr.txt
ffmpeg:
hwaccel_args: preset-vaapi
birdseye:
enabled: false
live:
stream_name: KLATKA_PODJAZD
cameras:
# KLATKA_PODJAZD
KLATKA_PODJAZD:
enabled: true
ffmpeg:
output_args:
record: preset-record-generic-audio-aac
inputs:
- path: rtsp://frigate:[email protected]:554/Streaming/channels/101
roles:
- record
- path: rtsp://frigate:[email protected]:554/Streaming/channels/102
roles:
- detect
mqtt:
required_zones:
- PODJAZD_PERSON_DETECT
detect:
enabled: true
width: 1280
height: 720
zones:
PODJAZD_PERSON_DETECT:
coordinates: 129,720,77,507,653,231,1075,453,1034,573,926,720
inertia: 1
objects:
- person
filters:
person:
min_score: 0.70
threshold: 0.75
record:
enabled: true
retain:
days: 14
mode: all
events:
retain:
default: 14
mode: active_objects
required_zones:
- PODJAZD_PERSON_DETECT
snapshots:
enabled: true
retain:
default: 30
mode: active_objects
required_zones:
- PODJAZD_PERSON_DETECT
motion:
mask:
- 410,24,407,0,0,0,0,25
threshold: 85
contour_area: 15
lightning_threshold: 0.5
# /KLATKA_PODJAZD
Blueprint notification in HA
alias: Frigate Notification - Klatka Podjazd
description: ""
use_blueprint:
path: SgtBatten/Beta.yaml
input:
camera: camera.klatka_podjazd
notify_device: b23093b4025bafba0d26494c6748fce7
update_sub_label: false
critical: "false"
attachment: snapshot.jpg
icon: mdi:cctv
sound: none
volume: 0
zone_filter: true
zones:
- podjazd_person_detect
labels:
- person
cooldown: 20
custom_filter: "false"
tap_action: "{{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/snapshot.jpg"
button_1: Podgląd na żywo
button_2: Nagranie
url_1: >-
{{base_url}}/api/camera_proxy_stream/camera.{{trigger.payload_json['after']['camera']
| lower | replace('-','_')}}?token={{state_attr( 'camera.' ~ camera,
'access_token')}}
url_2: >-
{{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/{{camera}}/clip.mp4
button_3: Wycisz na 10min
silence_timer: 10
base_url: https://xxxx.xxx
debug: true
message: Ktoś na podjeździe!
title: Ktoś na podjeździe!
alert_once: false
initial_delay: 0
notify_group: wszystkiekomorki
I’m running the latest dev version available as indicated above for interacting with the latest Frigate Beta 0.14 version. Everything seems working for me except my presence filter. I’ve always used a custom presence Group as defined in configuration.yaml and it always worked great but this combination is not working anymore. It simple ignores my group device tracker. It however works if I indicate a single person/device tracker. I’ve validated my group is indeed setup correct using the dev tools/states and nothing has changed except upgrading to frigate beta and latest dev beta blueprint. It continues to send me messages even while home.
Is this a new bug?
For troubleshooting purposes can you enable update attachment please and report back.
Thanks, can you please report it in the pull request on GitHub and include the debug output.
I seem to be getting delays with the 0.14 code taken from Github - I’ve sometimes managed to get inside, lock the door and walk down the corridor before they’re received. I see it mentioned by someone else above but wanted to check if it’s still a known issue or have I missed some form of update/should revert back to an earlier version? Thanks!
I haven’t figured it out yet.
No worries thanks for confirming, I’ll toggle back to the previous version and deal with the occasional false notification for now.
Hi. I want a button press to silence my frigate notifications for some time, Example, if I press the button it stops notifications for the next 30min. Do you know if this is something possible to do?
I believe that’s exactly what that feature does, however it does not impact existing events, so you may still get notifications after that, but it should affect new events.
I mean a physical button, not the silence button on the notification
Like a switch or Zigbee button? You use it to trigger an automation/script that disables the Blueprint for X minutes.
Hang on, I have something similar…
Edit - one of these booleans is used in the Frigate Notification BP as a condition. The second one triggers the second automation.
alias: Disable Surveillance Notifications For 1 hour
sequence:
- service: input_boolean.turn_off
metadata: {}
data: {}
target:
entity_id:
- input_boolean.all_object_detection_notifications
- input_boolean.frigate_notifications_sonos
- delay:
hours: 1
minutes: 0
seconds: 0
milliseconds: 0
- service: input_boolean.turn_on
data: {}
target:
entity_id:
- input_boolean.all_object_detection_notifications
- input_boolean.frigate_notifications_sonos
mode: restart
This automation triggers a few different says to make sure it all resets each day or if HA is restarted, but it disables all of my Frigate Notification Blueprints if the input_boolean.frigate_notifications_sonos is turned off.
alias: Turn frigate notifications on/off
description: ""
trigger:
- platform: state
entity_id:
- input_boolean.all_object_detection_notifications
to: "on"
id: "On"
- platform: state
entity_id:
- input_boolean.all_object_detection_notifications
to: "off"
id: "Off"
- platform: time
at: "00:01:00"
id: Time
- platform: state
entity_id:
- input_boolean.frigate_notifications_sonos
to: "on"
id: Sonos - On
- platform: homeassistant
event: start
id: Home Assistant - Starts
condition: []
action:
- if:
- condition: trigger
id:
- "On"
- Time
- Home Assistant - Starts
then:
- service: automation.turn_on
metadata: {}
data: {}
target:
entity_id:
- automation.fnvrb_turnaround
- automation.fnvrb_shop_front_door
- automation.fnvrb_front_gate
- automation.fnvrb_t_turnaround
- automation.fnvrb_a_front_gate
- automation.frigate_tts_front_gate
- automation.fnb_a_s_phone
- service: input_boolean.turn_on
target:
entity_id: input_boolean.all_object_detection_notifications
data: {}
- if:
- condition: trigger
id:
- "Off"
then:
- service: automation.turn_off
target:
entity_id:
- automation.fnvrb_turnaround
- automation.fnvrb_shop_front_door
- automation.fnvrb_front_gate
- automation.fnvrb_t_turnaround
- automation.fnvrb_a_front_gate
- automation.frigate_tts_front_gate
- automation.fnb_x_s_phone
data:
stop_actions: true
- if:
- condition: trigger
id:
- Sonos - On
then:
- service: input_boolean.turn_on
target:
entity_id: input_boolean.all_object_detection_notifications
data: {}
mode: restart
Hopefully this gets you headed in the right direction.