I keep receiving the alert: “Wyze - Oops. Something went wrong. Please try again.” This prevents me from viewing my cameras or event logs. It occurred on October 1, October 17, and again on October 26. Could you help me understand why this keeps happening?
I’m currently using a Pixel 8 Pro running Android 15 with Wyze V3 cameras (activated 02/08/2021), firmware version 4.36.13.0416, and plugin version 3.2.0.14. My network connection is solid with a strong three-bar signal, and all three V3 cams are set to auto-restart every Monday at 10:30 AM CST.
Using the most current Wyze app version 3.2.0.580
To temporarily resolve the issue, I have to:
Open App Info
Force Stop the app
Clear the cache
After these steps, I can access both the live feed and event logs again. Could you please advise on a permanent solution or any potential fixes?
And being a user forum. There are many here that are still willing to help. Have you tried deleting the app. Restarting your phone and then reinstalling the app? I would try that first. Are you using any VPN type service?
Well, I see this. I see it less now than I used to. But still see it once in a while. I’m not even using an Android phone either. I think, you could try this next time.
Pick one of your cameras that is reporting this, and turn it off. No, not in the app. go remove its power. Could give it 15+ seconds or longer to cool down a little, but then power it back up. Check at the phone again. Better? If so, I encourage you to restart your cameras. At least each time this happens. But, some of us have done this to ward off the evil.
We put our Wyze cams on a WiFi smart plug so we can turn them off remotely. I think most of us that put them on a WiFi smart plug, we don’t use a Wyze smart plug. And even better, if you get a WiFi smart plug that allows you to create a schedule so you don’t have to. I restart all of mine at 03:00 am - daily. Yes it still happens, but less than 5% of the frequency before. So setting up an Alexa routine that you can use to turn them off, and back on with a voice a command is cool for that once-in-a-while time you wanna do it. You might want to try just one for starters. But wow, this sure fixed most of my cam issues.
I’m going to chime in here. The Forced Stop has become my best friend. I have been chasing a memory leak in my Samsung s21 ultra for months.
Others in this forum, same phone, have not seen the memory leak.
It has become so common that I found an app"Kill App" on Google Play. It does one thing-- it kills the app. Foreground, background and memory resident.
I am not ready to nuke my phone or get a new phone (my preference) until I figure out what is causing this. The app has a little widget that I have next to the wyze app. I hit that widget a few times a day. Makes the wyze app basically flawless.
If you are hitting the “force stop” more than once a year— something else is going on.
If you have “Developer Options” watch the Wyze app over a period of hours. If you see it continuing to grow memory then you may be seeing the memory leak I am seeing.
As a data point other beta testers, same phone, are seeing the wyze app using 200 - 300 mBytes. My phone can see up to 1gBytes. A hit on “Kill App” reduces this to 200 - 300mBytes.
Keep us informed what you see.
p. s. To the wyze devs. I am sure I don’t know all the ramifications but the “kill app” takes 2 seconds. I would gladly give up 2 seconds when the wyze app opens to restart everything.
I am having this problem “Oops! Something went wrong…” but only on my Macbook Pro Google Chrome. I can log into my Wyze Access My Cams flawlessly with Safari. My app does not have this odd behavior. If I only go to My Account, there is no issue, but if I try to Access My Cams, the first thing I get is “Oops”. If I then click Cameras, it goes right to them, because I am logged in. Still, it is an aggravating step to have to go through this extra step. This started yesterday, Oct. 26, 2024 for me. I have cleared cache in Samsung S22 Ultra phone and Google Chrome on Macbook Pro. Anybody have a solution? Is this a Wyze problem or a Google Chrome issue?
I had to reread your post a few times to understand the flow of events.
Since safari works and chrome does not I’m leaning towards chrome.
Here’s why.
When you go to wyze.com and click on “my account” you are still at wyze.com.
When you click on “Access my Wyze cameras” you are redirected to “my. wyze.com”. Then you get the “oops message”.
It is my opinion that there is a breakdown in this process. When wyze.com redirects to my.wyze.com
I belive it is passing some info to the next site using a protocol called auth2. This tells the new site that you have been authenticated. The fact that after you get the oops message you are able to see your cameras tells me there must be a fallback to auth2 otherwise you would have to re-login.
What can you do. This one is tough.
If this just started as you posted, and you made no updates to Apps, then you might wait a few days and see if it clears. Google has metrics that may or may not see this.
You may need to change your default browser. I am not IOS conversant so I will leave this to others.
I think @ronl4625 is right. It has to do something with Google. I am on a Mac and I have no issues using Safari. Chrome has hard time logging me in into my.wyze.com. I don’t get the Oops!.. but I get login failed.
Thankfully my default browser is Safari and I don’t use Chrome much. I only use it for handful of sites that are not optimized for Safari.
I give credit where credit is due Also, don’t forget that there is a long standing bad blood between Google and Apple. I am even surprised that Apple gives you an option to set Chrome as default browser on a Mac. But then we all know how that went for Microsoft when they had Explorer monopolly.
I understand it’s a forum. Before posting this issue online, I submitted it to Wyze Support on October 17th under ticket #4113676, and I’m still waiting for a response.
I shared it here to inform the whole community in case anyone else is experiencing the same issues.
Perfect. In your original post it wasn’t mentioned that Support had been contacted so I wanted to make sure you were directed there. If you don’t hear back soon you may have to contact them again and mention the previous ticket number and say you’re looking for an update. Thanks!
browser to cut down on tracking.
Also, don’t forget that there is a long standing bad blood between Google and Apple. I am even surprised that Apple gives you an option to set Chrome as default browser on a Mac. But then we all know how that went for Microsoft when they had Explorer monopolly.