Did a couple more tests and got a trace that looked more normal. Here it is.
It used to be. Now that is built in and critical is used as an actual critical notification. Keep it off for now.
1 Like
Your trace shows the initial notification conditions were not met, only the conditions during the subsequent loop.
If you are using custom action Auto it has the same conditions and did not trigger.
If you are using custom action auto multi it should have triggered, but i can se it did not so suspect you are not using this. Note this will trigger multiple times.
I may need to consider flexible conditions in the future but they are fixed currently.
you should be able to see where I have screenshot this from your trace.
The arrow points to the custom action section. If you click the square below it. it will show the conditions were not met, hence it bypassed.
hereās what I got.
alias: Frigate Notify Driveway Car Detect NEW
description: SgtBatten 0.12.01r Blueprint w/ TV
use_blueprint:
path: SgtBatten/Beta.yaml
input:
camera: camera.driveway
notify_group: notify.family
alert_once: true
zone_filter: true
zones:
- monitor_car_detect
labels:
- car
cooldown: 90
custom_action_auto:
- service: script.display_driveway_pip_popup_on_tv
data: {}
Iām also having issues w/ reliability of notifications to notify.family group. Weāre not getting all the notifications, though Frigate is capturing and sending them to frigate,
Notifications are also REALLY late, and sometimes donāt fire for some cameras in this new version. Itās real spotty. Frigate is capturing the events, Home assistant SAYS they are going off, but they arenāt.
Iām sorry but you last 3 posts arenāt really giving me anything to look at. Nothing has significantly changed with how we trigger and send notifications here, just more options.
Does reverting change anything?
Did you try individual notifications for each device?
Is it all devices, and if not is it the same device or operating system?
Define late and how you are monitoring it.
Is the hardware of the server adequate?
Did you try without the script?
Is reception reliable?
What are the traces saying when you dive into the steps for the notifications being sent in terms of time (and success)?
These are just some of many follow up questions that I have depending on what information is available. You may prefer to raise a GitHub issue.
Itās actually the weirdest issue. Iāve gone back to the original notifications ( I had just disabled the older ones while trying the new blueprint ) and for all cameras, Itās completely random. The only thing that has changed is Iām using the Frigate+ models ( shouldnāt have anything to do with this ). Iām getting random false positives say in my driveway, but when a car pulls in, I get nothing. Looking at the traces for actual positives, it skips right to the bottom, as I showed above. Iāve restarted home assistant completely actually shutting down the vm and restarting, have updated MQTT, and the issue persists. Itās really the strangest thing. I can call the service to notify the group, and I received the message on all cell phones assigned instantly.
Iām so confusedā¦ This was working on the old blueprint, I switched my Frigate box to unraid instead of a dedicated linux box and now Iām unable to get the notifications working. Even worse, for fun I sent my notification to my new Pixel watch and it worked the first time. Now, it wonāt re-push to it or my phone. This makes no sense. Any ideas?
Iāve uninstalled and re-installed the Frigate integration, frigate card, and blueprint. Restarted HA and Frigate multiple times to no avail.
Frigate Integration: V5.0.0beta 2 (thought it would help to go Beta?)
Frigate Card: v5.2.0
Blueprint: (0.12.0.1r)
Iāve also tested a dummy automation notification for HA to my phone and it works, so it doesnāt appear to be a permission issue on my phone / device.
What are you referring to specifically?
Which old blueprint?
How did you send it?
Did you build the automation from scratch? Depending on where you came from several options are different. Critical for example, I not you have it true but you probably shouldnāt any more. This is not causing your issue though. But something else could be.
I have not had time to install the beta. Some other users said it was working with a few quirks to be fixed.
Please share your automation config
Please share a screenshot of the top half of a trace at minimum
Please share your frigate camera name from your frigate config.
Check your zones coordinates look correct in frigate debug. Iāve had mine move before. Or if your resolution is different it will be wrong.
So hereās what Iāve found. And what Iāve done. Iāve taken my home assistant off the VM, gave itās own heavy metal, i3 10th gen with 16gb of ram and dedicated 1gb network connection. CPU util. went from 60% to 20%. Went back to Frigate Notifications (0.12.0.1). Still, hit or miss notifications. But even the developer tools would be hit or miss.
Followed the instructions here: Critical notifications | Home Assistant Companion Docs
and added data: ttl 0 and priority high to my test notification:
alias: 1_Test Notify
description: ""
trigger: []
condition: []
action:
- service: notify.family
data:
message: This is a test
title: Testing
data:
ttl: 0
priority: high
mode: single
Now, my phone can be screen off, an hour of idle, on, being used, and I get it instantly. So it looks like the HA app for android at least still requires that level of code in the notifications. How do I add it to my frigate notifications?
Yes you are correct, it does require it to prevent delays. It is hard coded in the current beta.
For the stable release use critical true to add it.
Yeah, the problem is, the Beta wouldnāt send instant notifications. Neither is the old that does have critical set to true. They were working for the longest time. Once I installed the beta, to try to get the video feeds to launch on my TV, the old ones have stopped working. Iād say they work about 25% of the time.
Stable hasnāt been changed in months.
Please try removing the most troublesome phone from the group (or donāt but change the group and tag fields so it is a different notification) and set it up as a single device notification.
Then let us see if there are any reliability differences.
But still, most of my questions from earlier remain the same
Itās just two phones, and they both exhibit the same issue. One phone doesnāt get the notification over another. Sometimes one will get it up to 1 min or even 10 minutes prior to the other, but when I use the notification with the critical as explained earlier, they both get them immediately, just not the frigate automation notifications. During testing, they are sitting right next to one another, on wireless, so nothing has changed from when they were previously working. I donāt know enough about coding to go through the traces and figure out whatās doing what when and if itās correct or not.
Could you please start a github issue as it will become difficult to follow the conversation here.
I do need lots of data to be able to figure it out.
Traces (screenshots of the trace tree) will be important.
If you have the ability to trigger an event and then observe a 1-10minute delay in notifications i need to see the trace and the timestamp on both phones.
Please enable debug, Please also keep more traces than the default 5 as they disappear to quickly for us to do any back and forth discussion on a particular one. I recommend 50 or 100 traces during troubleshooting.
@SgtBatten Hey, I seem to get more issues with the time.
- Notification Colour is set to red, but nothing is different
- Some Snapshots in the Notification show the square around the person some not
- The Icon for the notification is not shown
- Tried all settings under URLs but nothing works, everything gets opened in the browser, rather than in the APP.
- Live view for iPhone not working
I have deleted the whole notification and set it up all new again, but that did not change anything.
Any idea for troubleshooting maybe?
That is still my code:
alias: Benachrichtigung_Eingang_Ole
description: ""
use_blueprint:
path: SgtBatten/Stable.yaml
input:
camera: camera.eingang
notify_device: e6200f10cfb6a42fdfa1c69320f4b6b3
message: Eine {{ label }} wurde erkannt.
title: š¹ Eingang
attachment: snapshot
color: red
icon: >-
mdi:{{'account-outline' if label == 'Person' else 'dog' if label == 'Dog'
else 'cat' if label == 'Cat' else 'car' if label == 'Car' else
'home-assistant'}}
tap_action: /lovelace
sound: none
debug: true
button_1: Aufnahme ansehen
button_2: Snapshot ansehen
url_3: "{{base_url}}/lovelace"
button_3: Home Assistant ƶffnen
url_1: "{{base_url}}/api/frigate/notifications/{{id}}/{{camera}}/clip.mp4"
url_2: "{{base_url}}/api/frigate/notifications/{{id}}/snapshot.jpg"
Colour and mdi icons only work for android.
I did some work for iOS icons but itās not mdi and I donāt think anyone got it working anyway. Also, not in stable.
How are you setting it? Both ways are flawed regardless.
If set within frigate, it needs processing time which means it often doesnāt happen.
If set within the attachment input, it only works while the event is active so if you get a final image sent at the end of an event itās possible the event ends before the snapshot is downloaded and therefore the snapshot wonāt have the boxes. Iāve already set a delay for the final notification to give frigate time. Nothing more seems possible on this one.
Likewise, this is also beyond control of the blueprint. Youāve done what you can with the URL. The rest is up to device settings (for remembering how to open urls) and the HA Devs. Iāve no idea what is the reason.
For live viewā¦ It should just be there once you hold down on the notification I think. Did you change it to true since you last posted your config?
Hi, thanks for letting me know. It puts my mind to peace knowing that this behavior is not coming from any misconfiguration on my side.
Iāll leave it to a basic configuration then for the time being.