Has there been a fix for this? using xfinity and doorbell v2 had been disconnecting. AT&T haven’t.
We released a firmware to beta today that we believe will fix this issue, should fully release soon if it tests well.
2 Likes
We bought a V2 doorbell a coupld of months ago and just installed it last Saturday. There were multiple updates and it worked great- beautifully for four hours. And then…it went offf line. With only two attempts Saturday night, we got it back on line. Then Sunday, it went offline again. I had to call wyze for help after the 4th attempt. This time we documented it, took out the SD card and reset the power at the circuit breaker. And finally, it read the QR code and worked for another 24 hours. Monday, offline again. Pushed reset which is the easiest part, because getting it to read the QR code takes at least 10 minutes. Reset power once, and around the 5th try…it worked again. For another 8? Hours? And then today, we discovered it was offline, again…possibly since late Monday? Today is Wednesday. After 35 minutes of resetting the power, and trying desperately to get the camera to read the QR code…at a minimum of 10 minutes each attempt…it never did agree to go back on line. I rage quit trying for the evening. We have 5 other wyze devices…cameras. in just 4 days, this wyze v2 doorbell has failed more than it has succeeded, well beyond any other wyze device we have. It looks like there are many problems with this doorbell. Its about to go to the trash…soooo frustrating. Looking forward to some help here. Thanks
I would look at your router, its seems that the majority of the problems seem have been AT&T routers or companies that combine the 2.4 and 5 radios into a single SSID. The version 2 doorbells apparently don’t like that. I have placed a dedicated 2.4 router behind my AT&T router and not a single disconnect in over three weeks. It’s something to do with this likely. I’ve seen at least five other users fix it by going dedicated 2.4
Hi - we have just one router with three boosters. This is the sixth wyze product we have in our home. Each device ranges from 10 ft to 50ft from the router. The wyze V2 doorbell, once installed, worked beautifully for four hours. And that’s the one time it worked consistently. The router is not AT&T, its owned by Xfinity and that is our service. All of our wyze products use 2.4, none of them use 5.0. One other camera needs to be reset about twice a month but I have gotten used to that and wyze support has been unable to fix it. I have had wyze cameras for over 5 years and none of them have ever failed to this degree right out of the box. And the fact that it takes a minimum of 12 minutes for it to scan the QR code is very odd. I read other people talking about the wyze doorbell V2 and i am not sure what solution I can use. I cannot move the doorbell closer to the router or the router closer to the doorbell. I have tested the amps for the doorbell and they are in the correct range. The signal is 3/3 bars at the doorbell. And the fact that the doorbell worked beautifully for four hours demonstrates the installation went well. But then, something clearly happened. Its a complete mystery. Thank you so much for suggestions! I am looking forward to any advice to be had in this situation.
1 Like
I have same issue.
Dedicated 2.4 ghz.
Cannot connect to Wifi even though it was able to from January to about a few weeks ago, probably after update.
Now cannot update to latest if I cannot connect!?
Lost connection 4 times in 3 days since firmware update. Won’t reconnect. Doorbell v2 - upgraded wiring, recommended transformer power, and 15ft from latest Xfinity router on combined 2.4 & 5ghz ssid.
Log 1558184
MAC D03F27B6FE08
Firmware 4.51.2.0578
Ironically, I updated firmware on pan cam v3, and it fixed connection problem, and on doorbell v2 it made it worse. They used to quit at the same time, now just the doorbell, so some progress.
Same problem. att fiber. Lightening fast internet. Wyze doorbell v2 worked perfect for 6 months. Then started disconnecting. Didn’t change a thing. Router is close to camera. Excellent signal. I have to reset my breaker once or twice every 24 hours to keep this camera online. Sometimes it will work for a couple of days and i think it may have been fixed then while im at work, camera goes off line. Its incredibly frustrating. Its not a hardware issue. Wyze sent me a replacement and the same thig is happening. Wyze pushed out a few software updates and it seems to resolve it for 2 days, then boom, blinking oraange light. So it seems like this is not a rare problem. It’s a software issue and Wyze needs to fix. Im about to get rid of all my wyze products. This is not happening to any othery wyze product. Only the doorbell. Why ??? Please Wyze fix this once and for all.
I have the experimental firmware, 4.51.2.0897 (Thank you, Jason) and it’s better, but still goes offline once or twice a week and requires a restart to reconnect.
how do i get the experimental firmware for the doorbell?
I don’t have the answer to that, because I don’t think that version was released publicly; however, a later version, 4.51.2.0950, was released for beta testing last week. You can check Wyze’s Web site for details about being a beta tester.
Apparently it is, and I didn’t get stuck and still have notifications.
I’ve been running a separate router for a couple weeks now with flawless results. I’m hesitant to disconnect my old dedicated 2.4 router since it has been working so well. Has anyone tried the new firmware update 4.51.2.1041….is it working?
I’m still on 4.51.2.0578 and have been there for only about a week and a half. I postponed that one for a long time because I didn’t want to install something that was going to break notifications, and I finally made the leap recently because I was having an unrelated (I think) issue with the doorbell and figured I wasn’t going to make things much worse by updating since Wyze was offering a warranty replacement anyway.
As with previous firmware updates, I intend to watch the Forum for a week or so to see what others report before I try the update myself, but I also haven’t been experiencing the particular connectivity issue described in this topic. 