[Blueprint] Frigate Vision - AI-Powered Notifications with LLM Recognition, Cooldowns & Multi-Cam Logic (v0.9) 🚨

Firstly, credit where credit is due! A lot of this automation was inspired and even copied from both @SgtBatten’s Frigate notification Blueprint and @valentinfrlch’s LLMVision Blueprint. If anyone has an issue with content or code, please reach out.

Frigate Vision

After sharing a screenshot of one of my Frigate automations the other day, a few of you asked if I had a blueprint. At the time I didn’t… so I sat down, taught myself how to build one and here it is!

Introducing Frigate Vision; a blueprint designed to bring intelligent notifications and AI object recognition to your Home Assistant setup, powered by Frigate, LLMVision, and Home Assistant.


:page_facing_up: Get the Blueprint:

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.


:bulb: What Frigate Vision Does

  • :rotating_light: Listens for new Frigate detection events from any camera you choose using MQTT
  • :brain: Integrates with LLMVision to enrich notifications with event summaries
  • :clock3: Enforces per-camera cooldowns so you’re not spammed when a squirrel does laps in your yard
  • :iphone: Pushes mobile notifications with custom text, camera names, and optional sublabels (e.g., who or what was recognized)
  • :jigsaw: Uses input helpers so you can easily reuse this blueprint across cameras without editing YAML
  • :control_knobs: Debug mode lets you preview all variables and logic without sending notifications

🛠️ Why I Built It:

I’ve used @SgtBatten’s reworked Frigate notifications for years and finally decided to break it down and recreate it to my liking. It started out as a fun project, but once I discovered LLMVision and the ability to generate dynamic event summaries from clips, I was hooked.

I’ve since spent time crafting what I felt was the ultimate smart notification setup for me. The blueprint includes 3 built-in notification actions and is currently optimized for Android (with iOS support planned). This is still a beta version, but it’s what I’d call mostly complete—and I’m already planning to add more customization options like SgtBatten’s original in future releases.


:gear: Requirements:

  • Frigate installed with MQTT events enabled
  • LLMVision installed and configured
  • Home Assistant mobile app (for push notifications)
  • An input_boolean helper for multi-camera queuing
  • A dashboard to use as a landing page (used for LLMVision event summary widget)

:construction: Current Version: v0.9

It’s working great in my setup, but I’m calling it a “beta” for now until I squash a few quirks and gather feedback.


:telescope: Coming in v1.0:

  • :soap: Cleaner debug logs & error handling
  • :green_apple: iOS support (notification actions + formatting tweaks)
  • :control_knobs: More customizable notification action sets

:brain: TL;DR:

Frigate Vision makes your HA notifications smarter by blending real-time detection with AI object recognition and smart logic; all wrapped in one reusable, configurable blueprint.


I’d love your feedback, ideas, bug reports (via github please), and feature requests. If you use it and like it, drop a comment; let’s make Frigate Vision even smarter!

Cheers,
Zach

P.S The automation and blueprint was all cooked up by me, but I’m lazy and had AI assist with writing this forum post. :slight_smile:

3 Likes

I look forward to testing this out.

1 Like

Definitely no where near as customizable as yours but you basically single-handedly taught me how to build an automation and blueprint in YAML, so thanks!

I’d be honored to get your opinion.

Thank you so much for building this blueprint and sharing it with the community! I have to try this out.
If you have any questions about LLM Vision feel free to reach out!

Much appreciated, at first the only question I had was if I can view the frames that get sent to the LLM, then I was building this and re-read the expose_images option and realized it’s already done!

Oh, actually I do have one, when using the retry time option, how does that work exactly?

i.e
Retries = 4
Time = 60s

Does it:

  1. Try to send 4 times over 4 minutes total
  2. Try to send 4 times over 1 minute (every 15s)

Thanks for making the tools to allow stuff like this!

Do you mean the frigate_retry_attempts and frigate_retry_seconds options? If so, your example would attempt to fetch the video from Frigate every 60 seconds, up to a maximum of 4 attempts.

If you want to take a look at the implementation, the relevant part is here: ha-llmvision/custom_components/llmvision/media_handlers.py at d0adc2a0b2905bd4ea91c33afc423882daa5e5ee · valentinfrlch/ha-llmvision · GitHub

Ah, yeah that’s exactly it. Thanks! I figured that’s how it worked but wasn’t too sure. Much appreciated!

1 Like