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: raspberry pi libcamera motion bulseye (tosiara)
   2. Re: Making cheap IP Camera work with motion (Giampiero Campa)


----------------------------------------------------------------------

Message: 1
Date: Tue, 16 Nov 2021 16:46:11 +0200
From: tosiara <tosi...@gmail.com>
To: Ed Kapitein <e...@kapitein.org>
Cc: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] raspberry pi libcamera motion bulseye
Message-ID:
        <cachtdwqaheayuqv+-pep-xpbut-doiqfbobyahpl_d1aq4f...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

I'm not aware if there are any talks with Raspberry Pi team. But
MrDave has created an issue in motion's github:
https://github.com/Motion-Project/motion/issues/1434

On Tue, Nov 16, 2021 at 11:15 AM Ed Kapitein <e...@kapitein.org> wrote:
>
> Yes, same PI, same camera, just rebooted.
>
> My guess is that taking a picture with libcamera-still caused this change.
>
> Are you in contact with the raspberry pi team, or the libcamera team, so
> they can be notified of the driver problem?
>
>
> Kind regards,
>
> Ed
>
>
> On 11/16/21 10:07 AM, tosiara wrote:
> > Your log now is different:
> >
> > Was:
> >
> > [1:ml1] [NTC] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: Supported 
> > palettes:
> > [1:ml1] [NTC] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: (0) pBAA
> > (10-bit Bayer BGBG/GRGR Packed)
> > [1:ml1] [DBG] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: 0 - 10-bit
> > Bayer BGBG/GRGR Packed (compressed : 0) (0x41414270)
> > [1:ml1] [NTC] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: (1) BG10
> > (10-bit Bayer BGBG/GRGR)
> > [1:ml1] [DBG] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: 1 - 10-bit
> > Bayer BGBG/GRGR (compressed : 0) (0x30314742)
> > [1:ml1] [NTC] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: (2) BA81
> > (8-bit Bayer BGBG/GRGR)
> > [1:ml1] [DBG] [VID] [Nov 15 13:27:34] v4l2_pixfmt_select: 2 - 8-bit
> > Bayer BGBG/GRGR (compressed : 0) (0x31384142)
> >
> > Now:
> >
> > [1:ml1] [NTC] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: Supported 
> > palettes:
> > [1:ml1] [NTC] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: (0) pRAA
> > (10-bit Bayer RGRG/GBGB Packed)
> > [1:ml1] [DBG] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: 0 - 10-bit
> > Bayer RGRG/GBGB Packed (compressed : 0) (0x41415270)
> > [1:ml1] [NTC] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: (1) RG10
> > (10-bit Bayer RGRG/GBGB)
> > [1:ml1] [DBG] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: 1 - 10-bit
> > Bayer RGRG/GBGB (compressed : 0) (0x30314752)
> > [1:ml1] [NTC] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: (2) RGGB
> > (8-bit Bayer RGRG/GBGB)
> > [1:ml1] [DBG] [VID] [Nov 16 09:09:09] v4l2_pixfmt_select: 2 - 8-bit
> > Bayer RGRG/GBGB (compressed : 0) (0x42474752)
> >
> > The third pixel format changed from BA81 to RGGB (8-bit Bayer
> > BGBG/GRGR (compressed : 0) (0x31384142) to 8-bit Bayer RGRG/GBGB
> > (compressed : 0) (0x42474752))
> >
> > If you are still using the same camera module, then something is
> > seriously wrong with the driver
> >
> > On Tue, Nov 16, 2021 at 10:40 AM Ed Kapitein <e...@kapitein.org> wrote:
> >> Hi Tosiara,
> >>
> >> Thanks for your support so far, i appreciate it!
> >>
> >> Yesterday i found out that after a clean reboot *none* of the
> >> resolutions are working.
> >>
> >> So the logs i attached are after a clean reboot and motion is not
> >> working with any of the resolutions.
> >>
> >> However, if i take a picture with libcamera-still, and then start
> >> motion, motion will work with a 640x480 resolution, although the image
> >> is cropped. (to small FoV)
> >>
> >> So this leads me to believe there are two problems going on here:
> >>
> >> -1 libcamera crops the image at certain resolutions, as described in [1]
> >>
> >> -2 motion is not initializing the camera correctly, it only works after
> >> taking a picture, which initializes the camera module.
> >>
> >> Kind regards,
> >>
> >> Ed
> >>
> >> [1]
> >> https://www.raspberrypi.com/documentation/accessories/camera.html#known-issues
> >>
> >> On 11/16/21 8:03 AM, tosiara wrote:
> >>
> >>> Could you specify BA81 3280x2464 pixel format, run motion with -d 9
> >>> and send the log? I'd like to see the "non-working" log On Mon, Nov
> >>> 15, 2021 at 8:59 PM Ed Kapitein via Motion-user
> >>> <motion-user@lists.sourceforge.net> wrote:
> >>>> Some of the observations i made are described in the known issues
> >>>>> < SNIP ><



------------------------------

Message: 2
Date: Tue, 16 Nov 2021 16:01:57 -0500
From: Giampiero Campa <giampiero.ca...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Making cheap IP Camera work with motion
Message-ID:
        <CAOH8zGNDLn8KGm0=mh5kveosfpvdgx3aadppqzv_qyz3ymv...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Thank you Henk and David for your answer.
This is the output of a scan on port 554:

-------------------------------------------------------------------------------------
giampy@BOS-DNLP:~$ sudo nmap -p 554 192.168.1.101
[sudo] password for giampy:
Starting Nmap 7.80 ( https://nmap.org ) at 2021-11-16 15:26 EST
Nmap scan report for 192.168.1.101
Host is up (0.095s latency).

PORT    STATE  SERVICE
554/tcp closed rtsp
MAC Address: B8:0C:0A:0C:01:CF (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 0.56 seconds
-------------------------------------------------------------------------------------

indeed trying rtsp:// in a browser opens a video app saying that it cannot
connect to the resource.
I have tried the following (in a browser only) but it cannot connect either.
http:/<IPAddress>/webcapture.jpg?user=admin&password=<Password>&command=snap&chanel=1

In the mean time, the camera looks exactly like this one:
https://www.centralspyshop.com/video-surveillance-equipment/spy-covert-video-nanny-cameras/spy-cameras-recorders-dvr/dual-port-usb-mac-apple-charger-covert-camera.html
so maybe i can find more info on supported formats (it does say it supports
H.264, tough i do not think there is any SD card).
I am going to try ONVIF device manager or Onvir later.

By the way, the camera has a built in motion detection system (see attached
images) that maybe, just maybe can be also be used.
Do you know how these cameras are supposed to work with their apps? I guess
when they detect motion they record a video somewhere in the filesystem and
then the app accesses the filesystem (presumably through port 80?) to
collect the video? Any idea?

Thanks for your thoughts, as usual.
Giampiero

On Mon, Nov 15, 2021 at 5:08 AM Henk Demper <henk_dem...@hotmail.com> wrote:

> ...the suggested RTSP URL would only work if port 554 is open, conflicting
> with:
>
> A scan with nmap shows that port 80 seems to be the only one open.
>
>
> If the latter is correct, and only port 80 is open, then RTSP on port 554
> will obviously fail...
>
> Henk Demper
>
> On 15 Nov 2021, at 10:27, Henk Demper <henk_dem...@hotmail.com> wrote:
>
> Hi Giampiero,
>
> I have a bunch of different brand/model, cheap $15-$25 HD cameras from
> AliExpress and although not documented from the box, they *all* work
> (after some experimenting indeed with ONVIF as Andr? suggests & web
> searches), returning a RTSP HD stream using:
>
> netcam_url
> rtsp://<IPAddress>:554/user=admin&password=<Password>&channel=1&stream=0.sdp?real_stream
>
> You can also get still images off (I use with wget in home automation) in
> SD quality using:
>
>
> http:/<IPAddress>/webcapture.jpg?user=admin&password=<Password>&command=snap&chanel=1
>
> Notice the exact spelling (like 'chanel') ;-)
>
> You might give those a try ?
>
> Henk Demper
>
> On 15 Nov 2021, at 2:24, Andr? H?nsel <an...@webkr.de> wrote:
>
> Try connecting to it with ONVIF Device Manager. I will probably support
> ONVIF and you can get the RTSP URL from it.
>
> *From:* Giampiero Campa [mailto:giampiero.ca...@gmail.com
> <giampiero.ca...@gmail.com>]
> *Sent:* Montag, 15. November 2021 02:17
> *To:* Motion-user@lists.sourceforge.net
> *Subject:* [Motion-user] Making cheap IP Camera work with motion
>
> Hi All,
>
> I have a cheap IP camera that used to work with an iphone app which has
> been removed from the app store last year or so.
>
> Recently I played with it a bit and noticed that you can connect to it
> (and access the settings) via http. You can see a pretty good live image
> using http://192.168.1.111/video/livesp.asp
>
> Unfortunately I do not have much information about the formats it
> supports. If you go to the settings the only information is as follows:
>
> Device SN
> V200
> Hardware Version
> 2.0
> Firmware Version
> 1.9.8
> UID
> CM4F5B-38A550D4CF04-74B359
> Lan MAC
> WiFi MAC
> b8:0c:0a:0c:01:cf
> There is a QR code on it but if i scan it it only brings up the UID above.
> A search for it does not find anything. A scan with nmap shows that port 80
> seems to be the only one open.
>
> I have been able to use motion previously with both a built-in and a USB
> camera, with excellent results (thanks), but I haven't been able to make it
> work with this IP camera.
>
> I have tried stuff like the following in the config file:
>
> netcam_url http://admin:adminpwd@192.168.1.101/video/livesp.asp
> netcam_url http://192.168.1.101/video/livesp.asp?user=admin&pwd=adminpwd
> netcam_keepalive on
>
> But it cannot connect. I do not know what format it supports. I have tried
> to access it using rtsp://, rtmp:// and more but no success.
>
> Any clue to what I could do or try?
>
> Thanks a lot in advance.
> Giampiero
>
>
> _______________________________________________
> 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
>
>
>
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CamAS1.png
Type: image/png
Size: 55019 bytes
Desc: not available
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CamAS2.png
Type: image/png
Size: 47971 bytes
Desc: not available

------------------------------



------------------------------

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 185, Issue 17
********************************************

Reply via email to