Is anyone using Detection Zones for the Doorbell? Whenever I turn mine on, all event recording and alerting stops. Nothing is detected.
With zones off, the doorbell works but then is constantly sending repeat notifications of a package because other movement is triggering the AI to look again.
I can walk in front of it and nothing happens whatsoever. If I turn them off, it will immediately alert like normal.
The doorbell doesn’t have a distance setting and sensitivity down to 2 doesn’t help it from the motion events that are occurring (even though they are pretty far away).
Just confirmed the same as you. There seems to be a few issues when Detection Zone is on.
No Detection Zone: Everything works as expected. I get Person Notification without issues.
With Detection Zone on: I get no notification as everything shows up as motion. When I tap to show the Motion from the Dual Doorbell Live Stream Page, I get an error 05 as shown in this image:
As you can see, at the bottom of the image, I have person notification and then followed by Motion Only. I am moving and standing in front of each motion event. When I turn off the Detection Zone it is working fine.
I have 4 squares turned off. Here is my setting. Note: Mounting it outside tomorrow, so currently it is in my garage. I have masked out the window:
Thanks, I had noticed there were some big problems with detections lately, but hadn’t quite been able to put my finger on what the issue is.
One thing I did notice is that when I block out the entire road and an extra block out square all around it for good measure, it STILL detects all the vehicles on the road.
I also set my sensitivity level to the lowest level and every vehicle is still detected, which wouldn’t normally mean much, but when I used the VDBPro, I would set the detection zone to 3, or sometimes 2 and it wasn’t detecting most vehicles out at the road. So I suspect the Detection sensitivity may not be changing or doing anything so I added a detection zone, and the detection zone is being completely ignored except by the motion tag (the motion tag respects the detection zone, but the AI detections are not respecting it at all).
At least that was my preliminary analysis. Then it recently seemed like I didn’t get notified about some events, but I did still sometimes get notified about some. I just haven’t narrowed everything down yet. We’ll make sure Wyze is alerted to what you are seeing too. Thanks for sharing @Earl.Automation
I should mention I am currently on battery. I haven’t tried it wired yet.
I need to submit logs on this. It’s a bug for sure. Kind of a glaring error in my book but… what do I know? When I get my smart home camera company (Earlz), I suppose I can have something to say.
I need to submit my logs. It’s VERY easy to show the bug as @carverofchoice showed.
I have my doorbell wired for the official record. I see the problem as 2 things:
Detection Zones stops all event recording from occurring. Which then means no notifications. Turning off Detection Zones restores the doorbell to capture events (Smart Detection too) and notify properly.
Secondary issue from this is the sensitivity of the doorbell seems to be ignored. Even set at Level 2, mine is being triggered on cars going by about 35 feet away.
@WyzeJasonJ - Could you comment on this notification behavior I have described above?
I can reproduce it very easily. I just did it 1 more time before submitting this post to confirm it. My logs are based on that.
Turn on Detection Zones… Doorbell stops logging events.
Turn off Detection Zones… Doorbell will constantly tell you about movement in the frame, even with sensitivity set to 2. **This may or may be by design. In my personal example, the tree was blowing a LOT in the video so that would constitute quite a bit of pixel change to the frame.
A Detection Zone would solve the problem but the Doorbell goes nigh nigh when that’s on. I’m wired in my configuration.
