The blueprint you asked me to look at does not send a gif. Indeed some people describe it like a gif in the thread but it does not send a gif, it is a video.
This blueprint already has a link to the clip as an optional action button, which is what I was asking about.
As I’ve been discussing above adding a video link is easy, working out the best delay to use is the challenge as it will be different for each event.
To be clear I created the video tag in the Companion app. It takes an mp4 video as an input, pulls 5-10 key frames, and then displays them as if they were a gif. Works great for me but definitely depends on the quality of the recording, iframe interval, resolution, etc
Ahh okay so that is built into the app. That’s interesting and clears up a few things I was reading in other threads.
I was hoping someone could help me. I have everything working with this blueprint except for when I receive a notification and I select it to view the clip, it tries to play a file that doesn’t seem to exist.
192.168.0.167:8123/api/frigate/notifications/1682727070.915402-xyvk8m/frontyard/clip.mp4
Im running the latest version of Frigate. Maybe I’ve missed something?
This is the configuration for the camera that I would like to work with.
I’ve worked it out, it seems it’s not compatible playing from a h.265 stream. Works perfect with my other camera.
I guess that’s a limitation of the browser more than anything else?
Hello.
I like the blueprint and its working fantastic.
But, Is it possible to use telegram instead?
Not currently. Could you make a feature request on github so it can be worked through collectively.
The same problem exists with this fork as with the original blueprint.
Cooldown of notifications does not work. When motion is detected in a zone the notification fires constantly despite the value set in the blueprint.
Does anyone have a workaround ?
I started using this BP since yesterday and I absolutely love it, but I guess the same. Cooldown doesnt seem to work correct?
@lee_evo and @sammyke007 I just tested it on my beta test notification and it worked fine. I am fairly sure cooldown has not been changed recently so stable should be the same. So, i will need some more information. Perhaps bug report on github where you can gather data?
I set the cool down to 40s and walked outside to trigger my notification. I then stepped inside for 15 seconds then walked outside again. In my trace history i have 2 traces as a result. The first fired and the second bypassed the notifications due to the cooldown. conditions/2 is the cooldown condition.
I think I’ve found little glitch in this automation. I have some cameras that work and others that don’t. I think it’s related to the fact that the camera name is different in frigate and home assistant.
I had already added my driveway camera via the ONVIF plugin, so now that the frigate version is camera.driveway_3 (even though the camera is just names driveway in frigate) none of the automations seem to trigger…
any way to change the logic on how it derives the camera name?
Yes that is known behaviour and I tried to describe it in the input description. I wanted to make entering camera names very easy with the automated drop down and that means it pulls the entity IDs from home assistant.
You should be able to edit the camera entity in yaml mode to remove the _3 though. Let me know if you can’t.
I just added double-take to my setup and am wondering how I can integrate it with the Frigate notification blueprint. Am I correct to assume I would use the “State Filter Entity”?
For my use case I’d like to receive a notification for unknown faces, so I believe I’d set the entity to double_take_unknown, but I’m not sure what state I would specify from there.
Hi,
Just been considering this and I think it will be a difficult one to implement accurately.
The issue is that every event starts with an unknown face. Even if it gets a good match later, the initial event and notification would occur before that.
So to do such a thing would require a delay until either a match is made (to end the automation) or the event ends (which is the only time we can confirm there was no match)
It’s possible, but will need some work and you may not like the delay.
Unfortunately I realise unknown matches would probably be the most common desirable notification however getting an actual face match is easier to implement than not getting one.
Regarding the state filter entity. I imagine you would need to make a seperate template binary sensor that turns true when the double take entity has been recently updated and fakse after a minute or two. So that is doable with current code but not a perfect solution by any stretch
I was able to, but now i have to change every automation and ui reference accordingly. Annoying, but the blueprint is otherwise so well done it’s probably worth it.
Thanks
An alternative (more work now I know) is to rename the ONVIF entity to be _4 and the frigate entity to not have a number. Depends on how many other references each pathway messes up on which way is better for you. The original version of the blueprint was a text field but I felt it caused more mistakes than this method.
I could strip out any endings of _x I suppose. My hesitation was that people might have multiple cameras with the same name in frigate and actually use _1 and _2 in their frigate config. Probably less people than experience the issue you do though, so I’ll look into it.
Forgive me if I am missing this feature, but I have searched the thread and came up empty. Is there a way to pass the time of the event in this blueprint? Much like a {{ label }}? For example, I want have my message state “A person was detected on the front porch at XX:XX PM”
Is that doable?
Thanks,
Scott
I think i have it working as {{event['after']['start_time']|timestamp_custom('%H:%M')}}
Would I place that in the message field itself? If so, I did that and got this:
Error while executing automation automation.frigate_notifications: UndefinedError: 'event' is undefined