Introduction and Motivation for Project
Recently my wife and I suspected that some unwanted guests had been visiting our garden. After a discussion we decided that we needed a motion activated camera that could send us emails once it detected movement. We also wanted the ability to view the live video stream from the camera on demand.
As a fully fledged Raspberry Pi geek I knew right away that I wanted to build my own solution. My wife was not so convinced, and starting listing the dozens of unfinished projects I currently have on my backlog. After promising her that I would see this project through to the bitter end I finally got permission to build a proof of concept :)
This project required no coding, but quite a bit of configuration. It took about 6-7 hours to complete once I had the parts in place. I spent most of this time wrestling with Linux and this blog will hopefully help anyone attempting a similar project.
To reduce the projects overall complexity I decided that the camera would be mounted inside our living room. This meant that the unit could be powered from the mains, and would be protected from the harsh Norwegian weather.
Below is a full list of the parts I used, along with current prices. I already had some of these parts laying around from previous projects, so my total project cost came up to about $40. If you need to purchase all of the below parts then I would suggest shopping around and looking into Pi Zero starter kits to keep your costs low.
- Raspberry Pi Zero Model 1.3 : $5
- SD Card with NOOBS : $8
- Micro USB Power Supply : $6
- Combined WiFi Dongle and USB Hub : $13
- ZeroView Camera Mount : $9
- Raspberry Pi NoIR Camera : $26
- Pi Zero camera cable : $5
- Mini HDMI adapter : $7
- Mini USB adapter : $3
Some notes about some of the specific parts:
- The Combined WiFi Dongle and USB Hub has two USB ports, allowing me to connect a keyboard and optionally a mouse when setting up the Pi Zero for the first time. The Pi Zero has only one mini USB port available, so this dongle is a worthwhile investment for the most Pi Zero projects.
- I chose the Raspberry Pi NoIR Camera rather than the standard model as the NoIR can work in low light conditions (you'll add need to add infrared lighting for this camera to perform well at night time). Edit March 2017: It's important to add that here the standard Raspberry Pi Camera provides better picture quality, so you'll need to think about your use case before buying.
- The ZeroView Camera Mount allowed for easy mounting of the camera and Pi Zero on the inside of my terrace window. It is a mount, not a case, and is not suitable for outside usage.
- If you struggle to pick up the Raspberry Pi Zero you can always use a Raspberry Pi Model 2 or 3. Both have CSI and USB ports and the Model 3 even has built-in WiFi. If you choose to do this you will want to reevaluate using the ZeroView Camera Mount.
Once I had all the pieces in place it took less than 10 minutes to put my prototype together.
Configuring the Pi Zero
After assembling the parts I connected a keyboard and monitor to the USB Hub and switched on the Pi Zero. After booting I installed Raspian Jessie 4.4 from NOOBS.
I configured the Pi Zero as follows, with frequent reboots underway...
From the terminal window run the command:
This will open the Raspberry Pi Configuration tool, from which you should do the following:
- Enable the Camera.
- Enable the ssh server (you’ll need this later on to connect to Pi Zero in headless mode - i.e. without a monitor and keyboard attached).
- Enable boot to command line without manual login.
At the terminal prompt type enter:
to change your password from the default. This will prevent tech savvy intruders from connecting to your Pi Zero using ssh and the default login and password.
Next you should set up a static IP address for your Pi Zero. This will make it easier for you to connect to your Pi Zero and to expose it outside of your home network via port forwarding. You can validate that your static IP address is working by connecting to your Pi Zero via ssh.
Now that you are connecting to the web, you can update Raspian Jessie by running:
sudo apt-get update
sudo apt-get dist-upgrade
If you forget to do this then I can promise that you will have problems later on!
Finally, Validate that your Raspberry Pi Camera is working. If you experience any problems, check the ribbon cable between the Pi Zero and camera - it can easily be dislodged.
Once all the above is done you can disconnect the monitor and keyboard and connect to the Pi Zero via ssh to complete the rest of the below steps.
Choosing Motion for the Camera Software
My next step was to choose a software solution for my security camera. My requirements were as follows:
- Streaming video - so that I could check the video feed at will.
- Motion detection and the ability to trigger events - so that I could send myself an email for each motion event.
- Small footprint - due to the size of the SD card (8GB).
- Low memory overhead - due to the capacity of the Pi Zero.
- Linux compatible (well duh).
- Compatible with the Raspberry Pi Camera (MMAL).
- Configurable - allowing one to tweak the software to get the most out of the hardware.
I choose Motion as it fulfills the above requirements out of the box with no additional coding. I also considered using the marvellous OpenCV, but felt that I would have spent more time having to tweak it to fulfill my needs.
Motion monitors an incoming camera stream and detects 'motion' by finding the pixel values that have changed from frame to frame. If a threshold (i.e. total pixels changed) is exceeded then Motion triggers a "motion detected" event and optionally creates a snapshot of the video stream. Motion includes an inbuilt webserver offering both a video stream and online configuration on the fly.
Important : before installing Motion you must have updated Raspian Jessie by running the 'sudo apt-get update' and 'sudo apt-get dist-upgrade' commands.
I found that installing Motion from the deb release file worked best, probably because the Raspberry Pi Camera requires a specific release:
- First get the deb file with the following command (if this doesn’t work then have a look for the correct release file on the Motion project GitHub):
- Install the gdebi tool as follows:
sudo apt-get install gdebi-core
- Install Motion using the gdebi tool (allow it to also install the minimal web server):
sudo gdebi pi_jessie_motion_4.0.1-1_armhf.deb
- Create a hidden folder in your home directory:
- Copy the original Motion config file to your new .motion directory. This ensures that the original config file doesn't get ruined (and can be used to return Motion to it's 'factory settings').
cp /etc/motion/motion.conf ~/.motion/motion.conf
Don't bother trying to run Motion yet as it won't work until you've updated the configuration file :)
You can open the configuration file in edit mode by entering:
sudo nano ~/.motion/motion.conf
Nano is a simple Linux text editor allowing you to edit and search text files. Feel free to use an alternative text editor if you wish.
Below is a list of the parameters that I have tweaked for my setup. Consult the manual for comprehensive documentation of these and other Motion parameters. Note that the rest of these blog will assume that you have set these values as I have specified.
- Uncomment the mmalcam_name vc.ril.camera parameter.
- Uncomment target_dir and change it's associated value to ’/home/pi/Documents/motion’
- Ensure that ffmpeg_output_movies is set to 'off'
- Set stream_localhost to ‘off’
- Set webcontrol_localhost to 'off’
- Set width to ‘640’ and height to ‘480’
- Set locate_motion_mode to ‘preview’
- Set locate_motion_style to ‘redbox’
- Set event_gap to '10'
- Set output_pictures to 'center'
- Set quality to '80'
- Set text_changes to 'on'
Feel free to play around with the configuration parameters to get a feel for what they do. Be careful to keep a record of the parameters you have changed, in case you mess up and need to start again. Remember that you always have a clean copy of the config file at /etc/motion/motion.conf.
Running Motion for the First Time
Now you are finally ready to run Motion for the first time! Use the following command to run Motion with your configuration file:
motion -c ~/.motion/motion.conf
While Motion starts up, key an eye out for any error messages that pop up. Problems can occur if your camera isn't correctly connected or if Motion lacks permissions to create image files.
Note that Motion occasionally fails to start up due to previous Motion processes that have failed to shut down properly and are running in the background. If you suspect this, try running the following:
ps aux | grep motion
sudo kill -9 [pid]
pid refers to the Process ID that you get from the ps aux command.
Once Motion is up and running you'll want to check out the video stream. To do this, you'll need the IP address of the Pi Zero along with the port specified by the stream_port parameter from the Motion config file. Go to the address:
and you should see your video stream in the browser.
You can also access Motion's HTML control panel by changing the port to that specified by the webcontrol_port as specified in the Motion config file. Here you can change configuration options on the fly, stop and start Motion and even take snapshots.
Now you can test the motion detection. Movement in front of the camera should result in a still image being saved to the directory you specified for the target_dir. If this is working then your motion activated security camera is almost ready for use!
Adding Email Alerts
Our next job is to ensure that alert emails get sent from our Pi Zero. As with all things Linux there are many different ways to do this, but I found the following to work without issue.
Installing a Mail Client
For this solution you'll need a throwaway Gmail account, as you are going to specify your Gmail password in a configuration file.
Start by installing the tools you'll be using to send emails:
sudo apt-get install ssmtp
sudo apt-get install mailutils
sudo apt-get install mpack
sudo nano /etc/ssmtp/ssmtp.conf
and ensure that file contains the following configuration parameters, making sure that your Gmail account credentials are in place:
Finally send a test email with an attachment from the target_dir directory:
mpack -s "Test Email" [target_dir/filename] [recipientEmailAddress]
If this mail arrives you are good to go to the next step.
Configuring Motion to send Email
Here you'll need to make a small change to your Motion configuration file.
sudo nano ~/.motion/motion.conf
You'll be updating the on_picture_save parameter. Uncomment it and change it's value as follows (updating the recipientEmailAddress to the email at which you want to receive alerts):
mpack -s "Your Security Camera has detected Motion!" %f [recipientEmailAddress]
What happens here is that Motion will call this command each time a new image snapshot is saved to the target_dir directory. The %f variable contains the full path to the file.
Save the configuration file, restart Motion and voila! You should now be receiving email notifications each time Motion detects a motion event.
Ensuring Motion startups up on Reboot
The easiest way to ensure Motion starts up on reboot is to add it to the rc.local file. This is a simple as adding the following command - assuming that you have specified the configuration file as outlined in this blogpost:
motion -c ~/.motion/motion.conf
Removing old files
Over time there is a danger that your SD card will fill up with old images. Therefore I strongly recommend that you create an automated cronjob to periodically remove all images from the output directory specified in the Motions configuration (the value to the key target_dir).
Evaluating The Result - Did the Security Camera work?
In addition the streaming video works perfectly, making it easy to check the video stream each time I get alerts. By setting port forwarding in my home router I have exposed the live stream to the web and can now view it from my iPhone.
The Camera is meant to run 24/7, and was recently up for 4 weeks without a single problem while myself and my family where on holiday in England. In addition to receiving alerts via email, we used the streaming video on a daily basis to see how the weather was in Oslo (and to check that my brother in law was watering the flowers as agreed).
There are many use cases for this kind of project. It can be used for wildlife watching, pet monitoring or even to tell you when your kids come home from school!
I have two minor problems with the solution, which are both easily resolved:
- The Pi NoIR camera works well in low light, but really needs an IR light source to perform at night. I haven't got around to picking one up yet, but they are easy to get hold of online.
- The camera is mounted inside the house looking outwards.There is a small gap between the lens of the camera and the glass, which allows for reflections to appear when it is dark outside and the living room light is on. This can be resolved by placing some cardboard or tape around the edges of the ZeroView camera mount, which would stop the light pollution hitting the glass right in front of the camera.
A more difficult issue to resolve was that of false positives. The Motion software algorithm for detecting movement is based on the amount of pixels changing from frame to frame. In practice this meant that I received alerts when the neighbours cat paid us a visit, or on partly overcast days when the shadows in the garden quickly moved and changed. Rain running down the window was also an issue.
On some days I received 50 alert emails due to these false positives, which tended to undermine the usefulness of the camera. Motion allows you to tweak the amount of pixels needed to trigger an alert, but then you run the risk of making the camera less effective.
Conclusion and next steps
Over all I was very happy with the result. The camera worked as designed and satisfied our original requirements.
The false positives issue was the only real problem. I therefore decided to find a solution to this!
In my next blog post I show how I solved the problem of false positives by using Image Analysis and Amazon Web Services.
Until then, thanks for reading! If you have put together a similar project, or have any questions about this blog, or find any errors in the code then feel free to tweet me @markawest or post a comment below.
This blog post was originally written here. Please visit it to see all the comments.