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.
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.
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?
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.
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.
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.
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
Good morning, already someone has found a solution?
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.
I had the same problem. I don't know which of the following really worked.
It finally worked at the end.
I hope this helps.
thanks! followed your steps. it worked
My controllers will not connect either.
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.
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
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.
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.
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.
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?
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!
Google Stadia’s controller limited to alphanumeric only passwords apparently.
https://twitter.com/googlestadia/status/1202971650003615746?s=21