Josh HawkinsandNicolas Mowen
88fc0fac8f
* Basic functionality * Threaded motion estimator * Revert "Threaded motion estimator" This reverts commit 3171801607cbbbe58cda7b637f2a3917d919959a. * Don't detect motion when ptz is moving * fix motion logic * fix mypy error * Add threaded queue for movement for slower ptzs * Move queues per camera * Move autotracker start to app.py * iou value for tracked object * mqtt callback * tracked object should be initially motionless * only draw thicker box if autotracking is enabled * Init if enabled when initially disabled in config * Fix init * Thread names * Always use motion estimator * docs * clarify fov support * remove size ratio * use mp event instead of value for ptz status * update autotrack at half fps * fix merge conflict * fix event type for mypy * clean up * Clean up * remove unused code * merge conflict fix * docs: update link to object_detectors page * Update docs/docs/configuration/autotracking.md Co-authored-by: Nicolas Mowen <nickmowen213@gmail.com> * clarify wording * pass actual instances directly * default return preset * fix type * Error message when onvif init fails * disable autotracking if onvif init fails * disable autotracking if onvif init fails * ptz module * verify required_zones in config * update util after dev merge --------- Co-authored-by: Nicolas Mowen <nickmowen213@gmail.com>
2.4 KiB
id, title
| id | title |
|---|---|
| cameras | Cameras |
Setting Up Camera Inputs
Several inputs can be configured for each camera and the role of each input can be mixed and matched based on your needs. This allows you to use a lower resolution stream for object detection, but create recordings from a higher resolution stream, or vice versa.
A camera is enabled by default but can be temporarily disabled by using enabled: False. Existing events and recordings can still be accessed. Live streams, recording and detecting are not working. Camera specific configurations will be used.
Each role can only be assigned to one input per camera. The options for roles are as follows:
| Role | Description |
|---|---|
detect |
Main feed for object detection |
record |
Saves segments of the video feed based on configuration settings. docs |
rtmp |
Deprecated: Broadcast as an RTMP feed for other services to consume. docs |
mqtt:
host: mqtt.server.com
cameras:
back:
enabled: True
ffmpeg:
inputs:
- path: rtsp://viewer:{FRIGATE_RTSP_PASSWORD}@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2
roles:
- detect
- rtmp # <- deprecated, recommend using restream instead
- path: rtsp://viewer:{FRIGATE_RTSP_PASSWORD}@10.0.10.10:554/live
roles:
- record
detect:
width: 1280
height: 720
Additional cameras are simply added to the config under the cameras entry.
mqtt: ...
cameras:
back: ...
front: ...
side: ...
For camera model specific settings check the camera specific infos.
Setting up camera PTZ controls
Add onvif config to camera
cameras:
back:
ffmpeg:
...
onvif:
host: 10.0.10.10
port: 8000
user: admin
password: password
then PTZ controls will be available in the cameras WebUI.
An ONVIF-capable camera that supports relative movement within the field of view (FOV) can also be configured to automatically track moving objects and keep them in the center of the frame. For autotracking setup, see the autotracking docs.