1.4.0 - Zones!
Changes and new Features
-
Zones are here! You can now configure zones for each camera and specify labels to track per zone.
Here is an example:cameras: - name: name host: ip port: port path: /Streaming/Channels/101/ zones: - name: zone1 points: - x: 0 y: 500 - x: 1920 y: 500 - x: 1920 y: 1080 - x: 0 y: 1080 labels: - label: person confidence: 0.9 - name: zone2 points: - x: 0 y: 0 - x: 500 y: 0 - x: 500 y: 500 - x: 0 y: 500 labels: - label: cat confidence: 0.5
A polygon will be drawn on the image using each point. Atleast 3 points have to be supplied.
If you are using Home Assistant, Viseron will publish an image to the camera entity over MQTT
with zones and objects drawn upon it.
The drawing and publishing takes some processing power so it should only be used for debugging and tuning. -
A boatload of new binary sensors are now created, tracking objects and zones. Checkout the README for a detailed explanation.
-
Allows a
logging
block to be entered per camera. -
Logging from motion detection is now named per camera.
-
The logger for the recorder is now named per camera.
-
You can now set log level individually for motion_detection and object_detection, either globally or for each camera.
-
New config option
publish_image
.
If enabled, Viseron will publish an image to the MQTT camera entity with objects and zones drawn upon it. -
You can now specify
width
,height
andfps
individually in the camera config. -
New config option
triggers_recording
for labels, if set to false, only the binary sensors in mqtt will update but no recording will start. This works on all labels configs (global object detector, per camera or per zone) -
Recorded videos will now be saved under a specific folder per camera.
Fixes
- TFLite is now properly installed in the generic, vaapi and cuda image for EdgeTPU support.
- Fixed motion detection not respecting
timeout
.
Docker images are available on Docker Hub
roflcoopter/viseron
roflcoopter/viseron-cuda
roflcoopter/viseron-vaapi
roflcoopter/viseron-rpi