mirror of
https://github.com/blakeblackshear/frigate.git
synced 2024-11-26 19:00:23 -06:00
NVR with realtime local object detection for IP cameras
aicameragoogle-coralhome-assistanthome-automationhomeautomationmqttnvrobject-detectionrealtimertsptensorflow
6e53c109b6
When serving Frigate at a subpath, the paths that show in the URL bar and that wind up in your browser history are anchored at the web root. I.e. you go to `https://example.com/frigate/`, it changes to `https://example.com/`, and clicking around works as expected, but the `frigate/` prefix is gone. It's confusing if you don't know that the URL's are entirely virtual. Also, your browser history is useless, since the URL's point to e.g. `https://example.com/#kitchen`, but visiting that URL will not hit `/frigate/` at all. Most of the work is already done. Nginx injects javascript to set `window.baseURL` based on the X-Ingress-Path header. This change passes that to BrowserRouter, so that it'll be part of the URL's it shows. Fixes #4526 |
||
|---|---|---|
| .cspell | ||
| .devcontainer | ||
| .github | ||
| .vscode | ||
| config | ||
| docker | ||
| docs | ||
| frigate | ||
| migrations | ||
| web | ||
| .dockerignore | ||
| .gitignore | ||
| .pylintrc | ||
| audio-labelmap.txt | ||
| benchmark_motion.py | ||
| benchmark.py | ||
| CODEOWNERS | ||
| cspell.json | ||
| docker-compose.yml | ||
| labelmap.txt | ||
| LICENSE | ||
| Makefile | ||
| netlify.toml | ||
| process_clip.py | ||
| pyproject.toml | ||
| README.md | ||
Frigate - NVR With Realtime Object Detection for IP Cameras
A complete and local NVR designed for Home Assistant with AI object detection. Uses OpenCV and Tensorflow to perform realtime object detection locally for IP cameras.
Use of a Google Coral Accelerator is optional, but highly recommended. The Coral will outperform even the best CPUs and can process 100+ FPS with very little overhead.
- Tight integration with Home Assistant via a custom component
- Designed to minimize resource use and maximize performance by only looking for objects when and where it is necessary
- Leverages multiprocessing heavily with an emphasis on realtime over processing every frame
- Uses a very low overhead motion detection to determine where to run object detection
- Object detection with TensorFlow runs in separate processes for maximum FPS
- Communicates over MQTT for easy integration into other systems
- Records video with retention settings based on detected objects
- 24/7 recording
- Re-streaming via RTSP to reduce the number of connections to your camera
- WebRTC & MSE support for low-latency live view
Documentation
View the documentation at https://docs.frigate.video
Donations
If you would like to make a donation to support development, please use Github Sponsors.
Screenshots
Integration into Home Assistant
Also comes with a builtin UI:
