![]() ![]() In summary, I’ve had the Motion Compensation enabled for over a week, and I’m still getting the same type of false alarm. In general, lighting going from light to darkness is triggering the camera. There’s always a second camera alarm file, associated with either the first or second of two motion sensitive lights turning off. The first file usually contains a video of that someone who tripped both the light and camera. I was hoping it applied to my situation, where I always get two alarms and associated files, whenever the motion sensitive lights located in my backyard turns on whenever someone passes by. When Sarah Zhang said that the Motion Compensation function prevents false alarms caused by “light changes”. playing with alarm settings and light levels), but merely under normal operation, observing the number and types of files that gets stored in my Alarm Path folder. However, I’ve not done any systematic testing (i.e. Never the less, I’ll still need to find a path forward.īarry Jan 5, 2011, 1:32:00 far, I’ve not seen any significant improvements in the level of false alarms from my FI8918W with the Motion Compensation turned on. Need to know if this is truly a FOSCAM vice my issue. Would appreciate if someone can confirm above, or provide recommended solution. Don’t want to do factory rest just for this. Don’t have a 08W to check see.Īlthough a minor problem, its annoying when moving the cams around, and having the cam located in the patio with video file names saying it’s from the driveway cam. So, FOSCAM has 50% of the set record path function working correctly.Īlso noticed that this problem does not exist with my FI8904W. The video files saved in the “Set Record Path” is okay, and reflects the latest Alias name change. ![]() Updated to latest (re this forum subject) firmware and web versions, but problem still exist. Can’t seem to change the associated Alias label for the files in this folder. ![]() I’ve tired all kinds of resubmits with no luck. THIS IS MY PROBLEM: The files in the “Set Alarm Path” folder gets locked into the initially set or first submitted “Alias” name Granted, if FOSCAM has a bug, then I still have a problem. Either, I have a problem or FOSCAM has a firmware bug for the FI8918W file-labeling names created and stored in the “Set Alarm Path”. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |