Hello everyone,
I'm trying to setup the environment to play stadia and have the best performance. I have Sky WiFi (open fiber 1Gbps) and I play Stadia from Google TV. Due to lag playing stadia with Sky WiFi router I decided to buy a google nest wifi to activate the stadia setting due to prioritize the stadia devices over the network. Now I have best performance while playing but Google Nest WiFi continue disconnecting for 2-3 seconds randomly, often every 5 minutes. This is so frustrating. I read that it is a common Google Nest WiFi problem. What can I do to fix it?
I can't use stadia anymore if I get kicked out every 5 minutes from my network. Should Google Nest WiFi be optimized for stadia?
Thanks @JohnZoidberg for the quick reply!
I actually fixed the problem and I am right now playing Cyberpunk 2077 with super quality and performance.
The problem is fixed by unchecking the "Video conferencing" checkbox from "Preferred activities" in Google WiFi settings. The only checked box is for "Stadia" and now all is working like charm. No more disconnections.
I hope that this can be useful to other users.
Just to say: I can't disable wifi from Sky WiFi router because it is not allowed by the user interface. So I renamed the Sky WiFi router network to "old network", and I gave my network name to Google Nest WiFi nework (I have 25 devices connected). Also, I had some online meetings and the quality was perfect, no lag, no disconnections.
Oooh... now that is interesting. First, I'm really glad you got this solved. I have heard a few recent complaints of issues with the "preferred activities" not working as expected. So, if you can use the "feedback" feature in the Google Home app to report this issue (and how you solved it), that would help the Google engineers gather more evidence and hopefully solve the underlying problem here.
One more note – if you can't disable the WiFi on your Sky router, then do try to make sure it is at least six feet away from the new Nest WiFi Router.
Hello @branco
That shouldn't be happening. Yes, there are some similar reports from Nest WiFi users, but the vast majority of customers don't have issues like that. That said, it can be really hard to diagnose this kind of problem remotely. But, I'll try to make some suggestions. First, have you disabled the WiFi on your Sky WiFi router? Or did you replace it entirely with Nest WiFi? If the old router is still in place, you'll want to turn off its WiFi interface to avoid any possible interference issues.
If you do still have the Sky router in the system, if it's not in a "bridge" mode, you may be dealing with "double NAT". That isn't normally a significant problem, but for Stadia, it can be, since Stadia uses a new transport protocol called "QUIC", which runs over UDP instead of TCP. Some NAT routers may only keep a UDP mapping in place for a few minutes, even if it's still being used. That could cause a disconnection and reconnection periodically. However, if this was the issue, I would have expected you to have a similar problem with the Sky router by itself – it shouldn't be worse with a Nest WiFi router in between.
Lastly, I would make sure you are connecting your gaming device via the most reliable method possible. The Chromecast with Google TV doesn't come with an Ethernet adapter, unfortunately, but you can get one from Google for a relatively low price. It replaces the power supply with a new one that has an Ethernet jack. You can then connect that to your Nest WiFi Router's LAN Ethernet port (either directly, or through a network of one or more inexpensive Ethernet switches if you have a need for more than one wired device). The idea here is to skip the WiFi link entirely, since Ethernet is more reliable in general, and subject to less variation in packet delivery. Your controller will still need to be connected via WiFi, but it should be more tolerant of using WiFi (especially when you get all of the video streaming traffic off of WiFi).
Basically, this all boils down to ensuring your network is as simple and as reliable as possible. Those are the things you can control. The Sky network itself is not something you can (directly) control, though. So, if that's where the problems lie, you'll have more work to do.
Thanks @JohnZoidberg for the quick reply!
I actually fixed the problem and I am right now playing Cyberpunk 2077 with super quality and performance.
The problem is fixed by unchecking the "Video conferencing" checkbox from "Preferred activities" in Google WiFi settings. The only checked box is for "Stadia" and now all is working like charm. No more disconnections.
I hope that this can be useful to other users.
Just to say: I can't disable wifi from Sky WiFi router because it is not allowed by the user interface. So I renamed the Sky WiFi router network to "old network", and I gave my network name to Google Nest WiFi nework (I have 25 devices connected). Also, I had some online meetings and the quality was perfect, no lag, no disconnections.
Oooh... now that is interesting. First, I'm really glad you got this solved. I have heard a few recent complaints of issues with the "preferred activities" not working as expected. So, if you can use the "feedback" feature in the Google Home app to report this issue (and how you solved it), that would help the Google engineers gather more evidence and hopefully solve the underlying problem here.
One more note – if you can't disable the WiFi on your Sky router, then do try to make sure it is at least six feet away from the new Nest WiFi Router.
I pull up again this thread because the disconnection problem has come back. I am thoroughly analyzing the scenarios that cause these disconnections on the devices. The main clue I found is that: when I open the Google Home app and I select "WiFi" I have again disconnections on all devices. I have tried to modify the preferred activities in all ways but sometimes the disconnections continue. I found a new resolution to the problem by setting bridge mode on google nest wifi. Since I have activated the bridge mode I have no more disconnections (but by reactivating the NAT mode they restart). The only thing that happens is that every 2-3 days I had to restart the Google Nest WiFi because I was receiving "wifi without internet connection". Another strange behavior that I notice concerns the speed test: I have a 1Gbps FTTH fiber and via wifi, from all the devices, I always have 400-500Mbps in download and 200-300Mbps in upload. The Google Nest WiFi speed test, on the other hand, always gives me 90Mbps in download and 200-300Mbps in upload. Also, I managed to turn off the wifi of the Sky WiFi Hub, so the only network currently available in the house is that of the Google Nest WiFi.
test speed from google home app on the left, and from browser on the right.
Hello @branco
Sorry for the delay, and I'm sorry to hear you're still having troubles. The NAT vs bridge mode is an interesting clue. But, I'm also interested in why the download speed in the built-in Nest WiFi internet speed test is so much slower than the speed you see from a client. That built-in test is using Google's infrastructure to test against, and this combination of results makes me suspect your internet service provider may be limiting the throughput to Google services for some reason.
Google works with some internet service providers to create a direct link into Google's network to get traffic (things like YouTube and Stadia) off of the ISPs public network links. In some cases, they also place some servers inside the ISPs network as well. This is advantageous for the ISP because all of their public network link traffic costs them money. But, if your ISP doesn't have that integration in place, they may be trying to control how much that traffic is costing them by limiting the total throughput to those services. We saw this once with an ISP in California that was having some financial difficulties. To be clear, I can't say for sure this is the problem, but it's a similar symptom. Some customers were able to prove this was happening by running Stadia through a VPN, which side-stepped the traffic prioritization the ISP was applying.
In any case, at this point, I would recommend reaching out to the Nest WiFi support community here: https://www.googlenestcommunity.com/t5/Nest-Wifi/bd-p/Nest-Wifi where it can be investigated further and potentially escalated through that support system.
Wow months of issues solved by finding this post. Thank you!
Hi everyone,
Since this is an older post, we'll be closing it now. If you still need help after reading through the comments, then please feel free to create a new post.
Best,
James