Nice! Will be updating v11 tonight then.
Ok so the notification thumbnail does seem to be updating on my Pixel 6 Pro! Would be nice if it was the full image cuz even with update thumbnail option it updates it but with the cropped version.
Also, so even though itās updating it still sends that blank silent notification, idk why, but at least it seems to he working on my Pixel 6 Pro.
The blank one is labelled test which means itās not coming from my latest versions. Maybe you have another automation running still?
1 Like
Hmm good point, I checked this out and it looks like it was another automation, thanks!
Basically, I was trying to test out GIF previews instead of the still snapshots, and as you can see it clearly didnāt work.
Turned that one off, sorry for the confusion haha.
1 Like
Good morningā¦
What an awesome workā¦thx for this great blueprintā¦works so far i was hoping for besides that i dont have access to video clip or picture, but i am still tinkering on that.
But i really qould love to know is, is how to add more than one person to the āonly notify when xyz is not homeā list.
My wife and i both want to be ānot homeā to have notificatuons triggeredā¦
Thx alot for any ideas
Hi SgtBatten,
thanks for your support. I can define a group in my configuration.yaml file but this is not useful for my filter ā(Optional) Presence Filterā => I would like to use devices which change from āhomeā to ānot homeā. For this filter i have to use an entity which is only a single device. How i can consider two devices in the given blueprint?
If I should use a group (you suggested it) then i have to use my new group āwifeandiā into notification group. This would send a notification to all devices which is defined under the group āwifeandiā (here: two devices). But this would not consider the presence of my wife (home / not home).
Please correct me if I didnāt catch the function of notification group. Is it possible that you can show me an example with the given blueprint?
Thanks!
Thatās not true. If you create a group containing two entities that give the home or not home state (such as person entities in the example I gave you) then the group also has home and not home states.
My example was not a notify group. It is an entity group.
@Darkyputz oddly you have asked the exact same question and the answer is the same. You can use a group just as it says in the blueprint description.
Call me crazy but I cannot get @SgtBatten or @davidnestico Blueprint to trigger. I only have the camera name configured and the notification group. Am I missing something obvious?
In Frigate, I have person detection working and sending events. I also have set up a MQTT automation to send push notifications and it works.
Can someone help point where I can start to troubleshoot why it wonāt trigger?
Here is my YAML.
alias: Frigate Automation
description: ""
use_blueprint:
path: SgtBatten/frigate_0.10_notification.yaml
input:
camera: camera.driveway_south_2
notify_device: 0ba5914ea14670d18a944dfb05f6fdd1
zones: {}
labels: {}
Hmm itās been working great for me.
This is what mine looks like:
alias: FRIGATE - NEW SILENT TEST - DRIVEWAY all notifications
description: Testing on DAVIDS DEVICES FIRST before all devices switch to new blueprint
use_blueprint:
path: hunterjm/frigate_0.10.1_notification.yaml
input:
camera: camera.driveway
notify_group: davids_notify_devices
alert_once: true
zone_filter: true
zones:
- driveway_pavement
- driveway_path
- driveway_car
labels:
- person
- dog
- car
update_thumbnail: true
I will try it with your YAML but modified to my parameters and get back shortly.
1 Like
No luck. Time to keep digging.
1 Like
Hmm, strange. Not sure why it wouldnāt be working.
@SgtBatten might be able to help better since he is the one is writing the code.
Hey mate.
For the path, stick with your first example. David uses the same code but pasted it into that hunterjm file so his path is different only for that reason.
The first suspect I have is that the camera entity ends in _2. Do you actually have two driveway south cameras?
1 Like
I have fixed the _2. It looks like something was lingering around from when I started with HA. It no longer exists.
For the record your blueprint config looked fine. So the issue is with triggering it, which means we would be looking at the entities frigate creates and ensure they exist with the right names and are working as expected. Then the likely culprit is mqtt, check the logs for any errors
Just to verify, I only need the camera entity. I donāt need the camera.person entity or any other camera related entities correct? With regards to the mqtt, the information is coming through from frigate->mosquitto->ha with all the variables.
Just an update. Here is the mqtt data I receive:
{
"before": {
"id": "1666136546.454753-70wefj",
"camera": "Driveway_South",
"frame_time": 1666136559.136452,
"snapshot_time": 1666136559.136452,
"label": "person",
"sub_label": null,
"top_score": 0.82421875,
"false_positive": false,
"start_time": 1666136546.454753,
"end_time": null,
"score": 0.76171875,
"box": [
622,
356,
803,
763
],
"area": 73667,
"ratio": 0.44471744471744473,
"region": [
408,
210,
1012,
814
],
"stationary": false,
"motionless_count": 4,
"position_changes": 1,
"current_zones": [
"driveway"
],
"entered_zones": [
"driveway"
],
"has_clip": true,
"has_snapshot": true
},
"after": {
"id": "1666136546.454753-70wefj",
"camera": "Driveway_South",
"frame_time": 1666136559.711958,
"snapshot_time": 1666136559.136452,
"label": "person",
"sub_label": null,
"top_score": 0.82421875,
"false_positive": false,
"start_time": 1666136546.454753,
"end_time": 1666136566.118437,
"score": 0.5234375,
"box": [
618,
641,
710,
790
],
"area": 13708,
"ratio": 0.6174496644295302,
"region": [
355,
0,
1783,
1428
],
"stationary": false,
"motionless_count": 0,
"position_changes": 1,
"current_zones": [
"driveway"
],
"entered_zones": [
"driveway"
],
"has_clip": true,
"has_snapshot": true
},
"type": "end"
}
i think you have found a flaw in my edited blueprint, at a glance, it might not handle capital letters.
I can test it real quick lowercase letters.
i think I have a solution maybe, I could go back to the original method of typing the name into the automation manually, but I wanted to try selectors, hence why itās now broken.
Edit: Iāve fixed this now using the advice below of the lower command.
2 Likes
So I reloaded my Frigate cameras with lower case letters and it now works with the latest version from your GitHub Gist. So it is confirmed that capital letters in Frigate is a problem. I would have never caught that.
I tried your blueprint you posted and had no luck. I think there was an issue with the iif statement. I am working on trying to fix it now. I wonāt guarantee I can fix it.
1 Like