The Sensitivity setting alone is not going to eliminate the movement of tree leaves. You didn’t mention setting the Detection Zone by blocking out rectangles so I’m assuming you have not done so. Unless your delivery people are flying up to your front door, there should be no reason to leave areas at the height of tree leaves open within your Detection Zone.
I hear you, fine tuning settings are an option with most but my cam is at the back door of a condo that faces an alley way with a lot of trees about 10 feet away. To make things worse the trees are aspens. Aspen leaves shake alot when there is even the slightest wind.
There was a mention today in the Fix-it Friday thread. Unfortunately it is not good news:
My VDBv1 is on .060 as well, but it has not been affected by the 3 of 3 load stall. It is still a mystery as to how\why some units are affected and some are not. My only theory would be some obscure differences in local network settings\architecture or differences in chipsets used between manufacturing lots of the doorbell. I believe the latter is more probable. Regardless, the issue seems to be related to the cam pulling the settings from the server for the Night Vision. This theory is based on the repeated posts that show toggling the NV settings or locking it into NV will allow it to load.
My VDBv1 Detection Zone was affected on the introduction of FW .042 in March. I found that the detection zone does work… it just 45° out of phase with the image. I fixed this by mapping my DZ blocks on paper aligned with the image, then clearing them and reproducing the same block count with the paper rotated 45° counterclockwise. It took a lot of time and physical testing moving around in front of the cam, but I was able to dial it in.
Both of these issues began with release .042 in March… which is very interesting since that release had the following updates:
Fixed a video rotation issue in Wyze Home Monitoring
Fixed a bug that prevented night vision changes
The constant motion event notifications (especially when it is windy) can be fixed: Subscribe to CamPlus, enable AI Event Recording and Notifications, disable Motion Notifications, filter out Motion Events.
I have been having this trouble ever since I got the door bell but is somewhat resolved when left in night vision mode but sometimes the playback of the video in night vision mode during the day is blown out, so I am currently downloading the beta software for the door bell and will see how that works. Will update.
Is a new doorbell likely to fix this? All of my Wyze system is pretty solid except this doorbell which has been completely unreliable since April of this year.
I have considered the Doorbell Pro, but can’t stand that fisheye view. I really like the view the regular Wyze doorbell gives me and considered it a superior product to the Ring Doorbell I installed for my mom, until everything went south this April.
After the firmware update borked my doorbell I figured that I just had to wait it out and Wyze will push out a fix. Now 6 months later …
Go to your account on your app, then select about and you will see Beta. Once you click that, it will let you select what you want. I just selected the doorbell. After, open your doorbell and it will do a firmware update. Mine has been fine since!
So a quick update on at least my situation. The beta firmware seems to have solved all problems. So great.
Still astonished at how terrible Wyze’s communication is. I mean this clearly isn’t as bad as when they were hacked an all of our info was possibly shared with hackers and Wyze STILL hasn’t addressed it with their customers as far as I know.
I personally have about 24 Wyze cameras (a mix of v3, tilt and pan, and outdoor cams) a scale, a bunch of door sensors, like 12 lights, 4-5 socket adapters, two doorbell cameras, three door locks… lots of other peripherals; clearly I am a major Wyze fanboy. Yet the absolute silence when it comes to stuff like this is disturbing.
Oh well, it looks like perhaps the beta firmware has fixed things.
I am patiently waiting for this beta firmware to become production firmware!
Until the beta becomes production, I will stick with version 220.127.116.114
Thanks to all the beta testers, I really appreciate your diligence !
My replacement Video Doorbell V1 arrived with 18.104.22.1684 (and is working great).
It wants to go to 22.214.171.1243 still (like it did when I installed it).
Will it go directly to this “to be released” new firmware (126.96.36.1994), or will I have to walk it through
188.8.131.523 to get to 184.108.40.2064?
Looks like you have to go through 220.127.116.113 before you can apply 18.104.22.1684.
After I applied 22.214.171.1243 it seemed to connect fine (no 3 of 3).
It then showed 126.96.36.1994 was available, which I proceeded to apply (takes a while to update).
I am on the current video doorbell firmware now, and it seems to work great!
Thanks to the Wyze software engineer(s) that fixed this problem.
I would love see the behind the scenes code patch that fixed this.
Some people never had a problem, while others were plagued with “3 of 3”!
Yeah, the 3 of 3 problem seems to have been corrected, but the camera’s sensing abilities are still spotty. I had a delivery today that I received NO notifications about nor was the event recorded. Yeah, I know…”You get what you pay for”
So I’m not the only one. Notifications are somewhat better but not 100%. Detection zones still a mess, wind blows, a leaf moves and movement detected, Amazon guy drops off a package and it’s ignored.not reliable at all. It’s been relegated to side gate for a while, simply not reliable to be used at front entrance. Waste of money.