Have you cleared your Cache from within the App? Clearing the Cache, the logging out of the App, restarting the device, and then logging back in seemed to help me in the past.
In addition, rebooting the router has helped me out. Last Resort though for me.
Clear cache - May help on first connection after clear but after that back to stuck.
Logout/in - Made no difference
The only thing that reliably unsticks the authenticate 3/3 is if there is motion in the camera view.
I believe they have a task scheduler issue to where the authenticate task only gets run when there is motion. Or alternatively the task scheduler is stuck waiting for motion.
I have 2 wired doorbells. 2 different houses. 2 different wifi’s. Same issues of getting stuck on 3/3 on both. Different phones Android or iOS same.
Typical troubleshooting techniques and such don’t work.
However… leaving each camera in night mode works perfectly except that it’s Black and white.
This has been a solid work around for me. Putting the cameras in auto just goes back to getting stuck at 3/3.
Been having at times that it will go through the 1-3 process and repeat the process and either load or say failure to connect and clicking retry happens to connect back instantly. Clearing cache, rebooting device/power cycling or rebooting router does not resolve this. Seems to last about a day and then starts doing this again. I’ll submit logs as soon as it happens again.
seems to be fine so far - noticed once or twice, maybe after re-opening the app and going to view doorbell, it went back to SD - I changed it back to HD and so far it seems to be holding.
Frankly, no one should be testing beta anything unless they are prepared for some serious setbacks, especially when you consider the actual releases are pretty much just late stage betas, so these are often early betas with minimal pre-testing.
Anyway, I definitely agree there should be a way to rollback. I recall during a hardware beta test, they did have a way to rollback, so it’s not impossible. Make it only available in the beta apps to avoid problems with the release users. It should not be that difficult.
It’s not a beta issue. The official release is what broke things. The reason some of us even tried the beta is to try to help repair the damage caused by the faulty non-beta releases.
Completely agree though that no one should be griping if a beta breaks something.
Oh, confused then, thought this was the db beta thread. But ya, when it comes to Wyze, especially after testing beta hardware, I’ve come to the conclusion everything Wyze is essentially a beta.
Thanks for this workaround (Turning Night Vision Mode ON, instead of letting it default to AUTO).
Settings
Advanced
Night Vision Mode
ON
I tried setting the Sensitivity to 100% and that did not work consistently.
These past few firmwares are still of problems where I now don’t get any recordings or notifications and it fails to connect half the time every day and flipping the breaker everyday to fix it is becoming very annoying that I’m at the point where I’m just going to replace this with another ring device. I really didn’t mind this at all but not having a working video doorbell is a pain.