Motion tagging and event recording to the SD card are not on the same sensitivity as for notifications. I find this to be not intuitive and causing a lot of WTH responses. There seems to be a missing link where sensitivity actually starts triggering a notification. For example, if motion tagging (green box) were to identify every motion recognizable and a red box identified motions that trigger notification, users would be able to fine tune the sensitivity and could visually see what should trig…

So that means motion tagging will always ‘tag’ all motion? This means my #roadmap for turning the motion tagging box from green to red will still give users instant visibility of the effects of the slider instead of getting to test it every 5 minutes. Right now, if I move the slider, I can only hope the new setting will notify me when someone is walking in front of the camera instead of a squirrel. If the setting isn’t right, you have to wait 5 minutes to test a new setting. There is a better way.

Hmmm I always thought they were. Seems like another disconnect that doesn’t make sense. As a user, given options to change settings, I think I am customizing my set up only to find that some settings are fixed by default. Very confusing.

You’re welcome! Thank you for your patience. Here’s the information verified by the dev team that I received:
V1 & V2: Record on event will be affected by motion detection zone but NOT by motion sensitivity.
Pan: Record on event will NOT be affected by either motion detection zone or motion sensitivity.
If you have an inconsistency between microSD card recording and event recording, please check the detection settings. If that doesn’t fix the problem, please send us a firmware log through the…

I will give all of your feedback to the team. I know that the motion tagging is a hardware feature so I’m not sure exactly how much control we have over it (since I’m not a dev) but I’ll make sure the team sees this.

The sensitivity setting would be pushed down to the firmware (hardware code) in order for the hardware to know when to send the notifications to the cloud and when to record events to the SD card. I’m not opposed to having the SD event recording being set at 100 and the Notification sensitivity being user slide controlled, but that just doesn’t seem to be the case as @peepeepanalysis pointed out. Whatever it is set at, isn’t intuitive and causes confusion. Setting them all the same would at least end some confusion. The next issue is giving the user visual feedback at where the sensitivity slide bar starts picking up motion.

Via Gwendolyn:
I’ll send you an official message and close your ticket shortly. But here’s the information! Apparently your help allowed us to find the bug and I hear that it’s fixed in version 4.94.29. So when you get that firmware, please test it and let us know how it goes.
Was gonna wait until new firmware was released and tested before posting this, but now not sure how long that will be, so here it is, fwiw.

I’m noticing that the version number that is available is slightly lower than the one I was given where the fix is present. I’ll check in on this to see if this is because the fix isn’t actually out yet or if the fix didn’t work.

You know, what gets me is how few users are actually diligent enough to be aware of this problem. If the light is on, it must be working?
You’re killing me. In 2 hours you find a 33% failure rate in events getting recorded. What’s up with that?