One of the cameras won't "detect" anyone

[gniknalu]

Can you spot anything I've done wrong? This camera won't detect anything but it WILL, via MQTT, work as a "camera" in home assistant. It clearly displays the zone outline and you see a fuzzy purple outline around people when they walk outside. But it won't "detect" "person"

Here is the config:

  - name: "BackEast"
    host: !secret xxxxxxxxxx
    port: !secret xxxxxxxxxx
    stream_format: rtsp
    username: !secret xxxxxxxxxx
    password: !secret xxxxxxxxxx
    path: /xxx/xxxx&xxx&proto=Onvifxxx
    mqtt_name: camera_back_east
    publish_image: true
    motion_detection:
      interval: .5
      trigger_detector: true
      timeout: true
      max_timeout: 300
    object_detection:
      interval: .5
    zones:
      - name: BackYard
        points:
          - x: 329
            y: 141
          - x: 898
            y: 16
          - x: 1915
            y: 181
          - x: 1915
            y: 1069
          - x: 421
            y: 1074

And here is some of what I see in the log when I start viseron:

[2021-05-28 18:45:54] [INFO    ] [viseron                 ] - Initializing NVR threads
[2021-05-28 18:45:54] [DEBUG   ] [viseron.nvr.backeast    ] - Initializing NVR thread
[2021-05-28 18:45:54] [DEBUG   ] [viseron.camera.backeast ] - Initializing camera BackEast

[2021-05-28 18:46:00] [DEBUG   ] [viseron.camera.stream.backeast] - Stream information from FFprobe: Width: 1920 Height: 1080 FPS: 25.0 Video Codec: h264 Audio Codec: pcm_alaw
[2021-05-28 18:46:00] [DEBUG   ] [viseron.camera.backeast ] - Resolution: 1920x1080 @ 25.0 FPS
[2021-05-28 18:46:00] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic backeast/frame/decode/object, <queue.Queue object at 0x7f0fc4138550>
[2021-05-28 18:46:00] [DEBUG   ] [viseron.camera.backeast ] - Starting decoder thread
[2021-05-28 18:46:00] [DEBUG   ] [viseron.camera.backeast ] - Running decoder backeast.object_detection at 0.5s interval, every 12.5 frame(s)
[2021-05-28 18:46:00] [DEBUG   ] [viseron.camera.backeast ] - Camera BackEast initialized
[2021-05-28 18:46:00] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic backeast/frame/processed/object, <queue.Queue object at 0x7f0fc41295b0>
[2021-05-28 18:46:00] [DEBUG   ] [viseron.motion.backeast ] - Initializing motion detector
[2021-05-28 18:46:00] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic backeast/frame/decode/motion, <queue.Queue object at 0x7f102cae0af0>
[2021-05-28 18:46:00] [DEBUG   ] [viseron.motion.backeast ] - Starting decoder thread
[2021-05-28 18:46:00] [DEBUG   ] [viseron.motion.backeast ] - Running decoder backeast.motion_detection at 0.5s interval, every 12.5 frame(s)
[2021-05-28 18:46:00] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic backeast/frame/scan/motion, <queue.Queue object at 0x7f102cae06a0>
[2021-05-28 18:46:00] [DEBUG   ] [viseron.motion.backeast ] - Motion detector initialized
[2021-05-28 18:46:00] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic backeast/frame/processed/motion, <queue.Queue object at 0x7f102cae0430>
[2021-05-28 18:46:00] [DEBUG   ] [viseron.nvr.backeast    ] - Starting camera
[2021-05-28 18:46:00] [DEBUG   ] [viseron.camera.backeast ] - Starting capture thread
[2021-05-28 18:46:00] [DEBUG   ] [viseron.camera.stream.backeast] - FFMPEG decoder command: backeast -hide_banner -loglevel error -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts -use_wallclock_as_timestamps 1 -vsync 0 -stimeout 5000000 -c:v h264_cuvid -rtsp_transport tcp -i rtsp://*****:*****@xxx.xxx.xxx.xxx:xxx/xxx/xxxx&xxx&proto=Onvifxxx -f segment -segment_time 5 -reset_timestamps 1 -strftime 1 -c:v copy -c:a copy /segments/BackEast/%Y%m%d%H%M%S.mkv -filter:v fps=2 -f rawvideo -pix_fmt nv12 pipe:1
[2021-05-28 18:46:00] [DEBUG   ] [viseron.recorder.backeast] - Initializing ffmpeg recorder
[2021-05-28 18:46:00] [DEBUG   ] [viseron.nvr.backeast    ] - Waiting for first frame
[2021-05-28 18:46:00] [DEBUG   ] [viseron.nvr.backeast    ] - NVR thread initialized

No folder is created, like what I see with the other cameras. I've had multiple people walk out and it doesn't do anything with them. (There's no other mention of the camera in the logs.)

When you look at nvidia-smi, it shows the camera name "backeast" (nice update - showing the camera instead of ffmpeg). Plenty of CPU/GPU available and plenty of RAM on the GPU and on the host.

Thank you!

[roflcoopter]

Object detection will only run when motion is detected due to the config option trigger_detector
And if you say that you get purple squiqqly purple lines when you walk infront, that means that your motion detector is too insensitive.
This is from the documentation:

Images will be published with drawn objects, motion contours, zones and masks if publish_image: true is set in the config.
Objects that are discarded by a filter will have blue bounding boxes, while objects who pass the filter will be green.
Zones are drawn in red. If an object passes its filter and is inside the zone, the zone will turn green.
Motion contours that are smaller than configured area are drawn in dark purple, while bigger contours are drawn in pink.
Masks are drawn with an orange border and black background with 70% opacity.

So you most likely need to tweak the motion detection settings a bit so it becomes more sensitive.
A good tip is to start with it being very sensitive and then tweak it from there.

I am planning to make it easier to configure this by being able to benchmark different settings with eachother but i havent come to a good solution there yhet

[gniknalu]

THANK YOU!