Surveillance camera based on BuildRoot and Motion

[Saffik]

Hello All,

This is a question for everyone and, would appreciate all your responses if possible.

I'm currently putting together a CCTV system and currently I've got 1 USB webcam (Live! Cam Sync HD) which works great with MotionPie (thanks to ccrisian).

As most of my camera/cctv will be based outdoors which mean they need to be all weather proof and day/night capable (Infrared at night perhaps..) and would ideally be wall mounted, so does anyone know which USB wall mounted day/night outdoor camera's work with MotionPie (powered by USB power hub) that I could buy?

I have already tried to buy some DVR-webcam wall mounted but unfortunately they didn't work in MotionPie and failed to detect. They did not work on Raspbian either so I guess they are not compatible.

Any suggestions?

Thank you.
Saf

[hockinfinger]

Another question regarding motionpie: I have 2 units running motionpie, (1) A+ and (1) B type RPi.

The A+ model seemed to frequently lose connection to the pi camera. Rebooting seems to fix it for a while. I took a look at the motioneye.log file and discovered it was over 26MB in size... a few hundred thousand lines. I looked at some of the entries and saw quite a few "unable to allocate memory" lines. I deleted the log file yesterday, and since then have not had any lost camera connections. Also the current log file since yesterday only contains 27 lines.

My B model's log file is about 4MB and I've been running it nearly as long as the A+.

Any clue what I should look for in the motioneye.log file if this happens again?

[sidb]

Hi

Should Rasberry Pi 2 work ok with latest MotionPie? I can't seem to get it to boot - quick flicker of the activity light at power up then nothing. Am trying with a fresh image written with writeimage.sh

Thanks

[ccrisan]

No.

Hi

Should Rasberry Pi 2 work ok with latest MotionPie? I can't seem to get it to boot - quick flicker of the activity light at power up then nothing. Am trying with a fresh image written with writeimage.sh

Thanks

[GordonTGopher]

No.

Given the hardware changes 'under the bonnet; I'd have been surprised if it worked with no changes.

Are you working / do you plan to work on a version that will work on the Pi2?

Thanks for a great piece of software.


Gordon

[ccrisan]

Yes, there will be a motionPie version for the PI2 as soon as I get my hands on such a PI2 device.

No.

Given the hardware changes 'under the bonnet; I'd have been surprised if it worked with no changes.

Are you working / do you plan to work on a version that will work on the Pi2?

Thanks for a great piece of software.


Gordon

[ccrisan]

Hello there,

I just wanted to let you know that motionPie has made its first steps towards a board-agnostic video surveillance distro. Thanks to a very kind user who donated a BananaPI and an Odroid C1, I have been able to port motionPie to BananaPI (and soon to Odroid C1). Owners of a Banana PI board can grab the testing OS image from here: https://github.com/ccrisan/motionPie/re ... g/20150208. Feedback is always welcomed.

As a side note, the wiki has been reorganized for an easier access to documentation.

P.S. A version for the Rasperry PI 2 is also on its way.

[petay]

the RTC i personally own needs an extra kernel module, and works via i2c

http://afterthoughtsoftware.com/products/rasclock

Im sure others will be slightly different though!!!

I know the AP mode is rather sketchy, only a handful of adapters support it. just thinking of solutions to my perticular problem. The RTC pretty much becomes redundant without the AP mode, as it will be able to get its time from the network

Thanks for the awesome work

Pete

[AtomicEdge]

Really loving the system!

I tried using 2 USB webcams, and either of them work by themselves, but if both are plugged in I can only get one to show.

Really looking forward to the Pi 2 release, I want to hook 3 cams up to one.

Also, as well at the Pi 2 with 3 cams, would it be possible for me to plug a cam into my existing Pi 2 setup, and then use it's streaming URL to add that one to the Pi 2 as an IP camera? It's a long shot, but being able to manage all my cameras from one interface would be great.

[Saffik]

Hi ccrisan,

I would like to setup SSH_Keys to connect via PuTTY into the raspberry pi running the latest version of motionPi.
I have generated the keys using:

1) ssh-keygen
2) Then I renamed the 'id_rsa.pub' to 'ssh_authorized_keys'
3) Copied to /data/etc/ssh_authorized_keys
4) Rebooted pi so that changes takes effect
5) I am now able to login as 'root' but it does not ask me for the password! (Which is what I want)
I wanted to know, how can I permanently disable password login and only allow login via SSH key.

I think under /etc/sshd_config .... i changed a param called 'EnableRootLogin' (or something similar) from yes to no and I'm no longer able to login at all... or even use MotionEye (via browser)


Also, was wondering how can we restart ssh configuration?
In Raspbian I used to use 'sudo /etc/init.d/ssh restart' but that doesnt work on MotionPi.

[ccrisan]

Hi,

To disable SSH password authentication, add "PasswordAuthentication no" to /etc/sshd_config. Leave EnableRootLogin enabled, as root is the only user you can login with

To restart sshd you should probably do something like /etc/init.d/S50sshd restart, but don't do it over SSH - I think it will disconnect your shell; I recommend rebooting - it's fast enough.

Hi ccrisan,

I would like to setup SSH_Keys to connect via PuTTY into the raspberry pi running the latest version of motionPi.
I have generated the keys using:

1) ssh-keygen
2) Then I renamed the 'id_rsa.pub' to 'ssh_authorized_keys'
3) Copied to /data/etc/ssh_authorized_keys
4) Rebooted pi so that changes takes effect
5) I am now able to login as 'root' but it does not ask me for the password! (Which is what I want)
I wanted to know, how can I permanently disable password login and only allow login via SSH key.

I think under /etc/sshd_config .... i changed a param called 'EnableRootLogin' (or something similar) from yes to no and I'm no longer able to login at all... or even use MotionEye (via browser)


Also, was wondering how can we restart ssh configuration?
In Raspbian I used to use 'sudo /etc/init.d/ssh restart' but that doesnt work on MotionPi.

[aknisley]

Installed this and it is exactly what I have been trying on and off for a year and never got it to work this well. Thank you very much. Going to put the camera on my 3D printer to monitor it.

[mikerr]

I've had this runing rock solid on a model B for a while,
but just tried it on a model A+ and it seems to crash after a minute .

I see some other comments above with problems on A+ ...is it a memory issue?

[ccrisan]

Yeap, there might be some memory issues with A+ models (and 256 MB models, in general). I'm not sure what to do about it. Probably reducing the GPU memory will solve the issue but will probably generate problems with the CSI camera. I'm thinking of making this GPU mem setting configurable and leave a note somewhere in the wiki about these issues.

I've had this runing rock solid on a model B for a while,
but just tried it on a model A+ and it seems to crash after a minute .

I see some other comments above with problems on A+ ...is it a memory issue?

[ccrisan]

I have released 20150214 which is a testing release that brings support for Raspberry PI 2. Please test it and let me know of any issues you may encounter, so I can make a final stable release soon.

[mikerr]

I've had this runing rock solid on a model B for a while,
but just tried it on a model A+ and it seems to crash after a minute .

I see some other comments above with problems on A+ ...is it a memory issue?

I connected HDMI monitor up and saw plenty of segfaults on A+

Didn't realise there was a default overclock in this image:

- I've deleted all the overclock details out of config.txt so it now looks like this:

Code: Select all

start_file=start.elf
fixup_file=fixup.elf
gpu_mem_256=128
gpu_mem_512=128
disable_camera_led=0

and it now works fine on my A+

[ccrisan]

Oups, that might be the cause indeed. I will reduce the default overclock to 800 to prevent this kind of issues. Thanks for reporting it.

I've had this runing rock solid on a model B for a while,
but just tried it on a model A+ and it seems to crash after a minute .

I see some other comments above with problems on A+ ...is it a memory issue?

I connected HDMI monitor up and saw plenty of segfaults on A+

Didn't realise there was a default overclock in this image:

- I've deleted all the overclock details out of config.txt so it now looks like this:

Code: Select all

start_file=start.elf
fixup_file=fixup.elf
gpu_mem_256=128
gpu_mem_512=128
disable_camera_led=0

and it now works fine on my A+

[ccrisan]

Hi,

The stable 20150215 version is out.

On a side note, at the suggestion of one of the motionPie users I have created a facebook page for the project. I guess it could be an easier way to bring users together and to share their problems and success stories.

[hairynoggin]

will you keep this thread going? A few of us....probably a very few, don't use facebook

[ccrisan]

I will keep answering to posts that show up in this thread, of course.

will you keep this thread going? A few of us....probably a very few, don't use facebook

[sidb]

Just installed 20150215 on a Pi 2 via writeimage.sh on an old Pi B. Up and running in no time without any problems (apart from it not liking the first 2 Logitech webcams I tried).

Good work as usual - many thanks.

[angusmedia]

in
nano /programs/motioneye/templates/main.html

line 3 should be replaced by:

{% block title %}{% if title %}{{title}}{% else %}{{hostname}}{% endif %}{% endif %}{% endblock %}


So not all cams are called "motionpie" but the hostname is visible in browsertab.

[ccrisan]

Thanks, this is actually a good idea.

in
nano /programs/motioneye/templates/main.html

line 3 should be replaced by:

{% block title %}{% if title %}{{title}}{% else %}{{hostname}}{% endif %}{% end$

So not all cams are called "motionpie" but the hostname is visible in browsertab.

[mikerr]

I'm now getting the error "unable to load image list" (after 30 seconds on the progress wheel) when trying to view the captured images from the web page.
A reboot didn't help.

I can still view them from the samba share though.

[ccrisan]

Approximately how many images do you have? Working with many pictures over a samba share can often prove to be very slow. If you don't think you have a considerable number of pictures, then I'd like to see your motioneye.log file after such an error.

I'm now getting the error "unable to load image list" (after 30 seconds on the progress wheel) when trying to view the captured images from the web page.
A reboot didn't help.

I can still view them from the samba share though.