Lots of goodies in this one!
Breaking changes
area
formotion_detection
is now a percentaged based value and needs to be changed from an int to a float.
This means that if you change yourwidth
and/orheight
,area
wont be affected.
Changes and new Features
-
Masks can now be configured under each cameras
motion_detection
block.
Masks are used to limit motion detection from running in a specified area.
The configuration is similar to how zones are configured, here is an example:Config example
cameras: - name: name host: ip port: port path: /Streaming/Channels/101/ motion_detection: area: 0.07 mask: - points: - x: 0 y: 0 - x: 250 y: 0 - x: 250 y: 250 - x: 0 y: 250 - points: - x: 500 y: 500 - x: 1000 y: 500 - x: 1000 y: 750 - x: 300 y: 750
The masks are drawn on the image published over MQTT. they have an orange border with a black background with 70% opacity.
-
A switch entity is now created in Home Assistant which can be used to arm/dsiarm a camera.
When disarmed, the decoder stops completly so no system load will be used. -
Motion contours are now drawn on the image that is being published over MQTT.
Dark purple contours are smaller than the configuredarea
, while bright pink contours are larger than the configuredarea
. -
New config option
max_timeout
undermotion_detection
which specifies the max number of seconds that motion alone is allowed to keep the recorder going.
This is used to prevent never-ending recordings when motion detection is too sensitive -
New config option
rtsp_transport
undercameras
. Change this if your camera doesnt support tcp. -
VA-API is now installed in the CUDA image for use with ffmpeg decoding/encoding
Fixes
- The binary sensor for motion detection is now properly set to on/off.
Docker images are available on Docker Hub
roflcoopter/viseron:latest
roflcoopter/viseron-cuda:latest
roflcoopter/viseron-vaapi:latest
roflcoopter/viseron-rpi:latest