At Sensr.net we’re trying to strike a balance between storing everything and storing what makes sense.
A typical camera sends us a few frames per second. Our servers process these images and when we detect motion, we save the related images and organize them into the camera view.
Sometimes things can get out of whack if your camera has a lot of motion. The way to fix this is to adjust the sensitivity of the motion detection algorithm that we use on your camera. You can adjust the sensitivity of the motion detection by changing the setting in the edit page for your camera. (See the screenshot below.)
If you’re getting too many images, say more than a 500 per hour, you should consider lowering the sensitivity of the motion detection. For most cameras a setting in the 3-5 range seems to work well.
We have our limits. While we try to save everything, we do limit cameras to 600 images per hour. This means that if you set the motion sensitivity too high, you’ll blow through your quota of 600 images before the hour is up. In this case you might miss some important motion events. Say you use up all 600 images in the first 10 minutes, then Uncle Henry slips on a banana peel at 20 minutes into the hour, you’ll miss all the fun.
Other options. If you don’t want us to do the motion detection, you can simply configure your camera to send us images when it detects motion. In this case, you’ll want to turn off the Sensr.net Motion Detection option in the edit camera page. If you turn off the motion detection on our side, we’ll simply store all the images your camera sends us, assuming it’s doing the motion detection. We still enforce the 600 images per hour limit, however. So if your camera is sending us a lot of motion when there isn’t really motion (also called a false positive) then you’ll still have trouble catching Uncle Henry’s antics.
The disadvantage of having your camera only send images on motion, is that the Live View of your camera on Sensr.net will be pretty boring. The live view shows you all the images we get from your camera as they arrive. If your camera is only sending images on motion, then the live view won’t show anything most of the time.
The disadvantage of sending a few images per second is that it can use up a lot of your bandwidth. If you have a bunch of cameras at home and they are all constantly sending 2-3 images per second to Sensr.net, then you might be reach the limits of your DSL or cable modem service.
One solution is to combine these approaches. Some cameras let you send images periodically as well as on motion events. In this case you can have your camera send a frame once every 10 seconds or so and send images on motion. This will give you a slow frame rate live view on Sensr.net, but when there is motion, you’ll still capture it. To make this work, you’ll still need to have the Sensr.net motion detection enabled. Most of the images coming in at the 10 second intervals will be dropped, but when there is motion on your camera, the Sensr.net motion detection algorithm should also detect motion and save the images.
To summarize, if you’re getting hundreds of motion events per hour on your camera, you should probably lower the Motion Detection Sensitivity setting on your camera’s edit page. If you’re going over 600 images per hour, then you’re certainly missing events that you might want to catch, and lowering the sensitivity settings can help there as well.