forked from Github/frigate
Merge remote-tracking branch 'origin/master' into dev
This commit is contained in:
@@ -6,7 +6,8 @@ title: Configuring go2rtc
|
||||
Use of the bundled go2rtc is optional. You can still configure FFmpeg to connect directly to your cameras. However, adding go2rtc to your configuration is required for the following features:
|
||||
|
||||
- WebRTC or MSE for live viewing with higher resolutions and frame rates than the jsmpeg stream which is limited to the detect stream
|
||||
- RTSP (instead of RTMP) relay for use with Home Assistant or other consumers to reduce the number of connections to your camera streams
|
||||
- Live stream support for cameras in Home Assistant Integration
|
||||
- RTSP (instead of RTMP) relay for use with other consumers to reduce the number of connections to your camera streams
|
||||
|
||||
# Setup a go2rtc stream
|
||||
|
||||
|
||||
@@ -21,3 +21,5 @@ For object filters in your configuration, any single detection below `min_score`
|
||||
| 6 | 0.95 | 0.7, 0.85, 0.95, 0.90, 0.88, 0.95 | 0.89 | Yes |
|
||||
|
||||
In frame 2, the score is below the `min_score` value, so Frigate ignores it and it becomes a 0.0. The computed score is the median of the score history (padding to at least 3 values), and only when that computed score crosses the `threshold` is the object marked as a true positive. That happens in frame 4 in the example.
|
||||
|
||||
If you're seeing false positives from stationary objects, please see Object Masks here: https://docs.frigate.video/configuration/masks/
|
||||
|
||||
45
docs/docs/guides/ha_network_storage.md
Normal file
45
docs/docs/guides/ha_network_storage.md
Normal file
@@ -0,0 +1,45 @@
|
||||
---
|
||||
id: ha_network_storage
|
||||
title: HA Network Storage
|
||||
---
|
||||
|
||||
As of HomeAsisstant Core 2023.6, Network Mounted Storage is supported for addons.
|
||||
|
||||
## Setting Up Remote Storage For Frigate
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- HA Core 2023.6 or newer is installed
|
||||
- Running HA OS 10.2 or newer OR Running Supervised with latest os-agent installed (this is required for superivsed install)
|
||||
|
||||
### Initial Setup
|
||||
|
||||
1. Stop the Frigate addon
|
||||
2. Update your [config](configuration/index.md) so the DB is stored in the /config directory by adding:
|
||||
```yaml
|
||||
database:
|
||||
path: /config/frigate.db
|
||||
```
|
||||
|
||||
### Move current data
|
||||
|
||||
Keeping the current data is optional, but the data will need to be moved regardless so the share can be created successfully.
|
||||
|
||||
#### If you want to keep the current data
|
||||
|
||||
1. Move the frigate.db, frigate.db-shm, frigate.db-wal files to the /config directory
|
||||
2. Rename the /media/frigate folder to /media/frigate_tmp
|
||||
|
||||
#### If you don't want to keep the current data
|
||||
|
||||
1. Delete the /media/frigate folder and all of its contents
|
||||
|
||||
### Create the media share
|
||||
|
||||
1. Go to **Settings -> System -> Storage -> Add Network Storage**
|
||||
2. Name the share `frigate` (this is required)
|
||||
3. Choose type `media`
|
||||
4. Fill out the additional required info for your particular NAS
|
||||
5. Connect
|
||||
6. Move files from `/media/frigate_tmp` to `/media/frigate` if they were kept in previous step
|
||||
7. Start the Frigate addon
|
||||
Reference in New Issue
Block a user