How to Configure MotionEye, Part 1
I would like to thank everyone that has taken the time and opportunity to view and support my other MotionEye post, the amount of views it has received is outstanding!
As part of this post I shall be outlining some of the settings I have to mimic, as closely as possible a real CCTV system. If you aren’t already aware I use my MotionEye setup to film the front of my house, I do this for a number of reasons… as I purchased a new car I’d quite like to keep an eye on it and because I live in quite a publicly accessible place it seemed the right thing to do, to keep myself and neighbours safe from any wrong doing! When it comes to MotionEyeOs the opportunities and limits are almost endless.
Firstly, I am going to introduce you to Text Overlay and Video Streaming. Below you can see the two setting tabs you are presented with to configure both these key areas of MotionEye.
The Text Overlay area allows you to select the data and text you want to be visible on your stream, in my case I have selected the name of the camera and the timestamp – the timestamp is crucial for any CCTV system as it provides a date and a time for any evidence if necessary.
Secondly, the Video Streaming tab includes the frame rate you wish to achieve. For this I have set 20 as a respectable aim for my Raspberry Pi to reach, you can set it at whatever you like however if you try reach the maximum such as 30 it may decrease the stability of the Raspberry Pi and use more CPU and memory. You could lower this if you don’t intend to stream the video anywhere or altogether turn it off. This is the same for quality, I just set this to 100% as I’d like to reach it’s full potential for any video that is streamed to my mobile device. Motion optimisation should try to keep the picture as fluid as possible.
I’ve set my streaming port to 8081, you can set this to anything but 80, I recommend something in the higher port numbers such as http (which loads the Motioneye page) loads on port 80, therefore 8080/8081 are easy to remember!
Thirdly, the key point of recording. You wish to save anything that is seen on the camera, it is a wise idea if you ever need it for future reference. Below, I have not modified the file name from it’s default of Year Month Day – Hour Minute Second. The same as streaming, I have set the quality to 100% and have a recording mode of “Continuous Recording”. To note, Continuous recording with a maximum movie length of 0 seconds will allow the video to record endlessly and it’s random at what point the video will be split into another file. I tend to find the files on the Raspberry Pi have lasted a good 7-24hours before splitting into a separate file. I would NOT recommend this if you are using micro-sd storage unless you have a card in excess of 32Gb for MotionEyeOS. The reason for this is, unless you plan to set it to preserve movie’s longer than a day then you will fill your micro-sd card up in a matter of possibly two days for a 16Gb card, about 4-5 days for a 32Gb card.
Lastly, the motion detection below is linked to the motion triggered recording mode, this is configured as you please and allows you to record for things like light intensity changes and the amount of frames to capture of the motion.
For more information on MotionEye, it is available from the developer here.