Frigate AI Notification - Intelligent Security Camera Automation version 0.43

Hi, Can you check your downloader folder and see if any files have been downloaded also can you post a trace of a failed run.

It is possible to use the api directly in LLM vision for the video analyse but not the image analyse although i have not added this. The default LLM vision blueprint uses a direct link to the api without the downloader step.

Let me post my latest copy of the blueprint which has an extended time waiting for the download to complete and an option to select multiple zones required.

Version 0.3

  • [Frigate Options] Input to enable all zones required rather than any zone.

  • [Snapshot Analyse] Input to enable AI generated notification title.

  • [Snapshot Analyse] Input to enter a custom notification title if AI generated title disabled.

  • [Review Clip Analyse] Input to enable AI generated Notification title.

  • [Review Clip Analyse] Input to enter a custom notification title if AI generated title disabled.

  • [Downloader Options] Options to adjust the maximum wait time for the image and clip download to complete before retrying.

  • Continue on error added to downloader service calls

Hi all, first of all i would like to express my gratitude for sharing your achievements with us!

I would like some help please to complete my setup.
I am running HAOS on a mini pc and have frigate up and running as an addon.
I have downloaded downloader and setup a path which i have tested to be working (downloaded files from a url using the developer tools)
The path is /config/www/downloader.

I am running Ollama as a docker container and downloaded the necessary models.
I have installed the ollama integration (not sure if necessary) and LLM Vision, which were linked successfully with the ollama instance.
I have tested LLM Vision successfully using an image on the developer tools.

The problem i have is that the LLM Vision BP never triggers and I am not sure if it has something to do with the downloader path i set in the BP

In the BP options, I have set the “Downloader Directory” as “/config/www/downloader”, is that correct? what should i enter there?
The “Downloader Sub Directory” is empty.

How can I test that when a trigger is enabled on Frigate, i get a snapshot in that folder?

Thank you all in advance!

Hi can you try this path for downloader URL input.

www/downloader

You should not need to put any other quotes or forward slashes "/

Yes if the downloader action is sucessful the images/clips will be stored in your downloader directory until deleted, which you can do manually or as i do with a shell command in a seperate script/automation.

If you add a sub directory this will be created automatically as required.
examples:
with no sub directory(Downloader root directory):
www/downloader/ID123_snapshot.jpg
with sub directory:
www/downloader/subdir/reviewID123_clip.mp4

Let me know thanks.

Hi, also greatly appreciate the blueprint, it looks great!

In my instance, my frigate clips and snapshots are saved to a shared directory that’s outside my frigate docker. Is there anyway I can get this blueprint to search for the snapshots in a non-standard directory?

Hope that makes sense?

I’ll test that and let you know.
My downloaded folder is empty.
There is something I’m missing. I had a similar issue where the files did not exist when the api call was sent.
I don’t want to put the blame on your great blueprint! It probably is not.
If you have any debug steps in mind, I would really appreciate!

Thanks

Hi this BP uses the frigate API to retrieve the files so it shouldn’t be an issue as it’s not looking in a local directory

Hopefully this answers your question.

1 Like

The easiest way to check if the files exist is accessing the API directly. If you just copy the URL from the automation trace into a web browser you will find out if it does exist.

Start there along with the downloader URL change.

When I paste the url in a browser, I get an error saying not found.
Using a different url works.

For exemple, using this one : http://192.168.18.186:5000/api/frigate/notifications/1748444668.601076-lop642/thumbnail.jpg
Does not work.
This one does: http://192.168.18.186:5000/api/events/1748444668.601076-lop642/thumbnail.jpg

So basically replacing notification by events and removing /frigate/. would this means i need to setup something else on my part?

Thank you

Thanks for the reply, must be something I’m missing then!

Are you using the Frigate add on? or are you running a seperate machine?

Are you running frigate addon?

So firstly, I am terribly amateur.

But I’m running frigate and HAss in docker. I have the frigate integration via HACS and download implemented. Frigate is running and I can see events triggering. The trace on the automation completes but the api address provided does not resolve to anything. Events are happening though as they trigger the automation and I can see snapshots in the camera card that I have installed.

Honestly, I think it’s probably something specific to my setup, but if you can see anything obvious then please let me know.

Thanks :slight_smile:

Can you both try the home assistant ip address and port please

My input description should really be the Home Assistant IP address , because this is the api i am interacting with in this automation( /api/frigate/notifications/).

As you have mentioned you can access the HTTP api
(api/events).

For my part, I’m running HA on a raspberry pi and my frigate box is a separate dell computer. It is integrated to HA using the frigate proxy add on.

So I used the HA ip address as you said and now when I look at the trace timeline it looks like this:

I didn’t have that message before. Just the unknown step.

Got it, for some reason, i had the downloader subfolder filled in with www/downloader… it works now! So using the ha api linked to frigate! Now I better understand the difference… thanks so much!

Thanks for your help, my frigate and home assistant both have the same IP as they’re running in docker.

I’ve changed the port to home assistants port, if that’s what you mean, but will have to report back in the morning. Not sure my wife will be that impressed with me prancing about in front of my camera in the garden late at night :joy:

So I’m a lot closer now thanks - I changed the address and port to the Home Assistant server. I now get an error: Config entry not found. Please create the ‘Timeline’ config entry first.

Forgive my ignorance if I’ve missed a step and thanks again for your help.

EDIT:

Ok ignore the above, just needed to create a timeline entry in LLM vision!
I also have a weird error where my phone is named in 2 different ways - hence it could not send me a notification. Thanks for your help, all working now :slight_smile:

That’s good to hear well if you have any recommendations or errors let me know. Thanks