I think to use this blueprint and it’s conditions as a trigger you would need to go with the custom action version.
My understanding is that customer notification was only in the beta version
You would need to be using this specific blueprint. https://raw.githubusercontent.com/SgtBatten/HA_blueprints/custom_action/Frigate%20Camera%20Notifications/Beta
It has a field for you to create an action such as the TTS one you are trying to trigger within the blueprint. I’ve been waiting on people to try it out.
1 Like
not sure how to set MQTT Topic (Advanced)
Just leave it alone. frigate/events is the default
Not sure why but it doesn’t work.
I have copied the same same setting of version (0.12.0.1), a part from custom actions, but no sign of life
alias: Frigate Notifications (0.12.0.1a)
description: ""
use_blueprint:
path: SgtBatten/Beta.yaml
input:
camera: camera.piazzale_1
notify_group: you_and_me
base_url: http://xxxxxx.duckdns.org:8123
title: Una persona è stata avvistata nel piazzale
zone_filter: true
zones:
- zone_1
labels:
- person
tv: true
tv_interrupt: true
custom_action:
- service: tts.cloud_say
data:
cache: false
entity_id: media_player.casa
message: Ciao Ciao
- type: turn_on
device_id: 858505f11532263394f6abc227caca71
entity_id: 37ff657903b0489c4d5ea6e5c1b39d58
domain: switch
- type: turn_on
device_id: 1835a64aef6060bcc690223ab4e2083a
entity_id: cea1c545a51195748750cfa5e23b2a3e
domain: switch
- type: turn_on
device_id: f3c750f7a0c375236cc6a56bf04cb0be
entity_id: 5ee08c72a4f92c5ea3f36c315f63f74a
domain: switch
- delay:
hours: 0
minutes: 0
seconds: 30
milliseconds: 0
- type: turn_off
device_id: 858505f11532263394f6abc227caca71
entity_id: 37ff657903b0489c4d5ea6e5c1b39d58
domain: switch
- type: turn_off
device_id: 1835a64aef6060bcc690223ab4e2083a
entity_id: cea1c545a51195748750cfa5e23b2a3e
domain: switch
- type: turn_off
device_id: f3c750f7a0c375236cc6a56bf04cb0be
entity_id: 5ee08c72a4f92c5ea3f36c315f63f74a
domain: switch
mode: single
debug: false
Version (0.12.0.1) is working well
alias: Frigate Notifications (0.12.0.1)
description: ""
use_blueprint:
path: SgtBatten/Stable.yaml
input:
camera: camera.piazzale_1
notify_device: b76118c030e61eef2c2eee37a5d0fc0e
attachment: thumbnail
base_url: http://xxxxxx.duckdns.org:8123
labels:
- person
title: Una persona è stata avvistata nel piazzale
zone_filter: true
zones:
- zone_1
tv: true
notify_group: you_and_me
tv_duration: 24
tv_interrupt: true
Are there any traces, or is is not being triggered at all?
Forcing it won’t ever work.
The trigger needs only two things. An mqtt message from frigate that contains the first message if a new event, and a matching camera name.
For simplicity, can you do a fresh automation and just set the camera and device or group.
If it trigger, then add the custom action.
If it doesn’t, that blueprint might be broken and need some changes.
Done
alias: Frigate Notifications Test (0.12.0.1a)
description: ""
use_blueprint:
path: SgtBatten/Beta.yaml
input:
camera: camera.piazzale_1
notify_device: b76118c030e61eef2c2eee37a5d0fc0e
title: Test
labels:
- person
No triggered
Okay, then I will need to look at it another day to see why it is not triggering. It is fairly outdated now so I can modernise it and try again.
1 Like
Trying and updating from 0.11_0_13_beta to the latest beta 0.12.0.1l and I encountered some problem and the new automation does not trigger as expected.
This old one triggers as expected:
alias: Frigate Notification (0.11.0.13) - SgtB Besder 1
description: Besder 1
use_blueprint:
path: hunterjm/frigate_0.11_0_13_beta_SgtB_notification.yaml
input:
tv_transparency: 0%
camera: camera.besder_1
notify_device: b38a02f85da3e9293df77c27524f8b77
tv_size: large
state_filter: true
tv_position: center
alert_once: true
update_thumbnail: true
color: grey
state_entity: binary_sensor.template_binary_someone_home
state_filter_states:
- "off"
But this, the new one does not trigger at all:
alias: Frigate Notifications (0.12.0.1l) Besder 1
description: Frigate Besder 1
use_blueprint:
path: SgtBatten/Beta.yaml
input:
camera: camera.besder_1
notify_device: b38a02f85da3e9293df77c27524f8b77
update_thumbnail: true
state_filter: true
state_entity: binary_sensor.template_binary_someone_home
state_filter_states:
- "off"
when I change row 695 in SgtBatten/Beta.yaml
from:
camera: "{{ input_camera | regex_replace('^camera\\.|_\\d+$', '') }}"
to something simpler:
camera: "{{ input_camera | replace('camera.', '') }}"
it triggers as expected.
It looks likes there is a problem with the regex expression.
Long story short, intentional change. Many new HA users end up with duplicate entities causing the entity ID to end in _x. This makes it not an issue for them.
Only in beta for the reason you have discovered, it breaks for some users who actually have camera entities ending in _1 or _2 etc.
3 solutions.
Do as you did and change the blueprint.
Use stable instead.
Add a second _1 to your camera line in the automation config as it will only remove the last one.
We are waiting on a frigate update which will mean this issue can go away. It’s already merged into their code so can’t be far off stable release.
OK, thanks for the explanation.
I have added a custom filter in this pull request. Please try this version and see fi you can satisfy your request by creating a custom template
For those of you wanting to trigger additional things with this blueprint I am currently building some options.
Anyone keen to test, please grab the blueprint from the custom_action branch here
5 Likes
Hello everyone,
Im having trouble getting this blueprint to trigger.
Ive started rather simple:
1 camera with 1 zone (zone_0)
But when de zone is entered there is no notification.
I have an android phone, and using other HA automations with notifications that work.
alias: Frigate Oprit Notificatie
description: ""
use_blueprint:
path: SgtBatten/Stable.yaml
input:
camera: camera.oprit_2
notify_device: 8e207b3d5cd18918042f48defd666ad0
attachment: thumbnail
zone_filter: true
zones:
- zone_0
update_thumbnail: true
zone_multi: false
critical: "true"
message: "{{ label }} detected - {{ camera_name }}"
title: CCTV
Also tried the beta, which also does not trigger
alias: Frigate CCTV Beta Test
description: ""
use_blueprint:
path: SgtBatten/Beta.yaml
input:
camera: camera.oprit_2
notify_device: 8e207b3d5cd18918042f48defd666ad0
attachment: snapshot.jpg?bbox=1
update_thumbnail: true
zone_filter: true
zones:
- zone_0
In frigate I get snapshots linked to that zone_0 so I guess thats working.
MQTT is also getting the data.
Any idea what might be the problem?
//edit: I removed the zone filter and tried it, also no notification.
After I created a 2nd zone, the notification started comming in. I enabled the zone filtering again, and it seems to work now.
(the Beta one is working)
Your camera name in frigate is just oprit right? The _2 is why it isn’t working on stable
Beta has a temporary solution for that.
Please clarify. You had zone filter disabled and it wasn’t working, but you created a new zone in frigate and it started working? Then you enabled zone filter and it kept working.
I’m just confused by the order of events.
I recently updated to try out the snapshot/crop feature and now when I get a notification on HA application it does show up the alert on the iOS notification but the image is showing a 404 error. Clicking on the notification opens Safari and shows the image just fine.
What do you need to troubleshoot?
Running the latest Beta as of last night.
I did break it in one version so please confirm you are on beta o and paste your automation config.