Can some comment on my problem?
I have too many alert triggered by heavy snowing. It is like over a few hundred times per hour so that my ISP has shutdown my email account (SMPT outgoing).
Help !
Snow causing false trigger
Moderator: Staff
3 posts
• Page 1 of 1
-
Semper Vaporo - Posts: 331
- Joined: Sat Oct 09, 2010 11:51 am
Re: Snow causing false trigger
There are several things you can try to reduce the number of alarms issued.
1. Edit the rule "Look for:" section... Check the "Ignore objects smaller than:" checkbox and set the number of pixels to some size that is bigger than the snowflakes but not so big as to miss an otherwise important object in the scene. This is somewhat problematic in that the software cannot tell a difference in size between a snowflake near the camera and an elephant dancing on the hood of your car 50 yards away.
2. In the 3rd step of a rule create/edit ("That are:"), alter the area where motion is to be detected... maybe you can eliminate places where the snowflakes are easily seen close to the camera. Lighting might dictate where these areas are. Maybe where there is a light background the snowflake will not be so easily seen whereas dark backgrounds make them detectable, so create an area for motion detection only over light areas. You can draw quite complicated areas to include only those areas or to exclude those areas, but you can only draw one area. It initially has only 4 corners, but if you click on a side and drag you can create a new "corner" and create all kinds of oddball shapes. (RIght-click over a point to get a context menu that has a 'Delete' entry to remove a point.) I am not sure it is a good idea to create lots of corners for an area, as that may slow the software having to wade through the scene to remove the parts not in the area, but I know it works because I have created areas that skirt a bush and a tree that shake in the wind and a street area where there is a lot of car traffic, but keep two sections of my property where I can detect the mailman and meter readers to know when they come (and other people that are not necessarily welcome).
3. Instead of looking for motion in "areas", change the "Moving objects that are:" setting to "Crossing a boundary" to look for an object to cross a line and set the line to be vertical, or parallel to the general direction the snowflakes are moving. There would be less chance of a snowflake crossing the line and thus being detected as motion. You can adjust the position of the "Boundary" (or "line") by dragging the whole line from the center of it, or click and drag the ends of the line to change the length or orientation. If you just click the line without moving it, you can change it to detect only things crossing the line in either one direction or the other, or crossing the line in either direction (repetitive clicking cycles through the three options).
May have to make a combination of these suggestions. I have been through this several times, eliminating false alerts due to rain running down the window the camera is behind and shadows from trees and bushes moving in the wind and find I have to alter the settings a couple of times per year based on the position of the sun casting shadows of trees and such. The vertical line "Crossing a boundary" worked well to reduce false alerts from water running down the window, but have not missed people and animals coming up on my porch.
1. Edit the rule "Look for:" section... Check the "Ignore objects smaller than:" checkbox and set the number of pixels to some size that is bigger than the snowflakes but not so big as to miss an otherwise important object in the scene. This is somewhat problematic in that the software cannot tell a difference in size between a snowflake near the camera and an elephant dancing on the hood of your car 50 yards away.
2. In the 3rd step of a rule create/edit ("That are:"), alter the area where motion is to be detected... maybe you can eliminate places where the snowflakes are easily seen close to the camera. Lighting might dictate where these areas are. Maybe where there is a light background the snowflake will not be so easily seen whereas dark backgrounds make them detectable, so create an area for motion detection only over light areas. You can draw quite complicated areas to include only those areas or to exclude those areas, but you can only draw one area. It initially has only 4 corners, but if you click on a side and drag you can create a new "corner" and create all kinds of oddball shapes. (RIght-click over a point to get a context menu that has a 'Delete' entry to remove a point.) I am not sure it is a good idea to create lots of corners for an area, as that may slow the software having to wade through the scene to remove the parts not in the area, but I know it works because I have created areas that skirt a bush and a tree that shake in the wind and a street area where there is a lot of car traffic, but keep two sections of my property where I can detect the mailman and meter readers to know when they come (and other people that are not necessarily welcome).
3. Instead of looking for motion in "areas", change the "Moving objects that are:" setting to "Crossing a boundary" to look for an object to cross a line and set the line to be vertical, or parallel to the general direction the snowflakes are moving. There would be less chance of a snowflake crossing the line and thus being detected as motion. You can adjust the position of the "Boundary" (or "line") by dragging the whole line from the center of it, or click and drag the ends of the line to change the length or orientation. If you just click the line without moving it, you can change it to detect only things crossing the line in either one direction or the other, or crossing the line in either direction (repetitive clicking cycles through the three options).
May have to make a combination of these suggestions. I have been through this several times, eliminating false alerts due to rain running down the window the camera is behind and shadows from trees and bushes moving in the wind and find I have to alter the settings a couple of times per year based on the position of the sun casting shadows of trees and such. The vertical line "Crossing a boundary" worked well to reduce false alerts from water running down the window, but have not missed people and animals coming up on my porch.
Semper Vaporo,
-
pcmac - Posts: 51
- Joined: Sat Feb 11, 2012 12:28 pm
Re: Snow causing false trigger
similar problem :
I notice the slightest wind sets off cam recording ,for my rule of anyone coming through my front window sliding door
to upload video clips that matches this rule could be expensive to an FTP site
I notice the slightest wind sets off cam recording ,for my rule of anyone coming through my front window sliding door
to upload video clips that matches this rule could be expensive to an FTP site