I wonder if that is related to this known app bug they are working on:
It’s not happening to everyone, but it is happening. I wonder if it is affecting the webview too. They don’t list that though, and I thought the webview used Amazon Kinesis instead of WebRTC/TUTK, etc.
I will say that I’m not having issues streaming though, so I don’t know what the difference is.
@WyzeSeth Whatever you guys did over the last couple of days seems to have fixed the issue. All cameras are now connecting consistently via the web portal. Thank you!
I must say compared to Google updates on my Nest app to Google Home your Wyze updates and AMA have been very very helpful.
I appreciate how you try to keep us informed whereas with Google Nest cams we have been significantly ignored for the past 3+ years.
Yes there are challenges with rollouts and available resourcing but you continue to move in good directions with very cost effective products & services for us.
Thank you.
Mine has been working great until about 2 or 3 days ago, now I’m back to having to manually refresh or reconnect constantly again.
Even during the time that it was working well, I still couldn’t view my two cams at the same time. It worked well with the main camera I want to view, but it would be nice to view whatever camera(s) I want…
Hi,
I’m having the same issues.
My cameras (V3, V4, and Pan, 9 total) are working fine, most of the time.
But on the Web View, i’m randomly getting the “Device Offline” msg. I can access the cam on my application, so I’m not sure what is the problem there, but it has nothing to do with the power supply, the network quality, or anything in my house as the camera feed is accessible from the application.
I’m using Chrome.
I have also been having the “Device Offline” error for the past 2 or more weeks.
OG and Microsoft Edge.
I tried to open the Web View on Firefox, I’m getting better results so far. No “device offline” since almost 24h.
To all my fellow wyze users who I’ve loved before … just kidding. This was also happening to me and I followed the AI bots advice of connecting using incognito window and gasp it worked!
I am still going to be observing it for next few days to see if it sustains, but so far so good.
For general info I am using Chrome on a Macbook Air M1.
RD
OPREA… Portal sign in rejected…
“… # HTTP Status 400 – Bad Request …”
Had been OK for Months… Webt bad in last couple days.
Doorbell 2 audio isn’t enabled for webview. When the mouse hovers over the audio symbol, a “coming soon!” information bubble is displayed. It’s been coming soon for over a year. Of all my cameras, the doorbell audio is most important given it’s the front door. Has this feature still planned? Or should I give up hope?
I have the same problem. The cameras on the computer say lost connection, but when I go to the app on my phone they are connected. The website server is a 99.99 a year joke! Wyze won’t do anything about it because your hooked for a year with no refunds!
I had these problems repeatedly and noticed that certain cameras were more likely to be affected than others, even though they seemed fine in the app. I then tried to map the Wi-Fi coverage using the NetSpot app and discovered that the problematic cameras were in an area with poor Wi-Fi coverage.
Take a look at this map generated by the tool and edited by me to show the approximate location of the cameras:
Cameras 1, 2, and 4 were generally “Web Connection Failed”. * Cameras 3 and 5 had images displayed more frequently than the previous ones mentioned
Cameras 6 and 7 worked mostly fine even overnight
After adding some nodes to my network via MESH and even using a CPL Wi-Fi extension, I managed to get cameras 1, 2, 3, and 5 to behave the same way as cameras 6 and 7. Camera 4 is for winter use and I should be deactivating it now in the spring.
I’m not saying that everyone has this type of problem, but it’s a hint at a solution, because I thought I had good coverage, but the quality was preventing the cameras from working properly in my case.
Another interesting aspect: before there seemed to be a difference in results between different browsers, so that for me the only one that worked best was DuckDuckGo and Edge never worked, although Wyze officially recommends Chrome. After these changes, Chrome, Edge and DuckDuckGo show practically the same behavior.
Finally, I should point out that all of these changes were made last fall and were approved during the winter.
Excellent. I have Netspot. I will give this a try as I have several cams with challenges… on my XB7 with pods mesh network from Rogers with Shaw ISP.
