cancel
Showing results for 
Search instead for 
Did you mean: 
Cocoon
Community Member

Controller can't connect to Wi-Fi

Jump to Best Response
Anyone else having problems connecting your Stadia controller to Wi-Fi? The Stadia App will recognize my Controller, so when tryining to connect to Wi-Fi my Controller will vibrate. I confirm and then I will try to connect to my Wi-Fi, enter the password, but it won't connect. I already tried to - restart my phone - reset the Stadia Controller - restart my router - reset to router - reinstall the Stadia App I am running out of ideas what else to try. I didn't have any issues setting up the Chromecast.
14 Kudos
Best Response
Cocoon
Community Member

It seems that the problem was related to my Moto X Force smartphone, which was not able to connect the controller to my Wi-Fi. I have now tested it with a Pixel 3a XL and it did work on the first try.

View Best Response in original post

2 Kudos
ChrisFromGoogle
Community Specialist
Community Specialist

Hi Coriano, sorry to hear this is happening. If you have already exhausted the troubleshooting tips found on our Help Center, the next step would be to contact our Support Team. Let us know if you have any success or need additional assistance.

View Best Response in original post

1 Kudo
41 Replies
Lilly
Community Member
yes I am having the exact same problem
4 Kudos
metalshark
Founder
Founder

Same here.

Chromecast Ultra connects to WiFi fine, controller does not. Have WiFi 6 routers (AX, certified WiFi 6), logs show it authenticating with the wrong PSK. 100% using the right one. 63 character long PSK with two apostrophes in it. Where do I report the controller bug?

3 Kudos
charles-h-white
Community Member
@GraceFromGoogle Mine won't connect either. The app sees both controllers. One shows charging, the other does not. As I step through the process, it says leveling up... Then states unable to connect to controller. Please tell me this is not a 2.4 GHz vs 5 GHz issue. I am running on a OnePlus phone and Google Mesh WiFi. Google Mesh WiFi supports both frequencies but the OnePlus will only connect to 5GHz. Do I have to have my phone on 2.4 GHz? Did Google send us 2.4 GHz? Unreal ..
0 Kudos
WarriorPKT
Community Member

I'm having the exact same issue. Strangely, I was able to connected it to the guest version of my network, but when I attempted to sync with the chromecast, I'm able to input and connect based on the pattern on the screen and the controller vibrates. I then get the same linking pattern to connect the controller, but it fails.

Ironically, I'm using Google WiFi.  So much for ecosystem compatibility.

3 Kudos
Exition
Community Member

Hey,

I've the same problem the Chromecast and all other devices like TV(Sony, Samsung) mobiles(IPhone, Huawei) are working fine.  

I've tested

Asus RT-AC86U Router - 2,4&5Ghz Wifi.

The problem here is the WPA 2 AES,  WPA AES/WPA AES+TKIP encryption. If you have a "open system"  the controller can connect. 

Fritz Powerline 1240E WLAN - WPA 2 is not working 

I assume it s a firmware problem. 

2 Kudos
Himgi
Community Member

Hi. do you have any ideas about to fix this? i am not able to connect also. i have a Asus RP AC66U as AP to my Asus DSL-AC 87VG Router. my encryption is WPA2 AES. i can connect to my Network. but i cant Connect to the Goole service. and after a couple of minutes i lose the connection and cant connect again.

0 Kudos
GeneralDisarayn
Community Member
Same problem for me.. Chromecast connected using the same password but it will not connect to the controller. I am positive the password is the same but it will not connect
1 Kudo
Himgi
Community Member

Is no Support member in here? Seems that the Controller - connection Problem is a big Thing... 2 days ago i was able to call a Support on Phone. They dont know what to do. So... I cant connect to Google Service ore Chrome Cast. And knowbody can help. No answer from Support... Google, that s*ck's

1 Kudo
Himgi
Community Member

Good morning, already someone has found a solution?

