Frigate notifications in Home Assistant: snapshots & clips on your phone
A camera system that records everything but tells you nothing is just an archive. This guide wires Frigate's detections into Home Assistant so the events that matter reach your phone in seconds — with a snapshot you can judge at a glance, a tap-through to the clip, action buttons, and the filters, cooldowns and quiet hours that keep it from becoming noise you learn to ignore.
Published Nov 18, 2026 · Last updated Nov 18, 2026
How the pipeline works
Three pieces, each doing one job. Frigate detects an object and publishes a message to the MQTT topic frigate/events — the message carries the camera, label (person, car, dog…), score, zones entered, and a unique event ID. Home Assistant — with the Frigate integration installed and MQTT connected — listens on that topic. An automation decides whether this event deserves your attention and, if so, sends a push through the Home Assistant companion app with the event's snapshot attached.
The snapshot and clip come from the Frigate integration's built-in proxy, using the event ID from the payload:
- Snapshot:
/api/frigate/notifications/<event-id>/snapshot.jpg - Clip:
/api/frigate/notifications/<event-id>/clip.mp4
Because those URLs are served by Home Assistant itself, they work through your normal remote access (or locally) with your existing login — no Frigate port exposed, no separate credentials in the notification.
Before you start: MQTT must be running and Frigate must be publishing to it. That is the same broker setup from our Frigate + Home Assistant guide. If frigate/events is silent when you walk in front of a camera (check with MQTT Explorer or HA's MQTT listen tool), fix that first — no automation can notify about events it never hears.
Blueprint or hand-rolled?
There is a very popular community blueprint for exactly this (search the Home Assistant blueprint exchange for "Frigate notifications") and it is genuinely good: camera and zone pickers, cooldown, action buttons, iOS/Android handling. If you want alerts today, import it, fill in your cameras, done.
Build your own automation when you outgrow it — per-camera quiet hours, different rules for the doorbell than the backyard, a "only when nobody is home" condition tied to your presence setup, or just wanting to see the logic. The hand-rolled version below is deliberately plain: it is the blueprint's core ideas with nothing hidden, and it is the one the rest of this guide tunes.
The complete automation
This notifies for a person or car entering the driveway zone of the driveway camera, above a 0.75 score, at most once every three minutes:
alias: Frigate — driveway person alert
description: Snapshot notification with clip button, zone + score filtered, 3-minute cooldown
triggers:
- trigger: mqtt
topic: frigate/events
conditions:
# Only the first message for an event, not the update/end stream
- condition: template
value_template: "{{ trigger.payload_json.type == 'new' }}"
- condition: template
value_template: "{{ trigger.payload_json.after.camera == 'driveway' }}"
- condition: template
value_template: "{{ trigger.payload_json.after.label in ['person', 'car'] }}"
- condition: template
value_template: "{{ 'driveway' in trigger.payload_json.after.current_zones }}"
- condition: template
value_template: "{{ trigger.payload_json.after.top_score > 0.75 }}"
# Cooldown: at most one alert from this automation every 3 minutes
- condition: template
value_template: >
{{ this.attributes.last_triggered is none or
(now() - this.attributes.last_triggered).total_seconds() > 180 }}
actions:
- variables:
event_id: "{{ trigger.payload_json.after.id }}"
label: "{{ trigger.payload_json.after.label }}"
- action: notify.mobile_app_your_phone
data:
title: "{{ label | title }} in the driveway"
message: "Frigate spotted a {{ label }} — tap to watch the clip."
data:
image: "/api/frigate/notifications/{{ event_id }}/snapshot.jpg"
clickAction: "/api/frigate/notifications/{{ event_id }}/clip.mp4"
actions:
- action: "OPEN_CLIP"
title: "Open clip"
uri: "/api/frigate/notifications/{{ event_id }}/clip.mp4"
- action: "VIEW_LIVE"
title: "Live view"
uri: "/lovelace/cameras"
mode: parallel
max: 10
Things worth understanding in that YAML, because you will tune all of them:
type == 'new'— Frigate sends new, update and end messages for one event. Filtering to new means one trigger per event and the fastest possible alert. The trade-off: the snapshot at new is the first frame, not the best frame. If your snapshots look like empty driveways, switch the filter to'end'and usetop_score— you trade a few seconds of delay for the highest-scoring image of the event.- Zones do the heavy lifting.
current_zonesmeans "in the zone right now," which is what you want for a driveway apron. Requiring a zone at all eliminates most junk — detections on the public street never enter it. If your zones are sloppy, fix them before touching scores; our zones & masks guide is the prerequisite reading. - Score is a floor, not a target. 0.75 for people is a sane start. Raise it and you will miss the person in a hoodie at dusk; lower it and the mailbox becomes a person twice a week. Tune per camera, in daylight and at night, over a week — not from one afternoon.
- The cooldown is per-automation. Duplicate this automation per camera (or per camera group) so the backyard's cooldown never silences the front door.
Action buttons that do something
The notification above carries two buttons. A button with a uri simply opens that link when tapped — the clip, a live-view dashboard — and needs no further plumbing. A button without a uri fires a mobile_app_notification_action event back to Home Assistant, which a second automation can act on: snooze this camera for an hour (via a helper your alert automation checks), unlock nothing, ever — be careful what you wire to a lock screen — but things like "turn on the porch light" or "mark as known visitor" are fair game.
alias: Frigate — notification button handler
triggers:
- trigger: event
event_type: mobile_app_notification_action
event_data:
action: OPEN_CLIP
actions:
# The companion app already opens the clip via the action's uri;
# use this pattern when a button should DO something instead —
# e.g. swap OPEN_CLIP for SNOOZE and add an input_boolean helper
# your alert automation checks before notifying.
- action: persistent_notification.create
data:
title: Frigate
message: "Button pressed: {{ trigger.event.data.action }}"
mode: single
Quiet hours and not waking the house
Add a time or state condition to the alert automation rather than building a second one: a simple condition: time with after: "07:00:00" / before: "22:30:00" covers most households, and an input_boolean "guest mode" or your alarm panel's armed-home state covers the rest. The pattern that works long-term: front door and doorbell notify 24/7, perimeter cameras notify when the house is asleep or empty, everything else records silently. Which brings up 0.18's distinction —
Alerts vs review in Frigate 0.18
Frigate 0.18 separates alerts (the events you'd act on now) from review items (worth a glance later). Mirror that split in Home Assistant: push notifications only for alert-class events — a person in a defined zone, the doorbell camera, a car in the driveway overnight. Let everything else land in Frigate's review queue for the morning scroll. If every detection pushes, you will mute the channel within a month, and a muted channel is worse than none. Sizing the system so events are worth alerting on is also a config question — our Frigate config planner checks your 0.18 config and storage math, and the camera planner helps place cameras so zones cover approaches instead of streets.
Troubleshooting
- No notifications at all: confirm the event topic fires (MQTT listen on
frigate/#), the automation's traces show it triggering, and the notify service name matches your phone's actual device name in the companion app —notify.mobile_app_…names are per-device and easy to mistype. - Notification arrives, image doesn't: open the snapshot URL in a browser while logged into HA. A 404 means the event ID or integration proxy is wrong; a slow load means you are racing the new event — add a 3–5 second delay action or notify on end.
- Three notifications per event: your type filter is missing or set to include updates. One event, three message types — filter to exactly one.
- Alerts at 3 a.m. from headlights: that is a zone/mask problem (light sweep crossing your zone), not a notification problem. Mask the street, shrink the zone to the apron.
Cameras that feed this well
Notifications are only as good as the detection stream: a camera with a clean sub-stream for detection and reliable local recording makes the whole pipeline calmer. These are the ones our Frigate guides build on:
Prices are editorial and change often; buttons show live prices. Some links may earn a commission at no cost to you — see the disclosure page.
Official documentation and references
- Frigate documentation — Home Assistant integration (MQTT events, notification proxy URLs)
- Frigate documentation — notifications configuration
- Home Assistant companion apps — basic notifications (attachments, images)
- Home Assistant companion apps — actionable notifications
- Frigate integration for Home Assistant — GitHub (blakeblackshear/frigate-hass-integration)
Frequently asked questions
Do I need MQTT for Frigate notifications in Home Assistant?
Yes, for the approach in this guide. Frigate publishes every detection to the frigate/events MQTT topic, and the automation listens there. MQTT is optional for Frigate recording on its own, but it is required for the Home Assistant integration — and it is what makes notifications fast, because HA reacts the moment an event starts instead of polling.
Blueprint or hand-rolled automation — which should I use?
Start with the popular community blueprint if you want it working in ten minutes; it covers cameras, zones, cooldowns and action buttons well. Switch to (or copy) a hand-rolled automation when you want per-camera rules the blueprint does not expose, different quiet hours per person, or to understand exactly why a notification fired. Both use the same MQTT events and the same snapshot URL pattern.
Why do my notification snapshots arrive broken or blank?
Almost always the URL or timing. The image path must be /api/frigate/notifications/
How do I stop Frigate notifications from spamming me?
Layer the filters: zones and a minimum score first (most spam is bad detections, not bad notifications), then a per-camera cooldown of 2–5 minutes, then quiet hours for overnight. Also separate alerts from review items the way Frigate 0.18 does — only true alerts should ever push to your phone.
Can I get Frigate notifications without the Home Assistant app?
Yes — the same frigate/events MQTT topic can drive other notifiers (ntfy, Pushover, Telegram bots, or Frigate's own GenAI/notification features), but the companion app is the path with the least moving parts if you already run Home Assistant, and it is the one that gives you tap-to-clip and action buttons for free.

