Greater Control Over Detection Zone Shape

If they implement the ability to add multiple DZ’s, say 5, then it would solve @Wyz.Guy’s issue too. The area that WyzeGuy wants covered can be done with 3 simple rectangular DZ’s.

The picture I added above isn’t really similar to the problem I want to solve. I just snagged that off the Web to illustrate the concept of splitting the visible area into lots of configurable sectors.

A simpler solution that would probably work for me would be to have 5 configurable zones, but I’d need those zones to be configured as “Don’t detect motion here” rather than the current implementation of “Only detect motion here”. I’d still prefer the ‘lots of tiny configurable sectors’ method mentioned above, though.

Wyze needs to incorporate masking ability into future software/app upgrades. This is pretty basic functionality and much easier to code then motion tracking. Essential for outdoor camera mounts as motion from the wind and other sources constantly sets off the motion tracking and tagging.

1 Like

having the issue on my iOS too. hope it can be resolved soon.

Yes! User definable shapes to select or deselect! Many times, a scalable, rotatable triangle would work. I’m not complaining at all. It’s great to have what we have, in this price point!

Aaah, yeah, that is a caveman solution but the same as masking.

I have the same problem on my iOS as well. I’d love it if it were smaller. I’d get less notifications at night if it were smaller due to headlights.

1 Like

Also in favor of implementation of a more asymmetrical adjustment of detection zones +1

Good idea there. Separate zones for day and night mode perhaps.

I’m glad to see that I’m not the only one desiring more control and flexibility over the shape of the detection zone. it looks as if this has been desired for quite a while. There are some great suggestions in the comments, and I hope one or more are enacted soon. Having the ability to set a polygon, or being able to set sensitivity in various zones for alerts would be helpful. I also liked the suggestion of recognition of shapes, although that’s somewhat less important to me than safety and security. In addition to security, I bought the cam (and will be adding more) so that I could identify the local birds and see the deer and other creatures visiting my yard.

I have a high traffic house across the street, but want to see my mailbox, driveway and front yard. Because of the way the house is built, my camera is on an angle, so it’s difficult to set the detection zone to cover those areas without including high traffic areas across the street. I wouldn’t mind including their house/property for security/safety, in case they had issues, since we’re friendly, but don’t need to be alerted every time someone pulls in/out or goes from the house to garage/man cave. Being able to set that as a lower priority or non-report zone (but still having it on cam in case I needed to share w/them or police) would be fine with me. I hope we hear about developments relating to this soon.

1 Like

Update:
So I’ve installed BlueStacks (thanks to @ElectroStrong for the suggestion) to address the issue of streaming on my laptop. Since BlueStacks is Android, I went ahead and adjusted the detection zone there and was able to make it smaller. That solved my problem. BlueStacks may be a solution for those who are using iOS and not able to reduce the size of the DZ as small as desired.

Agreed, the grid or pixel paint method is the most flexible IMO. The Manything cam app has a good implementation of this and works excellent for blocking trees etc. This method should also reduce traffic on Wyze servers for all the false alert uploads to cloud etc. example…

This issue has been flagged as a bug because (a) it did not exist in previous iterations, (b) it does not exist on Android systems, and ( c) it is exclusive to the iOS community of users.

That said, we (iOS customers) have been continuously told to “post it to the “Wish List””. I’ve had it being treated like an unwanted step-child.

Telling us to post it on the “wish list” is detrimental to customer morale. A previous poster went so far as to install an Android app on their desktop in order to have granular control. I tried it yesterday but it refused my login, seems Androids don’t accept as long a password as iPhones do. After changing my password and logging in, the app wanted to be paired with my cams instead of just picking up the existing account — so I uninstalled it — but the fact of being willing to go to that extreme is a testament to the frustration we are experiencing.

I have liked the Wyze cams and am very appreciative of the price point. However, that only goes so far. Once support becomes dismissive, and the customer has convinced themselves of the utility of the concept, pricing becomes less of an issue — but — customer retention becomes a greater one.

Wyze has an entire segment of their customer base — everyone on iPhones — ticked off. If Wyze as a company is prepared and happy to loose them, then the tactics that have been expressed by their personnel, i.e., “Put it on the wish list”, “Sorry for the ‘frustration’ but we’re not updating the app and have no plans to do so”, etc., are just dandy. I believe the term is “suckers”.

I’m a new Wyze customer, but I have serious doubts that I will be a long term one with this sort of treatment; and there is no way on this earth I will try any other Wyze products when they treat people like this.

Some might say, ‘Well others are no better’. That may well be, but they don’t all purport to be either, nor are all of their systems as locked-in as these. I guess you could say Wyze has escorted me from excited to confused to concerned to annoyed to upset to angry.

I know I can’t keep customers that way.

— 7

You may have encountered someone who didn’t quite understand the specific issue. People requested similar things before the bug ever existed — they wanted detection smaller than the current Android limit, for example. That’s probably why someone referred you to the wishlist. But you’re right that the current minimum size on iOS is a bug, not a wishlist item. It’s something they’re already aware of. I’m not sure if it will be out with the next app update, but it has been flagged at least.

Thank you for bringing this up. I sent a reminder to the support team that bugs and troubleshooting should not be sent to the Wishlist and we apologize for that experience.

4 Likes

I have replaced all my externally facing Wyze cameras with Blink gen 1. They were on sale last year when Blink was moving inventory for their Gen 2 device. Very granular area control for only about $30 more per camera.

They have lost me as a customer over this lack of functionality. I have a bunch of Wyze cameras gathering dust.

How many, there are many people who would buy them if you are willing to part with them

1 Like

Honesty the current implementation and range limit would be a bug. What i was referring to was a new product feature , with a grid/pixel based zone implementation. I’m sure if the small time ManyThing app and others can do it , certainly Wyze could as well.

1 Like

If it had been one person from Wyze, or even two, I would say, “Yes, you’re correct”; but it wasn’t. I’m glad WG is reaching out to the support team.

I guess I don’t really understand what you’re saying. I’m not sure if the average customer service person at Wyze would be aware that this is a bug that has been flagged. If they’re not aware of that, it sounds more like a feature request than a bug. It’s only when you dig deeper and realize that it didn’t used to behave that way, and that it behaves different on Android, that it becomes clear that it is indeed a bug, and not just a limitation. Without that knowledge, they’d probably direct you here, as they’ve been trained to do.