Unfortunately, I don’t experience the issue you are having. As you know, I am on firmware 1.2.7 and running the latest beta app for Android.
In the past when I had issues with streaming and other items, I was doing a lot of research on the issues.
Turns out, replacing the router helped me out emensley. Not saying you need to do that, but may be worth a try.
Though it is massively hard to understand how a different router will make any difference since it is actually still on the network and responding to network request, but simply not communicating with the Wyze servers. I will never the less attach it to the providers WIFI router to see if that makes any notable difference. It will just take time since it’s a state away. I’ll update once I know more.
On a side note. What routers are you others using? I suspect the large majority are the provider routers and not after market ones.
I’m using an old Netgear R6020
I’m pretty close to giving up. I’ve tried 3 different firmware versions, 2 different thermostats and 3 different routers, sometimes dedicated to just the thermostat with a fixed IP address and it still happens. I’ll try one more replacement from Wyze and them I’m moving on. I really want it to work because I can’t find another one that you can set the Differential Temp as high as 3 deg which is a lot more efficient for my radiant heat system. I think the older Ecobee might do it, but not the newer ones…
I agree, it confusing to me as well. But it has to do with how it handles the actual traffic and the efficiency of it.
In the past, my main router would freeze when Live streaming 2 cameras. I then replaced to a different Router system and all of my streaming issues and other issues disappeared. Here is what I went through, note that I am in IT and some of this is a Hobby for me, so I spent time playing and learning. 
Router 1: TPLink P7 Mesh. Had issues and could not cleanly stream one cameras especially when there was a lot of activity going on. Had Thermostat issues with disconnecting. Seemed to coincide with the activity or events being triggered, but cannot confirm this.
Router 2: TPLink X60 Mesh. I could stream up to 4 cameras cleanly. But once the activity picked up around my house things started to freeze. Seemed to coincide with the activity or events being triggered, but cannot confirm this.
Router 3: ASUS ZenWiFi XT8 Mesh. Was able to stream 6+ Cameras at one time no matter the activity around my house. Thermostat and all other Wyze Products finally worked flawlessly. My notifications were coming in faster, no lag in camera streams, Thermostat has not disconnected since. Performance is great. I have a Gigabit connection and when connected via WiFi to the router, I get (on Average) 700 down but only about 280 up. This is an issue with ASUS and the Verizon FiOS network. Remember this is WiFi Connected to the Router, not the speed from the Router to the internet.
Router 4: Wyze Mesh Router. I can never leave well enough alone , But I have to say, this router worked amazingly for me. 3 devices to cover the house. No issues at all with streaming, T-Stat remains connected and even my Satellite Sensors are now back in the location I wanted them with no disconnects at all. Performance is just as good or better than the ASUS. I have a Gigabit connection and when connected via WiFi to the router, I get (on Average) 650 up and down. Remember this is WiFi Connected to the Router, not the speed from the Router to the internet.
Router 5: Wyze Mesh Router Pro: Even better devices. Only need 2 devices to cover my entire house. Everything functions as expected, no disconnects and I even streamed 9 cameras from Wyze Web View without it having issues. Once I was having work done in my garage and streamed that camera for 8+ hours. With this setup I get (on Average) 725 up and down. I have hit 800 before. Remember this is WiFi Connected to the Router, not the speed from the Router to the internet.
In any event, this is my history and I guess you could say I have a problem. 
But I will say, I am not experiencing the issues I was in the past and things just simply work. Knock on wood. 
Here’s what I did to fix the problem and not sure which did it. I have a mesh wireless system, so I ended up turn off roaming on my two stats and locking them on to the closest ones. I don’t think all wireless mesh systems have it, but mine did. I also run beta code and keep it the latest version. I had issues constantly before I did these things and solid since.
Thanks,
Dale
Roaming does play a part as does beamforming on Mesh systems. I turned those off as well.
With Asus I could lock a device to a node, which I did at first, but turned it off as I had better coverage than my TP-Link
What I gather from this is that Wyze is not able to work with modern mesh networks? They should provide a disclaimer if this is true.
JON
I don’t know if the blame can necessarily be placed that way if the devices all worked flawlessly on 3 out of the 5 examples (2 out of 3 brands). He doesn’t have any connectivity issues when he had a good mesh router like the ASUS or Wyze Mesh routers. He only had problems with TPLink. So this indicates that Wyze works fine with Mesh routers in general, but that the problem seems to lie in how some router brands, like TPLink handle their connections in some way. I know that in some cases people have criticized TPLink for having middling throughput performance and dynamic (not dedicated) wireless backhaul. I don’t know if these things contributed to performance issues with IoT, but it is possible. It does stand to reason that since the Wyze devices worked flawlessly on other Mesh systems that there is something being done differently with TPLink that is abnormal to the others where everything worked fine.
I’m on a new Eero mesh system and the thermostat drops the connection every week or so.
What caught my eye about spamoni14 and dalek77’s comment are that they had to turn off the roaming functionality with his mesh system to get it to work. Unless I misunderstood. If that’s correct, then Wyze should be able to note that in the setup instructions.
JON
That is correct. My main issue was with the TP-Link setup. Once I removed those from the mix, everything worked great. Let me clarify, TP-Link Mesh Network (DECO) Devices.
I did not have to turn it off to get it to work, mine is working with it on. I turned it off to try and clear up my streaming issues based on what I was reading.
On my ASUS setup, roaming was on, but did turn off Beamforming as that could cause issues with a lot of devices, other than Wyze.
I have also seen articles where individuals are having issues with Eero. Not sure exactly what that was, but something to note. As I said earlier, switching routers is something to try, but may not be viable for everyone.
You can always buy one, test it, and return if it does not work. If you search, for my posts on my issues, I am sire you will see everything I went through.
I wish that I could explain why I am not experiencing the same issue as you, but I am not.
Just out of curiosity, what is your setup and Provider.
I am not using the Wyze Mesh Router Pro, connected to Verizon FiOS with a Gigabit connection.
I just turned roaming off for those two stats. Didn’t have to turn it off for all devices. I have the decks. Work great though on a 3 story beach cottage.
Curious if it helps. You may want to look at Beamforming as well. But do one change at a time.
I posted about this issue in the new Fix-it-Friday event for those of you still experiencing this:
I am not experiencing this issue, but if you are, consider adding a like to it in that thread above so that Wyze can get an idea of how many people are still being affected by this issue.
@jiverson @Rmac @789bill @james11 and anyone else who is experiencing this still.
Thanks, it’s interesting the comments about TP-Link, because I’ve tried a couple of different ones, but they were both from TP-Link. I think I have an old Netgear one too, I’ll have to see if I can find it.
Yes. Even IF it does end up being that the issue is occurring on some specific routers and not others, maybe Wyze can narrow down what is happening and program a way to make the TStat work with it anyway. Regardless of where the fault lies, often a firmware update or workaround can be implemented to resolve it once the issue is discovered. I am hoping that if this is the most voted Fix-it-Friday issue that enough logs will help them find a commonality or pattern in those who experience the issue and get it resolved. It is definitely strange that some have noticed that the device is showing up okay on the router, but still shows offline. I saw a similar situation in the past where a generic IOT device used something like a ping to the Google servers just to check if it was online or not. If the Ping to Google was successful then the device showed an online status, if it wasn’t, then it showed offline. So when someone blocked all Google IP addresses, suddenly their IoT device said it had no internet, even though it did. They could even control it, but they were locked out of some other things because it THOUGHT it was offline. I wonder if something similar is occurring here. Something is making the TStat THINK it has no internet, even though some of you are seeing that is actually connected to the router with internet. I am not saying it is a ping to Google that is being blocked, but it could be a ping to some other service or something for all I know. It’s hard to know for sure until a Wyze dev looks into the logs and figures out the commonality between those of you having this happen. It will be interesting to hear reports on what they find if this is the most voted on item this month.
Like I said, it’s notactually affecting me, personally, but even so, I like to report things like this for people who are having obvious bugs negatively impact their experience too. 
So here’s hoping we learn what’s going on. 
I was having the same issue, I have reset my newly installed upstairs thermostat 3 times. I have another one downstairs and never ran into this problem. I saw on one of the comments that roku or other devices on the network maybe grabbing the same IP. Once I reserved the ip address on my deco mesh network the problem disappeared. I no longer have my thermostat dropping the connection. I hope this helps.
Pls provide the link to Fix-it-Friday
Thanks,
Bill