I only want the contiguous selection below to be saved. I don’t want to monitor tree limbs or bushes so I deselect those squares and save accordingly. I don’t worry about the 3 squares above my normal selection.
I try to deselect one or two squares and it doesn’t save these changes.
On one V2, I cannot fix this issue.
On another V2, I went through the same process but when I saved, I turned off the detection zone. When I turned the detection zone back on, It worked as you would expect.
Unfortunately, this V2 has issues constantly.
Any idea on how to resolve this issue on my faulty V2? My other V2s and V3s have no such issue.
I saw something similar to this once, though I was having the opposite issue (getting random black out zones instead of random detection zones). I did some testing and found it was trying to force a minimum number of one of the detection types, and if I didn’t select enough squares to be that type, then it was randomly selecting some for me.
Just for testing’s sake, will you open up Everything in the red zone as the detection zone and black out everything else and see if it now saves correctly:
I suspect that this will make it save correctly, and since you said you mostly don’t want it watching random foliage, this detection zone, if it works, would still mostly do what you intended it to do.
I still think they should fix this glitching behavior, and I am glad to see someone else reporting it. Will you please also post your App version, your firmware version and a log related to this so that I can potentially pass it on to someone since now both you and I have seen something similar related to the detection zones, so I now know it’s not an isolated incident. Thanks for the report. Please let me know if it still adds random detection squares if you test adding the detection zone I drew out. This will help me narrow down how similar it is to something I have been looking into.
Interesting that it still has an errant square
So there is merit to the theory about it wanting to try to have a minimum number of detection squares since it stopped the majority of them from repopulating, but that’s not the full story or we wouldn’t still have an errant square showing up, because your new attempt actually covered more than the previous total squares it forced, and it still added a new random one. Very weird. Will you submit a log for this and post the log number in here?
Same problem with just one camera out of 4. Very annoying, events on moving trees. Wyze tech. not helpful at all and do not reply to log data sent. We all get what we pay for. Time to move on from Wyze I think.
Having the same issue and it’s new - wasn’t happening this morning. I had just setup a new Cam v3 with detection zone and it worked great. Then today’s firmware update happened and now my detection zone won’t save. I get a random square or two that are on in the far left but that’s it. Power cycled, rebooted phone, etc… Next is deleting the camera and connecting it again, if I have to.
I have the same issue. I just installed two Cam v3’s yesterday. Motion detection zone was working fine on both cameras. Then I updated the firmware. Now the zone just gives me two random squares on the top-left and bottom-left side of the screen whenever exit and I go back in to check it. There is obviously a major issue here. How do we revert back to the old firmware?? This is BS!
If people believe they’re saving their detection zones according to their input, when in reality what it’s actually saving is 98% of the zone being blocked out, I’d say that’s a bit more than “mildly inconvenient” there Mister…
I am also experiencing the same issue after the firmwarm update to 4.36.11.7071. Does anyone know if a hard reset of the cam would work? Not really sure if I want to go through the trouble of setting the cam up all over again if it doesn’t help.
.
