We have noticed that some users are experiencing offline issues with their Doorbell v2 devices. To better understand and resolve this problem, we need your help in collecting device MAC. If you have time and would like to help us investigate this issue, please DM me the device MAC and the offline timestamp of Doorbell v2.
Your assistance is crucial in helping us address this issue effectively. We appreciate your time and effort in contributing to the improvement of the Doorbell v2.
I will send you my MAC addresses. Not sure about the offline timestamp but I will look for it.
This is a widespread problem judging from the numerous posts and threads here. Some of us are nervous about being stuck with worthless hardware. It would be very helpful if Wyze would put out a statement here acknowledging the issue and explaining what is being done to resolve it and the level of urgency. I realize this post is a start but I feel like we need to hear more from Wyze on this.
On my second doorbell and same problem within 24hrs. I have three properties and within the past two months they all have started having this offline issue. My WiFi is great, gig fiber and every one of my OG cams stay online all the time
Orange blinking ring of death always happens within 12 hours of a factory reset. Nothing I can seem to do about it. Plenty of signal, Even switched to a strictly 2.4 GHz network with its own unique name.
Posting it here because I can’t for the life of me figure out how to DM someone on the support forum.
You can click the user’s name or profile picture to see that person’s user card and then click the MESSAGE button:
I don’t recall if that’s covered in any of the Forum tutorials, but you can get to those by sending a direct message to @discobot. Try a message like “start tutorial” or “display help”.
Chiming in so I can track this post in case there are updates. Shout out to @WyzeJasonJ for being awesome and passing my MAC over. Clearly there’s traction on the issue. They knew my camera went off line before I did.
I’m a software analyst, so I can’t help but over-analyze bugs.
Things I’ve tried:
Putting the camera on a dedicated 2.4 network to rule out issues with seeing the 5.0 network - No Impact I can’t change this but did want to add that I too have AT&T Fiber
Removed the SD card - No Impact
Turned off the new Wide View (forget the actual name) - No Impact
Did not share the camera when I did a factory reset - No Impact (figured it was worth a shot)
Left the Familiar Faces notifications check marks unchecked. - No Impact
I still question the Familiar Faces given the fact that I can still administer the notifications but not the actual saved faces due to not having Cam Unlimited.
I was in the Alpha and Beta testing for the “Familiar Faces” service. I had a handful of people defined so the AI could identify them. Fast forward to moving Familiar Faces from a “free” beta feature to a paid feature only available via Cam Unlimited.
While I lost the option to administer the saved faces via the account tab, I still have the option to administer the notifications with my Cam Plus subscription.
Is there any chance the system still recognizes that Familiar Faces was previously setup and is trying to hit that service but errors out because it’s not a registered service?
I know there are quite a bit of calls to the AI services. Curious if the change to FF threw a wrench in the gears. I’m almost certain this issue started when Friendly Faces moved out of beta and was only made available to Cam Unlimited.Any chance those of you with this issue also played around with Friendly Faces when it was in beta and had saved faces?
Hopefully the logs I sent over this morning help out.
MAC : 80482C311E00
Firmware : 4.51.2.0578
Not sure on timestamps but mine will be ok for about a day max and every morning it is offline again. Using ATT fiber internet but running this one on the 2.4Ghz.
I cannot send a direct message either. I do not want to post my MAC address in a public forum. Can you enable the direct messaging option on my account?
D03F27D28386 has the same issue. Network is solid. The doorbell is the closest to the router of my 3 Waze cams and is the only one experiencing an issue.
MESSAGE button: