Re: [Motion-user] Motion as a security camera

[Andy B. <and...@gm...>]

On 15 December 2013 01:45, C.T. <sem...@ya...> wrote:

> I got this same one for about $12 on dx.com, back when Windows was my
> surveillance platform (and may become again if I can't find a suitable way
> to turn Motion on and off manually and quickly), Glad to see it also works
> on Linux i386, but you specifying it doesn't work in ARM Linux is one
> reason I tend to shy away from "exotic" solutions such as the Pi. I got no
> desktop computer at the moment, though it may change as I will need to
> build a NAS and no ready-built model seems to provide what I want for the
> price point I am aiming for. There is a 4-channel USB interface model
> available (without audio): how does it fare in Linux?
>
> You listed the Qvis.Dahua cameras, and while they look interesting, in the
> same price range I saw Foscam ones. However, no indication if either would
> be able to clearly make out a face 20 m away (exterior one I need). Needs
> to be tolerant of low (-20) and high (50) temperatures while operating.
> Neither of those will support Motion on the board itself, but their IP
> models do support direct upload to FTP server (SFTP remains an elusive
> dream). Have you tried direct upload to FTP with the Dahua?
>
> I know these question may seem silly for someone who has already built his
> security system, but I have one pretty tough requirement: time between
> capture and completed remote recording in case of a break-in must not
> exceed 30 seconds. I also expect cams to be destroyed. So smallest file
> sizes, highest possible quality, and remote-recording while capture is
> taking place are necessary-
>
> Does Motion support such "stream-recording", without making a local copy
> first?
>
>
Hello,

Maybe you can take a look at the http-control-API to stop/start motion
detection (also to stop the motion-process). It can ge done with a simple
http-request. I also use this interface for tuning the config parameters.
About running on ARM: I'm running in on a Synology DS209 NAS (but it's
using a lot of cpu), but 4 cams would be too much for my device. For faster
(multicore) devices, it should work I guess.

I'm currently running 3 applications for surveillance against a single
camera:
-Onboard on the camera (panasonic BB-HCM531): very convenient and easy
because of the standalone nature, but config parameters are limited and too
many false positives.
-Synology Surveillance station: easy setup, good looking interface but no
'that's it feeling', and also I cannot tweak the motion detection
parameters, always missing motion events and still false positves.
-motion (On same NAS): it surely is no plug'n'play, you need to hook some
alerting mechanism, some 'easy' viewer (currently using
http://www.lavrsen.dk/foswiki/bin/view/Motion/MotionJpegViewer). But motion
is definitely the best/most accurate motion detector of the three.

weak points of motion (to my opinion):
-only mjpeg and constant recompression
-motion detection on every frame and on full resolution (I would prefer to
record the exact incomming stream, and detect of 'derived' stream of lower
fps and resolution). (I prefer a detection mechanism like
https://github.com/sgjava/cvp/wiki/Architecture , but it uses so many
frameworks, I think it's less accessable and more difficult to use on
different platforms)
I'm also waiting on easy and lightweigth plug'n'play surveillance software.
(I think dedicated NVR devices like
http://ipcorder.com/product/ipcorder-knr-1000-series/ are also valid
options, but I don't have experience with these devices and don't how how
they accomplish off-site backup).

About the Foscam: it is good value for the money, but for these kind of
devices it is really cheap. I experimented with some FI8905W models. My
conclusion was: it is a cheap camera, it gives reasonable image quality,
not superior but good. The problem is the firmware: lot's of quircks to get
wireless configured (meanwhile that seems to be fixed), and also the
control of the imager, leds and IR-filter are way too basic. They result in
images constantly getting brighter/darker. sometimes 'half'-gray frames.
The detection settings are primitive, and upload/alerting settings were
'fancy' (who needs MSN-notifications?), but not sufficient.

Face detection at 20m is not possible with my models, but maybe it can be
done with the new HD models or with another lens. (which I hope have much
better firmware by now)

Just my humble opinion :)
Grtz,
Andy