Wyze Doorbell Cam v2 disconnects and stops working after a few days without a factory reset

@sharon.osha, I appreciate your taking the time to share what you can. That’s helpful, and I like that you’re looking out for your dad and that you were able to find someone at AT&T who was willing to work with you and get you a solution!

@ssummerlin, AT&T came through the neighborhood to dig and run fiber earlier this year (and may have cut the Cox cable and temporarily disabled some neighbors’ Internet service in the process…oops!), and now they’re apparently telling DSL customers (which has worked well for me, too) that our service may end about mid-December unless we switch. I think they want to retire the copper wire.

Good news for us. Thanks for the update.

1 Like

I hope it is. Maybe they want to recycle/sell the copper. :wink:

1 Like

Thanks for researching and testing some workarounds.

But most importantly, why doesn’t this issue happen with some of the other Wyze devices? I have several cam v2, a cam v3 (with garage controller), a cam OG, and a doorbell v1. Out of all of these devices, the doorbell v2 is the only device in my fleet that experiences this issue!

I’m very close to switching back to the doorbell v1. While it has way less features, it’s much more reliable and actually stays online!

Welcome to the Forum, @mermex! :wave:

I wish I had an answer to your question. I haven’t experienced the “offline” issues with my own Video Doorbell v2 that some other users have reported, but since any two users are unlikely to have exactly the same network setup, my best guess is that the problem is probably rooted in an individual’s home network and the Wi-Fi availability at a given doorbell’s location. I haven’t seen it specifically mentioned with regard to Video Doorbell v2, but I know that some Forum users have had connectivity issues with Cam v4 unless/until they disable WPA3 on their routers. I don’t know if that could be a factor here or not, but at this point I’m just speculating and trying to think about what else might be going on, because trying to troubleshoot someone’s issue without knowing all the details and potential variables in another individual’s network environment is a real challenge. :man_shrugging: