Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: outdoor camera UK (Dave Howorth)
2. latest git fails to open netcam (S Andreason)
3. Re: latest git fails to open netcam (S Andreason)
4. Re: latest git fails to open netcam (MrDave)
----------------------------------------------------------------------
Message: 1
Date: Thu, 29 Jul 2021 20:58:24 +0100
From: Dave Howorth <d...@howorth.org.uk>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] outdoor camera UK
Message-ID: <20210729205824.1f312...@acer-suse.lan>
Content-Type: text/plain; charset=US-ASCII
On Thu, 29 Jul 2021 17:40:22 +0100
George Savage <gtsav...@gmail.com> wrote:
> Although I have one camera (Reolink) working with motion I would like
> another camera to check the wildlife in the back garden. Is there a
> list of cameras that work with motion - every one I can find appears
> to need a mobile app.
Personally I just bought a stand-alone Browning Recon Force Elite HP4
from Naturespy and am very happy with the results it produces.
Connecting something to my network from where the creatures lurk and/or
replacing batteries powering wi-fi or other radio links didn't appeal.
------------------------------
Message: 2
Date: Thu, 29 Jul 2021 13:36:37 -0700
From: S Andreason <sandrea...@gmail.com>
To: Motion-user <motion-user@lists.sourceforge.net>
Subject: [Motion-user] latest git fails to open netcam
Message-ID: <241e51b7-14d9-03dc-48aa-fe48f6a3c...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
I updated from git and recompiled fresh
?motion Version 4.3.1+git20210728-ea2b2a9
Now it fails to open the netcam as given in motion.conf.
The motion.log is empty, even at log_level 9
The only list of errors I can see is from
$ sudo service motion status
? motion.service - LSB: Start Motion detection
?? Loaded: loaded (/etc/init.d/motion; generated)
?? Active: active (running) since Thu 2021-07-29 13:13:33 PDT; 14s ago
???? Docs: man:systemd-sysv-generator(8)
? Process: 15297 ExecStart=/etc/init.d/motion start (code=exited,
status=0/SUCCESS)
??? Tasks: 2 (limit: 4915)
?? CGroup: /system.slice/motion.service
?????????? ??15303 /usr/bin/motion
Jul 29 13:13:41 raspberrypi3 motion[15303]: [0:motion] [NTC] [ALL] main:
Motion thread 1 restart
Jul 29 13:13:41 raspberrypi3 motion[15303]: [0:motion] [NTC] [ALL]
motion_start_thread: Camera ID: 0 Camera Name: (null) Device: /dev/video0
Jul 29 13:13:41 raspberrypi3 motion[15303]: [1:ml1] [NTC] [ALL]
motion_init: Camera 0 started: motion detection Enabled
Jul 29 13:13:41 raspberrypi3 motion[15303]: [1:ml1] [NTC] [VID]
vid_start: Opening V4L2 device
Jul 29 13:13:41 raspberrypi3 motion[15303]: [1:ml1] [NTC] [VID]
v4l2_device_open: Using videodevice /dev/video0 and input -1
Jul 29 13:13:41 raspberrypi3 motion[15303]: [1:ml1] [ALR] [VID]
v4l2_device_open: Failed to open video device /dev/video0: No such file
or directory
Jul 29 13:13:41 raspberrypi3 motion[15303]: [1:ml1] [ERR] [VID]
vid_start: V4L2 device failed to open
Jul 29 13:13:41 raspberrypi3 motion[15303]: [1:ml1] [WRN] [ALL]
motion_init: Could not fetch initial image from camera
Jul 29 13:13:41 raspberrypi3 motion[15303]: [1:ml1] [WRN] [ALL]
motion_init: Motion continues using width and height from config file(s)
Jul 29 13:13:41 raspberrypi3 motion[15303]: [1:ml1] [NTC] [ALL]
image_ring_resize: Resizing pre_capture buffer to 1 items
/etc/motion/motion.conf does have the lines:
videodevice netcam
netcam_url rtsp://admin:password@192.168.254.205/Streaming/Channels/102
I get the same result on different cameras, so not just one model.
I noticed the rtsp source files were recently edited. Is this a newly
introduced bug?
------------------------------
Message: 3
Date: Thu, 29 Jul 2021 14:59:03 -0700
From: S Andreason <sandrea...@gmail.com>
To: Motion-user <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] latest git fails to open netcam
Message-ID: <686a1742-7e21-c47e-1c9f-9a80f87f6...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Disregard my last email. After 5 hours of working on this, of course it
is after sending an email that I discover the problem.... turned off
daemon mode, got lots of write permission errors, but finally could see
something helpful:
"videodevice" replaced with "video_device" after version 4.3.2
Another hour plus later, I'm still unable to get motion to work, from
motion.log
[1:ml1:205_HikVisi] [NTC] [VID] [Jul 29 14:12:30] vid_start: Opening
Netcam RTSP
[1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30] netcam_rtsp_set_parms:
Setting up norm stream.
[1:ml1:205_HikVisi] [INF] [ALL] [Jul 29 14:12:30] util_parms_add:
Parsed: >decoder< >NULL<
[1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30] netcam_rtsp_set_path:
Setting up rtsp via netcam
[1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30]
netcam_rtsp_set_options: norm: Setting rtsp/rtmp
[1:ml1:205_HikVisi] [INF] [ALL] [Jul 29 14:12:30] util_parms_add:
Parsed: >rtsp_transport< >tcp<
[1:ml1:205_HikVisi] [INF] [ALL] [Jul 29 14:12:30] util_parms_add:
Parsed: >allowed_media_types< >video<
[1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30]
netcam_rtsp_set_options: norm: option: rtsp_transport = tcp
[1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30]
netcam_rtsp_set_options: norm: option: allowed_media_types = video
[1:ml1:205_HikVisi] [INF] [ENC] [Jul 29 14:12:30] ffmpeg_avcodec_log:
Port missing in uri
[1:ml1:205_HikVisi] [ERR] [NET] [Jul 29 14:12:30]
netcam_rtsp_open_context: norm: Unable to open camera(205_HikVision_N):
Invalid argument
[1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30] netcam_rtsp_cleanup:
norm: Shutting down network camera.
[1:ml1:205_HikVisi] [NTC] [NET] [Jul 29 14:12:30] netcam_rtsp_cleanup:
Normal resolution: Shut down complete.
[1:ml1:205_HikVisi] [ERR] [VID] [Jul 29 14:12:30] vid_start: Netcam RTSP
failed to open
S Andreason wrote:
> /etc/motion/motion.conf does have the lines:
> videodevice netcam
>
------------------------------
Message: 4
Date: Thu, 29 Jul 2021 17:56:47 -0600
From: MrDave <motionmrd...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] latest git fails to open netcam
Message-ID: <547899c3-77d1-4f2c-6eca-6abfe2c48...@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
I think the revision I pushed last night may be tripping it up but I'm
not quite ready to revoke it.? (I may however add additional documentation)
Motion historically restricted the protocols that it would support and
many issues have been raised regarding expanding the list.? The revision
removed the restriction on what is supported and leaves it open to the
user to specify the right URI.? So it will now support http, https,
rtsp, rtsps, etc, etc.? Whatever ffmpeg supports, Motion just passes the
URI along to ffmpeg. BUT.....in order to do this, the default ports
become a problem. There is no longer a fixed list of protocols.
So from looking at your log, it seems that you may need to put in 554,
80 or something else into your netcam_url string so it addresses the message
[1:ml1:205_HikVisi] [INF] [ENC] [Jul 29 14:12:30] ffmpeg_avcodec_log:
Port missing in uri
Dave
On 7/29/2021 3:59 PM, S Andreason wrote:
> Disregard my last email. After 5 hours of working on this, of course
> it is after sending an email that I discover the problem.... turned
> off daemon mode, got lots of write permission errors, but finally
> could see something helpful:
>
> "videodevice" replaced with "video_device" after version 4.3.2
>
> Another hour plus later, I'm still unable to get motion to work, from
> motion.log
>
> [1:ml1:205_HikVisi] [NTC] [VID] [Jul 29 14:12:30] vid_start: Opening
> Netcam RTSP
> [1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30]
> netcam_rtsp_set_parms: Setting up norm stream.
> [1:ml1:205_HikVisi] [INF] [ALL] [Jul 29 14:12:30] util_parms_add:
> Parsed: >decoder< >NULL<
> [1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30]
> netcam_rtsp_set_path: Setting up rtsp via netcam
> [1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30]
> netcam_rtsp_set_options: norm: Setting rtsp/rtmp
> [1:ml1:205_HikVisi] [INF] [ALL] [Jul 29 14:12:30] util_parms_add:
> Parsed: >rtsp_transport< >tcp<
> [1:ml1:205_HikVisi] [INF] [ALL] [Jul 29 14:12:30] util_parms_add:
> Parsed: >allowed_media_types< >video<
> [1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30]
> netcam_rtsp_set_options: norm: option: rtsp_transport = tcp
> [1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30]
> netcam_rtsp_set_options: norm: option: allowed_media_types = video
> [1:ml1:205_HikVisi] [INF] [ENC] [Jul 29 14:12:30] ffmpeg_avcodec_log:
> Port missing in uri
> [1:ml1:205_HikVisi] [ERR] [NET] [Jul 29 14:12:30]
> netcam_rtsp_open_context: norm: Unable to open
> camera(205_HikVision_N): Invalid argument
> [1:ml1:205_HikVisi] [INF] [NET] [Jul 29 14:12:30] netcam_rtsp_cleanup:
> norm: Shutting down network camera.
> [1:ml1:205_HikVisi] [NTC] [NET] [Jul 29 14:12:30] netcam_rtsp_cleanup:
> Normal resolution: Shut down complete.
> [1:ml1:205_HikVisi] [ERR] [VID] [Jul 29 14:12:30] vid_start: Netcam
> RTSP failed to open
>
>
> S Andreason wrote:
>> /etc/motion/motion.conf does have the lines:
>> videodevice netcam
>>
>
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 181, Issue 17
********************************************