0 Kudos
Bork
Community Member
Same here. I have tried both 2.4GHz and 5GHz networks and I copypasted the passwords. I even deleted those networks from my phone and pasted the passwords to make sure my phone could use them to connect to the network. My phone was able to but not my controller. I have tried many times, restarted the controller and did the factory reset holding both Capture and Assistant for 6 seconds while turned on.
1 Kudo
Bork
Community Member
I just tried with my 2nd controller. It managed to lose its connection to my phone while trying to connect to the WiFi. The other controller (the one that came with the Founder's Edition) also did that from time to time. I have my controllers right next to my phone. Perhaps my phone isn't good with Bluetooth? How can I confirm this? I created a guest 2GHz WiFi (no password), the controller didn't lose its connection with the phone but it couldn't connect to it either. I'm running out of ideas... How can I return my controllers?
1 Kudo
Bork
Community Member

Something was wrong with my phone I guess. I was able to setup the WiFi on both controllers using an iPhone. I pasted the password from the same place, so it wasn't a password issue. 

If you have access to another phone, try this. 

Tags (3)
0 Kudos
JI
Founder
Founder

I had the same problem. I don't know which of the following really worked.

  • I erased the profile of the Chrome Cast Ultra from Google Home
  • Disconnect wired connection to Chrome Ultra and connected with wiress on Google Home app then made the profile again
  • I rebooted router, Chrome Cast Ultra, phone which I was using Google Home to connect
  • I connect the controller with the same wifi which Chrome Cast Ultra was connected

It finally worked at the end. 

I hope this helps.

2 Kudos
dkarnati
Community Member

thanks! followed your steps. it worked

0 Kudos
Studio
Community Member

My controllers will not connect either.

1 Kudo
Exition
Community Member

Hey,

I think I've found a solution. My smartphone is a Honor 10 (Huawei). I recognized that the chromecast configuration was a little bit slow after I've tried several WiFi configurations ... I grabbed my wife's Iphone (SE) and configured Chromecast with Google Home App and it worked much faster... So I've installed Stadia and tried to connect the controller with my WiFi -> It worked. :rolling_on_the_floor_laughing: 

Nothing has changed only the smartphone manufacturer! o.0 

I hope it's not a coincidence so please test it because it's a working solution for me 

0 Kudos
CRYO
Stadia Player
Stadia Player
I can connect to the router at 2G but it refuses to find the 5G on the same router yet all phones and tablets can connect to both frequencies?
0 Kudos
NRRID
Stadia Player
Stadia Player
 
0 Kudos
2beerS
Community Member
Same here... I tried: - resetting everything concerning wifi - 3 routers all 2.4 and 5 ghz - every wifi security setting apart from wpa enterprise - two different phones (iphone 11 and 7) What a pitty, I was so happy to see Stadia has arrived today so that I can play on TV. Hope this is a high priority problem at googles tech support!
0 Kudos
2beerS
Community Member

On further research i found out, that my stadia controller indeed connects to wifi but it gets an ip adress outside my configuration (192.168.0.xx <- controller VS. 192.168.178.xx <- my network). After changing my ip adress range accordingly the controller connected to wifi. Now I was able to connect to my wifi but had no internet connection according to the controller. Enabling the "device can enable forwarded ports itself" (<- sorry non native speaker here) I was able to connect the controller to the internet but not google services.

The last step was to enable port forwarding tcp from 44700 to 44899 and udp 44700 to 44899.

I am now able to play!

 

I hope this is a workaround for some of you. I know changing your home network ip range is not really a comfortable thing, especially with complex DCHP exception and static ips. But I was not able to give my controller the correct range.

 

best regards and sorry for my broken English.

0 Kudos
zelenev
Community Member

I have the same problem. Controller would not connect to WiFi on Cisco Access Points protected with WPA2/WPA3. I have dozens of enterprise, consumer and IoT devices, including Google and Nest products that connect to Cisco APs just fine.
Controller does connect to an OpenWRT AP with WPA3 and same password, so there is definitely some kind of a bug with controller firmware.

 

Is there a way to enable WiFi association/authentication logs on controller? The controller must be running a buggy WPA Supplicant or buggy 802.11 driver.

1 Kudo
zelenev
Community Member

Just a follow up, in case someone missed my response in the other thread. I got Stadia Controller to connect to my SSID by disabling 802.11v on SSID - evidently Stadia Controller has some kind of compatibility issues with this standard.

0 Kudos
Northlight
Community Member

I have the same issue however I always thought it was related to my Chromecast been connected directly to the ethernet and not the wifi.

Is are you connected using a ethernet wire to your Chromecast?

I collect Kudos for living.
0 Kudos
linex7
Community Member
I can get my controller to connect to a wifi hotspot on my phone, but I can't connect to my wifi router at all. I've tried with all wireless security disabled. I've tried different wireless modes. Nothing seems to have any effect. I've ran the Stadia app for setup on multiple phones. Factory reset the controller multiple times. Nothing. Google's lack of error codes for this makes the problem extremely hard to pin down.
1 Kudo
metalshark
Founder
Founder
Chromecast is fine works great. Controller though won’t connect to WiFi. Everything else is fine with WiFi. 63 character PSK with two apostrophes. Logs says the controller doesn’t authenticate properly (e.g. has a buggy supplicant). What we really want to know is how do we get actual support. Feedback on the app and this community site does not work and the Google Support line say to wait to hear for updates. How on earth do we get an update on a controller that won’t connect in the first place?
0 Kudos
Bork
Community Member

Hi @metalshark , sorry you're one of us...

After the nth time (probably 20th), I managed to get a controller to connect. Not the other though. I opened a support case.

I suggest contacting Stadia Support, their chat is open 24/7. Good luck and keep us posted!

0 Kudos
metalshark
Founder
Founder
Support on Twitter are now responding. Did some diagnosis together. Length isn't an issue so: abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz1234567890 works. Full stops (periods) aren't an issue so: full.stop works. Apostrophes are an issue (at least with the iOS app) so: one'apostrophe does not work. It's reported - have asked for a public ticket number/bug report/road map, if I receive one I'll post it here. From doing all of these tests this morning, for me, multiple attempts make no difference neither does manually selecting WPA, WPA TKIP, WPA2, WPA2 TKIP or WPA3 (this is a WPA2/3 network, but was asked to try WPA TKIP by support).
0 Kudos
metalshark
Founder
Founder
Worth noting that spaces in PSKs are also not an issue.
0 Kudos
metalshark
Founder
Founder

Google Stadia’s controller limited to alphanumeric only passwords apparently.
https://twitter.com/googlestadia/status/1202971650003615746?s=21

1 Kudo