Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation.

Screenshots From the README of blakeblackshear/frigate-hass-integration.

Screenshot from blakeblackshear/frigate-hass-integration

About

Frigate is an integration that connects Home Assistant to a Frigate camera system and works locally. It adds binary sensors, cameras, images, numbers, selects, sensors, switches and update entities, including live view, object snapshots, and switches for recording, detection and snapshots. A media browser with thumbnails and navigation lets recorded clips be browsed, and services cover manual events and PTZ control. Several Frigate instances can be used side by side. Authentication can use Frigate's own login, HTTP Basic Auth or a static Bearer token, which suits setups behind a reverse proxy. Options cover native WebRTC, an RTSP URL template and a notification event proxy with an optional access timeout, and the MQTT integration is also required.

Automatic summary of the README and code of blakeblackshear/frigate-hass-integration. Something wrong, or are you the maintainer and want your own text here? Get in touch

Supports

  • Works locally Talks to your devices on your own network. No vendor cloud in between.

  • From the Marketplace Installed through the Marketplace, formerly HACS.

  • Actively maintained Its author released or pushed a change in the last six months.

Provides

  • Cameras
  • Switches
  • Sensors

Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

Connect

  • URL
  • Validate SSL
  • Username (optional)
  • Password (optional)
  • Authentication mode'Frigate login' uses Frigate's native username/password login. 'HTTP Basic Auth' sends the username/password as a Basic Authorization header on every request (for reverse proxies enforcing Basic Auth in front of Frigate). 'Bearer token' sends the password as a static Bearer Authorization header on every request (username is ignored); use this for reverse proxies that expect a static token.

After setup

  • Use Frigate-native WebRTC support
  • RTSP URL template (see documentation)
  • Enable the media browser
  • Enable the unauthenticated notification event proxy
  • Disallow unauthenticated notification access after seconds (0=never)

Texts from the code of blakeblackshear/frigate-hass-integration.

Troubleshooting

  • DiagnosticsDownloads a diagnostics file to attach to a bug report.

Shows in Vulpo

Quick Toggle card, Camera card, Select card, Chart card, Apple Watch, Control Center.

Information

Installs
29.3k sharing analytics
GitHub stars
1.3k
Connection
Works locally
Upkeep
Updated in the last 6 months
Version
v5.15.6,
Category
Security and safety, Cameras
Kind
Marketplace integration
Brand
Frigate
Needs
Needs the Marketplace (HACS on 2026.10 and older)
Domain
frigate

More from Frigate

You might also like

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. About these numbers