Can't get motion detection to work #215

anna-oake · 2021-06-14T15:50:50Z

anna-oake
Jun 14, 2021

I've tried setting up a dev branch container on my Nuc after #210 was implemented.
It's my first experience of using viseron.

Here is my simple config:

cameras:
  - name: Front door
    mqtt_name: front_door
    host: [redacted]
    port: 554
    path: /?user=admin&password=[redacted]&channel=0&stream=1.sdp
    audio_codec: aac
    publish_image: true
    motion_detection:
      interval: 1
      trigger_recorder: true
      trigger_detector: false
      threshold: 5
      alpha: 1
    object_detection:
      enable: false
logging:
  level: debug

mqtt:
  [redacted]

According to logs, ffmpeg gets started correctly.

I've also mounted /segments as a volume to check if segments appear, and they do! I can open these mp4 and see some parts of video stream.

The problem is that it never detects any motion.
I've tried PTZing my camera in all directions, which should obviously trigger the detection, but it didn't.

Also:

When I try dynamic mjpeg stream, I get 404. When I try static mjpeg stream, I get infinite loading (server responds with 200 and no body).
I've turned on publish_image and got a camera entity in my Home Assistant, but there is no image.

P.S. As you can see, it's configured for very sensitive detection. I did this just for test.

gniknalu · 2021-06-14T16:47:04Z

gniknalu
Jun 14, 2021

I suggest starting out with this portion of your config. See if you get video. Then build from there.

cameras:
  - name: Front door
    mqtt_name: front_door
    host: [redacted]
    port: 554
    path: /?user=admin&password=[redacted]&channel=0&stream=1.sdp

5 replies

anna-oake Jun 14, 2021
Author

I can see video segments in /segments with my config and the log says it grabs frames correctly.

gniknalu Jun 14, 2021

I can see video segments in /segments with my config and the log says it grabs frames correctly.

Excellent.

Then for the dynamic or static mjpeg stream, what docker command are you using to start viseron?

anna-oake Jun 14, 2021
Author

I deploy it as a compose stack and the 8888 port is exposed.

I'm trying to access the dynamic stream with this url: http://[redacted]:8888/front_door/stream

All I get is 404:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/tornado/web.py", line 1681, in _execute
    result = self.prepare()
  File "/usr/local/lib/python3.8/dist-packages/tornado/web.py", line 2430, in prepare
    raise HTTPError(self._status_code)
tornado.web.HTTPError: HTTP 404: Not Found

Container logs:

WARNING:tornado.access:404 GET /front_door/stream (172.16.82.1) 1.45ms

anna-oake Jun 14, 2021
Author

If I add static stream like this:

    static_mjpeg_streams:
      test-stream:
        width: 1280
        height: 720

I don't get any response from the server, it's just loading infinitely and there are no mjpeg frames:

❯ curl -v http://[redacted]:8888/front_door/static-mjpeg-streams/test-stream
*   Trying [redacted]...
* TCP_NODELAY set
* Connected to [redacted] ([redacted]) port 8888 (#0)
> GET /front_door/static-mjpeg-streams/test-stream HTTP/1.1
> Host: [redacted]:8888
> User-Agent: curl/7.64.1
> Accept: */*
>

And this in container logs:

[viseron.webserver.stream_handler] - Stream test-stream is not active, starting
[viseron.webserver.stream_handler] - Stream {mjpeg_stream} already active, number of streams: 2

gniknalu Jun 14, 2021

I copied most of what you've posted and didn't find an issue. (Well I had an 'issue' until realized that everything is lowercase even if the camera name has uppercase characters.)

If you do a 'netstat' do you see that it is LISTENing on 0 0.0.0.0:8888 for tcpv4? When you run curl do you see any connection via netstat?

I have logging set to "INFO" and when there was an error in the URI, I would receive a message in the log similar to:

WARNING:tornado.access:404 GET /****/static-mjpeg-streams/**** (xxx.xxx.xxx.xxx) 0.43ms

roflcoopter · 2021-06-14T20:48:00Z

roflcoopter
Jun 14, 2021
Maintainer

Any luck with the motion detection if you make it super sensitive? Something like this:

motion_detection:
  area: 0.00001
  threshold: 1
  alpha: 0.001
  frames: 1

I think the default values might be a bit too insensitive. Will look into it.

Regarding the streams, can you please post your docker-compose and the full log output?

2 replies

anna-oake Jul 14, 2021
Author

Hey, I've got a chance to try your config on a fresh dev tag today.

Still no recording at all
Both dynamic and static (test-stream from the config below) mjpeg streams return 200 OK and load infinitely (no frames)
Segments are created properly, I can open them and they look fine

I'm running this on my Intel NUC in a Docker container on Ubuntu 21.04.

Here is my config:

cameras:
  - name: Front door
    mqtt_name: front_door
    host: [redacted]
    port: 554
    path: /?user=admin&password=[redacted]&channel=0&stream=1.sdp
    audio_codec: aac
    publish_image: true
    motion_detection:
      interval: 1
      trigger_recorder: true
      trigger_detector: false
      area: 0.00001
      threshold: 1
      alpha: 0.001
      frames: 1
    object_detection:
      enable: false
    static_mjpeg_streams:
      test-stream:
        width: 1280
        height: 720
logging:
  level: debug

mqtt:
  [redacted]

Here is my log:

[2021-07-14 08:17:22] [INFO    ] [viseron                 ] - -------------------------------------------
[2021-07-14 08:17:22] [INFO    ] [viseron                 ] - Initializing...
[2021-07-14 08:17:22] [DEBUG   ] [viseron.watchdog        ] - Starting scheduler
[2021-07-14 08:17:22] [DEBUG   ] [viseron                 ] - Starting cleanup scheduler
[2021-07-14 08:17:22] [DEBUG   ] [viseron                 ] - Running initial cleanup
[2021-07-14 08:17:22] [DEBUG   ] [viseron.cleanup         ] - Running cleanup
[2021-07-14 08:17:22] [INFO    ] [viseron.mqtt            ] - Initializing MQTT connection
[2021-07-14 08:17:22] [DEBUG   ] [viseron.detector        ] - Initializing object detector darknet
[2021-07-14 08:17:22] [DEBUG   ] [viseron.mqtt            ] - MQTT connected with returncode 0
[2021-07-14 08:17:22] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic */frame/scan/object, <queue.Queue object at 0x7fd36f54a880>
[2021-07-14 08:17:22] [DEBUG   ] [viseron.detector        ] - Object detector initialized
[2021-07-14 08:17:22] [INFO    ] [viseron                 ] - Initializing NVR threads
[2021-07-14 08:17:22] [DEBUG   ] [viseron.nvr.front_door  ] - Initializing NVR thread
[2021-07-14 08:17:22] [DEBUG   ] [viseron.camera.front_door] - Initializing camera Front door
[2021-07-14 08:17:22] [DEBUG   ] [viseron.camera.stream.front_door] - Getting stream information for rtsp://[redacted]/?user=admin&password=[redacted]&channel=0&stream=1.sdp
[2021-07-14 08:17:25] [DEBUG   ] [viseron.camera.stream.front_door] - Stream information from FFprobe: Width: 704 Height: 576 FPS: 12.0 Video Codec: h264 Audio Codec: pcm_alaw
[2021-07-14 08:17:25] [DEBUG   ] [viseron.camera.front_door] - Resolution: 704x576 @ 12.0 FPS
[2021-07-14 08:17:25] [DEBUG   ] [viseron.camera.front_door] - Camera Front door initialized
[2021-07-14 08:17:25] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic front_door/frame/processed/object, <queue.Queue object at 0x7fd36ed22e50>
[2021-07-14 08:17:25] [DEBUG   ] [viseron.motion.front_door] - Initializing motion detector
[2021-07-14 08:17:25] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic front_door/frame/decode/motion, <queue.Queue object at 0x7fd36f54e130>
[2021-07-14 08:17:25] [DEBUG   ] [viseron.motion.front_door] - Starting decoder thread
[2021-07-14 08:17:25] [DEBUG   ] [viseron.motion.front_door] - Running decoder front_door.motion_detection at 1s interval, every 12.0 frame(s)
[2021-07-14 08:17:25] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic front_door/frame/scan/motion, <queue.Queue object at 0x7fd36ed2bdf0>
[2021-07-14 08:17:25] [DEBUG   ] [viseron.motion.front_door] - Motion detector initialized
[2021-07-14 08:17:25] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic front_door/frame/processed/motion, <queue.Queue object at 0x7fd36ed2b940>
[2021-07-14 08:17:25] [DEBUG   ] [viseron.nvr.front_door  ] - Starting camera
[2021-07-14 08:17:25] [DEBUG   ] [viseron.camera.front_door] - Starting capture thread
[2021-07-14 08:17:25] [DEBUG   ] [viseron.recorder.front_door] - Initializing ffmpeg recorder
[2021-07-14 08:17:25] [DEBUG   ] [viseron.camera.stream.front_door] - FFMPEG decoder command: front_door -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 -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -rtsp_transport tcp -i rtsp://[redacted]/?user=admin&password=[redacted]&channel=0&stream=1.sdp -f segment -segment_time 5 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac /segments/Front door/%Y%m%d%H%M%S.mp4 -filter:v fps=1 -f rawvideo -pix_fmt nv12 pipe:1
[2021-07-14 08:17:25] [DEBUG   ] [viseron.nvr.front_door  ] - Waiting for first frame
[2021-07-14 08:17:25] [DEBUG   ] [viseron.nvr.front_door  ] - NVR thread initialized
[2021-07-14 08:17:25] [INFO    ] [viseron                 ] - Initialization complete
[2021-07-14 08:17:25] [DEBUG   ] [viseron.mqtt            ] - Got topic viseron/front_door/switch/set, message ON
[2021-07-14 08:17:28] [DEBUG   ] [viseron.nvr.front_door  ] - First frame received
WARNING:tornado.access:404 GET / (172.16.82.1) 2.34ms
WARNING:tornado.access:404 GET /favicon.ico (172.16.82.1) 0.93ms

roflcoopter Jul 14, 2021
Maintainer

Try setting trigger_detector: true

When trigger_detector is false, motion detection wont run. This made total sense before when you couldnt disable the object detector.
This is a bit silly and not very user friendly. Will fix!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Can't get motion detection to work #215

{{title}}

Replies: 2 comments 7 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Can't get motion detection to work #215

anna-oake Jun 14, 2021

Replies: 2 comments · 7 replies

gniknalu Jun 14, 2021

anna-oake Jun 14, 2021 Author

gniknalu Jun 14, 2021

anna-oake Jun 14, 2021 Author

anna-oake Jun 14, 2021 Author

gniknalu Jun 14, 2021

roflcoopter Jun 14, 2021 Maintainer

anna-oake Jul 14, 2021 Author

roflcoopter Jul 14, 2021 Maintainer

anna-oake
Jun 14, 2021

Replies: 2 comments 7 replies

gniknalu
Jun 14, 2021

anna-oake Jun 14, 2021
Author

anna-oake Jun 14, 2021
Author

anna-oake Jun 14, 2021
Author

roflcoopter
Jun 14, 2021
Maintainer

anna-oake Jul 14, 2021
Author

roflcoopter Jul 14, 2021
Maintainer