Application will not connect out of home network

My three cameras just decided to start doing this with the latest application update.

When I am on an IO device that is connected to any one of my configured home networks, the application connects to the cameras fine. I can switch between any one of several networks I have configured on the same router. Same experience, they connect right away in HD.
When I am on cellular 5G or on another network from another source, every camera hangs at “Getting video data” forever. Sometimes it will connect then show one shot and never update. Time stamp shows no movement.
This also occurs if I i have device A connected to my home network (regardless again of which one, cameras stay on their own configured network) with the Wyze app open and viewing a camera.It works fine. If I then connect device B to the personal hotspot of device A, I get the same Getting video Data error on device B while device A is just fine. Once I take device B off of the hotsopt and connect it back to a home network. it works great.
This mode of operation is not conducive to watching the cameras when I’m not home… which is the point of cameras.

I’m using an Asus router with several networks configured. It doesn’t matter what network the cameras are on or the device, as long as they are all on something configured on the router they are fine.


1 Like

I think I can explain your second issue (hotspot setup). It’s probably due to routing (or lack thereof) in Device A (is it an Android smartphone?).

You say you have multiple networks behind your Asus. To explain what’s going on, I’ll assign them arbitrary network numbers. Say,,
You connect Device A, via WiFi, to one of those networks, and it obtains an IP address from the Asus DHCP server. Let’s say Device A gets Your various cameras are on any/all of the Asus subnets. Perhaps one of them is at The Wyze app running in Device A (at is able to communicate with the camera at thanks to routing that is being performed in the Asus. It knows how to route packets between the 10.0.1.x subnet and the 10.0.2.x subnet (and all the other networks that you have configured on the Asus.

Now, you activate the hotspot in Device A and connect Device B to the hotspot. I don’t know the make/model of Device A, so can’t be certain of how it handles hotspots, but I’m familiar with the hotspot in iOS. An iPhone would create a new, independent LAN for devices that connect to the hotspot. I’ve done this with my iPhone, and know that it sets up a tiny wireless network with a dedicated DHCP server that leases addresses to hotspot-connected devices. That network is typically (Using CIDR notation, it’s a Any devices that connect to the hotspot will be assigned an address in the range (Dot-1 is the address of the iPhone on the hotspot’s network, and dot-15 is the broadcast address for the subnet).

For the purposes of this example, let’s assume that your Device B were connected to such a hotspot subnet. It might get assigned the first IP in the scope of the hotspot DHCP server:

You can now probably see where this is headed. In order for Device B to connect to the Wyzecam at, packets have to get routed correctly. Perhaps Device A has the smarts to recognize that is accessible via the Asus, and knows to route packets from off to the Asus, which will route them to the Wyzecam’s network. But even if it did, there’s no reverse path defined. Packets originating from the Wyzecam addressed to Device B at will never get there. The Asus router has no knowledge of the subnet. So it will route such packets off to your ISP through its WAN interface. If your ISP’s gateway router is performing correctly, it should drop these packets, since the destination address 172… is specified for use in private networks and is not routable on the public internet. (Search for RFC1918 if you are interested in such details).

There’s another possible explanation for why your hotspot setup doesn’t work as you expect, It has to do with how Wyze ‘discovers’ the network location of cameras. Too complicated to discuss here, but you might look in your Asus router to see if there is a feature named NAT looparound or loopback or redirect. If you find such an option, and it’s OFF, turn it ON and see if that helps.

1 Like

I’m having the same issue. I can connect to my cameras fine behind my local network (i.e. through wifi), but once I move to a mobile network (LTE) on my newer iPhone, the app logs into the camera fine, but hangs on ‘getting video data’. I submitted a ticket to WYZE support and it sounds like this might be a broader issue relative to the update, so I’m hoping they fix it soon. For now my service only works locally behind my local router.

Any news on this issue. I have same problem. Honestly it’s upsetting because this just started happening.

I’m at a loss and disappointed too. I was considering moving to the outdoor cams but if they can’t fix a major connection issue with many users related to an app update. I don’t know.

-Gabe Kopp

Chat person told me to plug and unplug camera. Thanks but I am 1800 miles away. You get what you pay for…

1 Like

Someone once said something to the effect of “When you don’t get what you want, you get a learning experience.”

And the follow up line was, “Well, I’m TIRED of LEARNING!