Common settings for Alerts and SD Card Record on Event


#1

As I understand it, currently, detection zone and sensitivity settings used for Alerts are not shared with SD Event Recording.

Whatever settings are used for Alerts should also be used for SD card Record on Event


Where can I find “record on event”?
#2

Here is the current status:

V1 & V2: Record on event will be affected by the motion detection zone but NOT by motion sensitivity.

Pan: Record on event will NOT be affected by either the motion detection zone or motion sensitivity.

Coming in V2.2, it will change so Record on event will be affected by both the motion detection zone and motion sensitivity.


#3

Great information. Are you saying only a V2.2 camera will do this and it’s not a firmware update?


#4

That’s Wyze app v2.2 (not a new camera version). There would be an associated firmware update that goes with it to make it work.


#5

That’s even better news! I kind of thought it would be a firmware upgrade but just wanted to make sure.

Thanks


#6

What about motion tagging? Will it ignore motion based on the user settings? If not, it will still be a mystery to visibly know when the slider is catching motion you want to catch.


#7

I just looked into this and motion tagging is not related to motion sensitivity. Thanks for asking! :slight_smile:


#8

I’d like it to record events to the sd card, show up as events, send notifications, but not send to cloud.

Cloud on/off solves this


#9

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.


#10

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.


#11

Just to help consolidate the confirmed knowledge base:

[edit: added]

~2/26/19

~3/1/19


#12

Thanks, peepeep!

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.


#13

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 @peepeep analysis 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.


#14

Thanks for your feedback! I’ll share it with the team, OverWatch. :slight_smile:


#15

Hey, new app version, so a little inside baseball:

Made the same analysis with identical settings and scene details as here - except with

Motion detection settings | Sensitivity - 100

(vs 50)

The untabled results:

6 cloud clips | 4 SD events

over 2 hrs.

Didn’t really expect any improvement, because firmware bug reportedly caught:


#16

Hey @OverWatch, waddaya think?

Start a topic, Confirmed by Developers, centrally listing confirmed items (in comments) as they are revealed?

If “peepeep, brilliant!”, you should do it, cuz you got the chops and stellar rep. :slight_smile:


#17

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.


#18

I have current Android version at 4.94.28

vs 4.94.29 with maybe the fix. Yeah?


#19

Yup! I think that a period was omitted with the message I was given before and that the version would be 4.9.4.29. I sent a message over to the dev team requesting more information and a confirmation.


#20

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?