Simple request, Motion Detection Zone height

wyze-cam
#1

The Motion Detection Zone height currently can’t be smaller than about half the screen height or 0.5. Not sure why this is the case, but I would like to have it smaller, at least 1/4 or .25, or smaller.

This should be a simple fix.

Thanks,

John

1 Like
#2

+1

#3

In the iOS app, I can set it to 1/3 of the screen height. Which phone OS are you using?

#4

Split the difference. In my @#$%^&* iPhone 6S, it’s 40% - yes I measured it.
But yes, it would be nice to get less than that…

#5

Looks like this is a bug that occurs to a specific device type and model. The bug occurs in iPhone SE which is similar to iPhone 5s, a 4 inch screen. Video is set to HD.

Good thing I’m also using a 2nd device Google Nexus 5X and this bug does not occur. I can make the motion detection area as small as 1/10 or 0.1 height.

I wonder if anyone else with iPhone SE or 5s can reproduce this bug?

Thanks,

… and Thanks to the founders of this company, these cams awesome!

John

 

#6

K6CCC, can you share your device type and model?

#7

As I said it’s a @#$%^&* iPhone 6S
I hate this phone!

#8

I would like to see all four corners to be independent so we are not constrained to either a box or a rectangle, for my main camera location a trapezoid will work best

1 Like
#9

I concur. I have multiple V2 cams and an iphone 6s. I tried to create a detection zone on the lower portion of the screen, but was unable to create one small enough to get rid of all the unnecessary notifications I’m receiving. I could not get the top of the boundary box to go lower than about 1/3 of the way from the bottom. As flacousa62 mentioned, I’d prefer to create a trapezoid, but I’ll deal with a rectangular shape.

FWIW, I love my 6S :wink:

#10

Trapezoid would be nice, even better polygons and multiple zones :slight_smile: The compute is likely local as oppose to the cloud, so it might not have enough hardware resource to do it.

At the very least though wyze should fix this bug that appears to be an iOS bug only and not on Android. Should be an easy bug fix.

 

#11

Good to know the detection box can be made smaller in Android! I can only make the box 1/3rd height on my iPhone 7 Plus, and need it just a bit lower to avoid picking up all the cars driving by on the street. I’ll have to use my old Android phone just to set motion detection box. Hope they can fix the iOS app to be able to set any size box.

1 Like
#12

I was about to create a new topic concerning this issue, but noticed that it had already been discussed several months ago. It’s still frustrating for me, so I’ll resurrect this thread. Perhaps worthy of roadmap inclusion? Below is what my new topic would have been.

Ref. the attached screenshot … moments ago I received a motion alert because a car, driving through our cul-de-sac, cast a shadow on the sidewalk in front of our driveway. The same thing happens frequently when the neighborhood children ride their bikes on the sidewalk.

If I could shrink (reduce height of) the zone to what is illustrated by the yellow rectangle I’ve drawn, then I’d only receive alerts when one of our cars pulled into or out of the driveway, which is the objective. Note that I’m using an iPad Pro 9.7". Thanks.

#13

We can set our detection zone(s) as small as we want (square/rectangular) using the iPad 4 iOS 12.1 or iPhone 5

73’

Tuna

1 Like
#14

Wish I could say the same for my iPad Pro 9.7" (2016 model) running iOS 12.1.3. I can set the width of the square/rectangle to anything I want. However, I can’t set its height to anything less (shorter) than what is shown in my screenshot above (cyan rectangle).

#15

Thank you!
This solved my problem.
I was primarily using my iPhone and I could not get the zone height low enough.
I used my iPad mini and now the detection zone is as small as I want it.

#16

I noticed this morning that the rectangle sizing problem has been marked as Solved. This is definitely not the case on my iPad Pro 9.7. I cannot shrink the height of the rectangle to anything shorter than what I’ve shared in the screenshot above. Soooo … definitely not solved for me.