Real AI agent use cases, with sources and setup prompts
How to set up local AI security cameras with Frigate, Ollama and Home Assistant (no cloud)
Short answer: Install Frigate (free, open source) with Docker on a small Linux box, add your cameras' RTSP streams, and let it detect people, cars and animals on the box itself. Then point Frigate at Ollama running a vision model such as qwen3-vl so it writes a plain-English summary of each event ("Person left a package at the front door") without any video leaving your home. Connect it to Home Assistant with the Frigate integration from HACS for alerts and automations. Typical cost: $0 for software, an Intel mini PC for detection, and a GPU or Apple silicon Mac if you want the AI summaries to be fast. Frigate+ ($50/yr) is optional.
Real setups: a landlord whose camera reads boiler error codes before the house gets cold, a local AI baby monitor that checks a camera feed against safety rules, and agents that found strangers' cameras on a home network and an exposed doorbell camera in an Airbnb. 5 matching use cases below, each with a public source.
Open-source NVR that records your cameras and detects people, cars, animals and more in real time on your own hardware. 0.17 added AI review summaries; 0.18 (Sept 2026) added setup in the web UI and a GenAI chat. Run 0.18.2 or later for its security fixes.
Optional detection models trained on real security-camera footage, with package, delivery-logo and wildlife labels, plus up to 12 models fine-tuned on your own images.
Prices are from each official page, checked Oct 28, 2026; they exclude tax and can change. Swipe the table sideways on a phone.
Install Frigate and get local object detection
About 1-2 hours. Needs a Linux machine (Debian or Ubuntu) with Docker Engine and at least one camera with an RTSP stream. Nothing here uses the cloud.
Find your camera's RTSP addresses. Turn on RTSP in the camera's app or web page and note the main stream and the substream (low resolution). The exact path differs by brand; search '<brand> <model> rtsp url'. Test it on another computer with VLC (Media > Open Network Stream) before going further.
Create the folders. On the Linux box:
shell
mkdir -p ~/frigate/config ~/frigate/storage
cd ~/frigate
nano docker-compose.yml
Write docker-compose.yml. This is Frigate's starter file plus the device line for an Intel/AMD GPU. Remove the devices you don't have.
Start Frigate and get the admin password. Frigate creates an admin user on first start and prints the password in the log.
shell
docker compose up -d
docker logs frigate 2>&1 | grep -i password
# open https://YOUR-SERVER-IP:8971 and log in as admin
Your browser will warn about the self-signed certificate on first visit; that's expected on your own network.
Add cameras and a detector. Use Settings > Global configuration > Camera management > Add Camera for a guided setup, or edit config/config.yml directly. This example uses Intel's built-in graphics for detection, the substream for detection and the main stream for recording:
Restart with docker compose restart. For a USB Coral use a detector with type: edgetpu and device: usb instead. Then draw motion masks over timestamps and trees under Settings > Camera configuration > Masks / Zones.
Add local AI summaries and plain-English search with Ollama
About 30 minutes on top of path 1. Needs Frigate 0.18 or later and a machine with a GPU (8GB VRAM fits most 7B 4-bit vision models) or an Apple silicon Mac running Ollama. Frigate's docs advise against running these models on CPU.
Pull a vision model and expose Ollama to your network. Frigate won't download the model itself, and it runs in Docker, so it can't use localhost to reach Ollama on another machine.
shell
# On the machine with the GPU or Apple silicon Mac:
ollama pull qwen3-vl:4b
# Let Frigate (in Docker, on another box) reach Ollama:
# macOS app: launchctl setenv OLLAMA_HOST 0.0.0.0, then restart Ollama
# Linux service: sudo systemctl edit ollama -> add
# [Service]
# Environment="OLLAMA_HOST=0.0.0.0"
# Environment="OLLAMA_NUM_PARALLEL=1"
# then: sudo systemctl restart ollama
curl http://OLLAMA-IP:11434/api/tags # should list qwen3-vl:4b
Point Frigate at Ollama and turn on summaries. Add this to config/config.yml (or use Settings > Enrichments > Generative AI). Adding the provider alone does nothing: review summaries and object descriptions are turned on separately.
yaml
genai:
local_vision:
provider: ollama
base_url: http://OLLAMA-IP:11434 # not localhost: Frigate runs in Docker
model: qwen3-vl:4b
roles: [descriptions, chat] # leave embeddings to semantic search
provider_options:
keep_alive: -1
options:
num_ctx: 8192
review:
genai:
enabled: True # summaries for alerts
detections: False # set True to summarize detections too
objects:
genai:
enabled: True # per-object descriptions for search
objects: [person, car]
semantic_search:
enabled: True # needs 8GB+ RAM, AVX2 CPU
reindex: False
Restart Frigate. Use 'Refresh models' in Settings > Enrichments > Generative AI to check Frigate can reach Ollama. Existing events need a one-time Reindex for semantic search.
Tell it what's normal at your house. The summaries include a threat level from 0 to 2. Describe your household's routine so a dog walker or the cleaner doesn't get flagged. Keep it general; overly specific rules skew results.
yaml
review:
genai:
activity_context_prompt: |
### Normal Activity Indicators (Level 0)
- Our family, our dog (a black lab) and our car (grey SUV) at any time
- Mail and package deliveries 7 AM - 9 PM
- The cleaner on Tuesdays 9 AM - 1 PM
- People on the sidewalk who don't come up the driveway
### Suspicious Activity Indicators (Level 1)
- Anyone trying car or house door handles
- Unknown person in the driveway or backyard 11 PM - 5 AM
- Someone picking up a package that was just delivered
### Critical Threat Indicators (Level 2)
- Forced entry, visible weapons, or someone climbing the back fence
Search your footage in plain English. Open Explore and type what you're looking for, for example 'person carrying a box to the side gate' or 'white van in the driveway'. Click a result's 'Find similar' to see every other time that object appeared.
Get smart alerts in Home Assistant and on your phone
About 30 minutes. Needs Home Assistant with the MQTT integration and an MQTT broker (for example the Mosquitto add-on).
Connect Frigate to the same MQTT broker. Frigate and Home Assistant must use the same broker for most Frigate entities to work.
yaml
mqtt:
enabled: True
host: 192.168.1.10 # your Home Assistant / MQTT broker
user: frigate
password: "{FRIGATE_MQTT_PASSWORD}" # set FRIGATE_MQTT_PASSWORD in compose env
Install the Frigate integration. From HACS, then add it under Devices & services:
text
Home Assistant > HACS > search "Frigate" > Download > restart Home Assistant
Settings > Devices & services > Add integration > Frigate
URL: http://FRIGATE-IP:5000 (internal port) or https://FRIGATE-IP:8971 (login)
Media source must be enabled in Home Assistant for clips to show in the Media Browser. For an AI agent that controls Home Assistant, see our Home Assistant agent guide.
Or use Frigate's own push notifications. Frigate can send browser push notifications that already include the AI title and short summary. It needs HTTPS, a signed-in Frigate user and a supported browser (Chrome, Firefox or Safari). Push messages go through the browser vendor's push service.
yaml
notifications:
enabled: True
email: "you@example.com"
cooldown: 10 # seconds between notifications from any camera
Check alerts away from home without opening ports. Install Tailscale on the Frigate box and your phone and open https://FRIGATE-TAILSCALE-NAME:8971. Don't port-forward 5000 or 8971 on your router.
Copy-paste prompts
Written for this setup. Replace anything in [brackets] before you send it.
1. Write my Frigate config
Before path 1 step 5, in Claude, ChatGPT or any coding agent.
Write a Frigate 0.18 config.yml for me. Hardware: [mini PC model / CPU], detector: [Intel GPU with OpenVINO / USB Coral / Hailo-8 / CPU]. Cameras:
- [name]: [brand/model], main stream [rtsp url with USER:PASS placeholders], substream [rtsp url]
- ...
Use the substream for detect and the main stream for record, track [person, car, dog, package], keep recordings for [N] days, and add hwaccel_args for my hardware. Explain every section in one line and flag anything you're unsure of instead of guessing an option name. Point me to the Frigate docs page for each option.
2. Find my camera's RTSP URL
You don't know the stream address.
I have a [brand] [model] camera, firmware [version], at IP [192.168.x.x]. What are the RTSP URLs for its main stream and substream, which port does it use, and where in its app or web page do I enable RTSP? If the format differs by firmware, give me each option and a VLC test for each. Tell me if this model has no local RTSP stream at all.
3. Write my 'what's normal here' prompt
Path 2 step 3.
Help me write a Frigate review activity_context_prompt with three sections: Normal Activity Indicators (Level 0), Suspicious Activity Indicators (Level 1) and Critical Threat Indicators (Level 2). About my home: [who lives here, pets, cars], regular visitors [cleaner, gardener, dog walker with days and times], which cameras see public areas like the sidewalk, and what I actually want to be woken up for: [list]. Keep each rule short and general enough that it won't misfire, and output valid YAML I can paste under review.genai.
4. Fix Frigate when it isn't working
Errors, high CPU or no detections.
My Frigate isn't working. Symptoms: [no detections / high CPU / 'Bus error' / camera offline / no AI summaries]. Here is my docker-compose.yml and config.yml with passwords removed: [paste]. And the last 50 lines of `docker logs frigate`: [paste]. Find the most likely cause, give me the exact change, and tell me how to confirm it worked. Check shm_size, detector and hwaccel settings, stream roles, the Ollama base_url (Frigate runs in Docker, so localhost won't reach another machine), and whether review.genai or objects.genai is actually enabled.
5. Build a Home Assistant automation from Frigate events
After path 3, in any AI chat or an agent connected to Home Assistant.
Write a Home Assistant automation in YAML that uses my Frigate integration. Camera: [front_door]. When a [person] is detected in zone [porch] between [10 PM and 6 AM], turn on [light.porch] for 5 minutes and send a notification to [mobile_app_my_phone] with the snapshot. Don't notify again for 10 minutes. Use only entities and triggers you can confirm exist in the Frigate integration; if you're unsure of an entity name, tell me how to look it up in Developer tools instead of guessing.
6. Audit my camera network
Any time, especially after adding a camera.
Here's my network layout: router [model], cameras [list with IPs], Frigate server [IP], Home Assistant [IP]. Give me a step-by-step plan to (1) put the cameras on their own VLAN or block their internet access, (2) check which of them still try to reach outside servers, (3) change default passwords and update firmware, and (4) make sure Frigate's ports 5000 and 8971 aren't reachable from the internet. Give me the exact commands to test each step from a laptop on my network.
7. Read a display or gauge with a camera
You want a camera to watch a boiler, meter or appliance.
I want to use a Frigate camera pointed at [my boiler display / a water meter / a gauge] to read its value or error code and alert me in Home Assistant. Compare these options and give me the setup for the best one: (a) a Frigate object prompt for that camera, (b) a Home Assistant automation that grabs a snapshot every [N] minutes and sends it to Ollama with a vision model, (c) a small script. Include the exact prompt to send to the model and what to do when it can't read the display.
Safety checklist
Never expose Frigate to the internet with a port forward. Port 5000 has no login at all; use Tailscale or another VPN for remote viewing.
Keep Frigate updated: 0.18.2 (October 2026) fixed security issues. Change every camera's default password and update its firmware.
AI summaries can be wrong. A threat level of 0 doesn't mean nothing happened; check the clip before you act on an alert, and never confront someone based on an AI description.
Recording laws vary. Audio recording, cameras that see neighbors' property and cameras in rentals or guest spaces are restricted in many places. Tell guests and tenants about cameras.
If you use a cloud AI provider instead of Ollama, frames of your home are sent to that company. Use a local model if that matters to you.
Use the substream for detection and keep an eye on disk space: recordings can fill a drive quickly.
A landlord pointed a Tapo camera at a rental's boiler, exports still frames and uses AI to read error codes on the screen, because the thermostats only alert once rooms are already cooling.
xinc3s says Claude Opus 5.5 built a 3D model of his home from one prompt in about 20 minutes and found two cameras that weren't his, both still sending data out. He notes a professional bug sweep for an average US home runs $1,500 to $6,000, per one firm's price page.
Model_Culture checked into a smart-home Airbnb (about EUR 120 a night) and says Claude Code found a hidden microphone in a smart plug and an unsecured doorbell camera broadcasting to the open internet, all in under two minutes.
A designer vibe coded Hearth over a weekend with help from Claude and Codex, using SwiftUI, Python and JavaScript. It sits in the Mac menu bar and connects to hundreds of Home Assistant integrations: energy use, cameras, speakers, lights, plugs, air conditioners and supported cars.
How do you set up local AI security cameras with Frigate, Ollama and Home Assistant (no cloud)?
Install Frigate (free, open source) with Docker on a small Linux box, add your cameras' RTSP streams, and let it detect people, cars and animals on the box itself. Then point Frigate at Ollama running a vision model such as qwen3-vl so it writes a plain-English summary of each event ("Person left a package at the front door") without any video leaving your home. Connect it to Home Assistant with the Frigate integration from HACS for alerts and automations. Typical cost: $0 for software, an Intel mini PC for detection, and a GPU or Apple silicon Mac if you want the AI summaries to be fast. Frigate+ ($50/yr) is optional.
Does Frigate need the cloud or a subscription?
No. Frigate runs entirely on your own hardware and is free and open source. Frigate+ is an optional $50/yr subscription for better detection models. AI summaries can run on Ollama locally, so video never leaves your network. The only outbound traffic you need is for updates, one-time model downloads and, if you turn them on, push notifications.
What hardware do I need for Frigate?
A Debian or Ubuntu machine with Docker. Frigate's docs say an Intel CPU's built-in graphics running the OpenVINO detector is enough for many homes, which makes an Intel N100-class mini PC a common choice. A Google Coral or Hailo-8 accelerator also works. Semantic search needs at least 8GB of RAM, and the AI summaries need a GPU or Apple silicon Mac running Ollama.
Which AI model should I use for camera summaries?
Frigate's docs recommend vision models such as qwen3-vl (for example qwen3-vl:4b), with gemma4 as an alternative. It must be a vision model. If you want one model to serve both Frigate and Home Assistant's assistant, qwen3-vl supports both vision and tool calling in Ollama.
Can AI tell me what actually happened, not just 'person detected'?
Yes. With review summaries on, Frigate sends frames from each event to your model and saves a title, a short summary for notifications, a scene description and a threat level from 0 to 2. You can tell it what is normal for your home (for example, dog walkers or a 7 AM cleaner) so it stops flagging routine activity.
Can I search my footage in plain English?
Yes. Turn on semantic search and you can search the Explore view for things like 'red car in the driveway' or 'person carrying a ladder'. It uses local Jina CLIP models, needs 8GB+ RAM, and older events must be reindexed once.
Is it legal to record with AI cameras?
It depends on where you live. Many places restrict recording audio, pointing cameras at neighbors' property or public areas, and recording guests or tenants without notice. Check your local rules, and keep cameras on your own property.
Do my existing Ring or Nest cameras work?
Only cameras that offer a local RTSP stream work directly. Many Reolink, Amcrest, Hikvision, Dahua, Tapo and Unifi cameras do. Ring and most Nest cameras don't provide a local stream.
Which AI tools do people use to set up local AI security cameras with Frigate, Ollama and Home Assistant (no cloud)?
Across the 5 sourced use cases in this guide, the most used tools are Claude Code, Claude, Figma, Home Assistant, OpenAI Codex.
How much does it cost to get started?
1 of the 5 use cases can start on a free plan. Prices come from each tool's official pricing page.
How long does setup take?
0 of the 5 use cases list a setup time of an hour or less. Each card shows the setup time the builder reported.
Are these real examples?
Yes. Every use case links to its public source (an X post, a Hacker News thread or a GitHub repo) with the author and date, so you can check it yourself.
The Daily 5
Liked this guide? Get five new use cases tomorrow morning
Five new real AI use cases every morning. Free. Unsubscribe any time.