Cameras and Doorbells

Frigate and Home Assistant: Integration Setup and Notifications

Set up the Frigate NVR with Home Assistant over MQTT, then configure object detection, notifications with snapshots and clips, and fewer false alerts.

On this page
  1. What Frigate adds to Home Assistant
  2. What you need before you start
  3. Step 1: Configure cameras in Frigate
  4. Step 2: Set up MQTT
  5. Step 3: Install the Frigate integration
  6. What you get in Home Assistant
  7. Ports to know
  8. Notifications with Frigate
  9. Troubleshooting
  10. Versions and features
  11. Common misconceptions
  12. Related guides

What Frigate adds to Home Assistant

Frigate is an open-source network video recorder (NVR) that uses object detection to find people, cars, animals, and other objects in camera footage. It runs as a Docker container or as a Home Assistant OS add-on. Frigate is a separate server, not part of Home Assistant itself. Home Assistant connects to it through a Frigate integration, which you install from HACS, and the two communicate over MQTT, a messaging protocol that many smart home devices use.

What you need before you start

  • A Frigate install, either as the Home Assistant OS add-on or in Docker. The add-on lives in the frigate-hass-addons repository. The “Full Access” variant is for hardware acceleration.
  • An MQTT broker, such as the Mosquitto add-on, that both Frigate and Home Assistant can reach
  • HACS installed in Home Assistant, so you can add the Frigate integration
  • One or more cameras with working RTSP streams. The Home Assistant cameras guide covers address formats.

Step 1: Configure cameras in Frigate

Frigate reads each camera’s streams from its YAML configuration. Each camera lists one or more ffmpeg inputs, and each input has roles. Use the substream for detect and the main stream for record:

mqtt:
  host: core-mosquitto

cameras:
  front_door:
    ffmpeg:
      inputs:
        - path: rtsp://user:password@192.168.1.50:554/h264Preview_01_sub
          roles:
            - detect
        - path: rtsp://user:password@192.168.1.50:554/h264Preview_01_main
          roles:
            - record

The host value depends on your broker. core-mosquitto is the usual name for the Mosquitto add-on, but a broker running elsewhere needs its own address. The RTSP paths above are Reolink examples. Use the path for your own camera.

Detect on the substream, record from the main stream

Running detection on a high-resolution stream wastes CPU. A detect stream around 640×480 to 1280×720, run at about 5 frames per second, is a common starting point. Recording uses the main stream, so you keep full quality for review.

Detector hardware

Detection speed depends on the detector hardware. Options include:

  • Google Coral, which has low inference times
  • OpenVINO on Intel integrated graphics
  • Hailo-8L accelerators
  • Nvidia GPUs

A CPU detector is generally not recommended. A Coral isn’t required, because OpenVINO and Hailo also work well.

Step 2: Set up MQTT

Frigate publishes its events over MQTT, and the Frigate integration depends on it. Install an MQTT broker such as the Mosquitto add-on, enable mqtt in Frigate’s configuration with the broker’s address, and point Home Assistant’s MQTT integration at the same broker. If the integration shows no events, confirm that messages are arriving on frigate/events in an MQTT client.

Step 3: Install the Frigate integration

  1. In HACS, search for the Frigate integration (frigate-hass-integration) and install it. Restart Home Assistant when prompted.
  2. Go to Settings > Devices & services > Add integration and search for Frigate.
  3. Enter your Frigate server URL. If you use a variant such as Full Access, adjust the hostname and port to match your setup.

What you get in Home Assistant

  • Cameras and media: live camera entities, object snapshots, and a Media browser with thumbnails and recorded clips
  • Sensors: motion and object binary sensors per zone, object counts, and FPS performance sensors
  • Switches: recording, detection, snapshots, and contrast improvements
  • Services: PTZ control on supported cameras and manual events

Ports to know

  • 8971: the authenticated web UI, in version 0.14 and later
  • 5000: an unauthenticated API. Keep it inside your LAN.
  • 8554 and 8555: the RTSP restream and the WebRTC port

Notifications with Frigate

Frigate’s documentation recommends triggering notifications from MQTT topics. Frigate publishes two of them:

  • frigate/reviews (version 0.14 and later) is the recommended trigger. Review messages include the event IDs you need to fetch thumbnails, snapshots, and clips.
  • frigate/events reports each tracked object’s new, updated, and ended states. Its change feed shows the “before” and “after” state of an object, so a notification can update as Frigate finds a better frame.

Notification images come from Frigate’s API:

  • /api/frigate/notifications/<event_id>/thumbnail.jpg
  • /api/frigate/notifications/<event_id>/snapshot.jpg
  • /api/frigate/notifications/<event_id>/clip.mp4

Your phone needs a way to reach these addresses. When you’re away from home, that usually means a secure remote access setup. Don’t open Frigate’s unauthenticated API to the internet to make it work.

Start from a blueprint

Starting from a blueprint is easier than writing automations from scratch. The community “Frigate Notifications” blueprint by SgtBatten handles zones, cooldowns, and actionable alerts. Generate the automation from the blueprint, then customize it.

Cut false alerts

Most noise comes from detections that pass a low threshold and then fail a higher one. These settings help tighten alerts:

  • Zones and required_zones limit alerts to areas you care about.
  • min_score (default 0.5) is the lowest score that can fire an event. threshold (default 0.7) is the score a detection needs to be confirmed. An event can fire at min_score and then fail the threshold. Raising min_score closer to threshold reduces noise.
  • Masks block areas such as a busy road or swaying trees.

Troubleshooting

  • No events in Home Assistant: Check that Frigate and Home Assistant use the same MQTT broker and that mqtt is enabled in Frigate.
  • Missing clips: Detections that never reach the confirmation threshold may not produce a full clip. Revisit min_score and threshold.
  • Blank screen from an iOS action button: One reported fix is to turn off Remember Last Page in the Companion app’s general settings.

Versions and features

Features change between Frigate releases. Face recognition and license plate recognition arrived in version 0.16, so check the release notes for the version you run before you plan around a feature.

Common misconceptions

  • “Frigate is built into Home Assistant.” It’s a separate server plus a HACS integration.
  • “You need a Coral.” OpenVINO and Hailo also work well.
  • “Detect on the 4K stream for better results.” High-resolution detection wastes CPU.
  • “You don’t need MQTT.” The integration depends on it.

The complete guide to cameras and doorbells

Home Assistant Cameras: Adding RTSP Streams and Choosing Cameras
Read the guide

Keep exploring

Guides from other topics

All topics →