You need to link your Stadia Controller to a screen before you can use it to play. In order to play on a TV with Chromecast, a mobile device, or on web with Chrome, you’ll need to use a linking code to link your Stadia Controller wirelessly.
To let your Stadia Controller know which screen you want to play on wirelessly, you’ll need to enter a linking code for that screen. The linking code lets you easily change which screen your controller is linked to. Each screen will have its own unique linking code that will rarely change.
Enter linking codes from left to right, one button at a time. Linking codes are 4-5 characters long and consist of only Up, Down, Left, Right, A, B, X, Y.
Here is a sample of what a linking code looks like. The code for your screen will be different.
Note: If the status light blinks orange, it means the controller can’t connect to Wi-Fi. Open the controller menu in the Stadia app to set up the controller with Wi-Fi. If you need to change the Wi-Fi on your Chromecast, use the Google Home app.
I have the same problem, but then with an TP-LINK archer.
Did you manage to fix your controller issue?
I can connect to my WiFi fine, but can't seem to connect to the Google Services.
I solved my problem:
`The MTU size of my router was setup incorrectly. The default was set to 1500. but the optimal value for my ISP is 1472, therefore the controller could connect to the internet but wasn't able to connect to the google services. ![]()
1492*
How do you check this? Where do you change it?
I'm still not able to link my controller to the Chromecast that came with it. I'm using a Netgear Orbi wireless router. I've tried chromecast on 5Ghz and wired and it makes no difference. I'm able to see all devices connected when looking at my router including the controller. I can ping the controller and chromecast as well and they are on the same network. I'm not able to connect the controller to 2.4ghz band though. I've tried lowering the 5ghz radio strength and hiding the SSID and it still connects at 5ghz. In any event, my controller connects to wireless fine, but will not communicate with Chromecast still. It is very frustrating.
Anyone with a Netgear Orbi able to get this to work?
I'm not sure what happened, but my controller simply won't connect. Let me explain:
I made sure to connect my controller to my Wi-Fi network, as well as my Chromecast Ultra. Then, I entered my linking code with the controller. Well, it started blinking white for a few moments, and then it vibrated and blinked orange for a few moments. After that, it just turned off by itself and wouldn't link. The odd thing is that I didn't have this issue until after I played Stadia on my laptop with a USB cable.
I'm not sure what to do now.
same issue here. yesterday i received the controller, evrrythink works fine. Today i wanted to play, but i can't link my Controller. Controller is connected to my Wifi - its blinking white, i tip in my Code. After this, thr Controller vibrates 2 times, and started to blink white. after few sendonds, it vibrates again automaticly and blinking orange.
I don't know what to do. i reset it, but nothing better. ATM i do not using a Chromecast, only my Smartphone (S10e). When i received my Chromecast, i i will test it again. i hope someone can help me
Can you please tell me where I go to return the controller
May I asked the process to change the controller. Can't find customer service for Stadia unless is through Google itself. Thanks in advance.
This is one of the biggest pains I deal with on Stadia. I have to link my Controller randomly. And there are times when the code just isn’t accepted at all. I have to power cycle the CCU, phone, and controller to get the code recognized, and sometimes I have to go through multiple power cycles.
Linux Pro Tip:
sudo rm -rf /etc
I agree. I have spent the last 30 minutes chatting with Stadia support in an attempt to get my controller reconnected to my Chromecast Ultra. After weeks that it worked fine today none of my two controllers managed to connect. I tried to reset my Ultra, reconnect the controller to the WIFI, etc. but I was still unable to connect to the screen. Eventually I rebooted my router and the Ultra and the controller and Ultra managed to see each other. What a pain. Let's hope that a future enhancement will make it foolproof and easier to achieve.
Hello together,
i`ve a little question/issue and i hope, you can help me.
It happens now every weekend, that the controller isn`t connected to the stadia anymore and i`ve to put in the code once again, because the controller blinks white. After this all is working fine and i can start stadia and so on, also the next day. So only when i don`t use stadia for round about one week, this situation happens. Is this normal and why it happens?
Thanks for your support!!
Best regards
Micha
@Bamberger wrote:Hello together,
i`ve a little question/issue and i hope, you can help me.
It happens now every weekend, that the controller isn`t connected to the stadia anymore and i`ve to put in the code once again, because the controller blinks white. After this all is working fine and i can start stadia and so on, also the next day. So only when i don`t use stadia for round about one week, this situation happens. Is this normal and why it happens?
Thanks for your support!!
Best regards
Micha
Hello,
my issue is solved. Looks like, there was a update or so and now Stadia is starting every time and switches to the right channel on my TV, also when some days are gone. I don`t need to enter the Code once again.
Best regards
Micha
This has been my experience as well to the t. Hopefully the controller issue will be better when it can be paired via Bluetooth or something
@Lilphish did you contact Google support to replace it? I've been waiting since April 29th for a reply email from them regarding my unlinking issues.
I have this exact issue. Did you find any solution?
What type of equipment are you using for your network? Ex. Router, switch, etc.
If you are using a home router, I would start by temporarily disabling any security features such as firewalls, security tampering features such as port blocking software on the router then try to connect the stadia. Also, I would reboot the router, phone and stadia
I've been using it wired and playing in a browser window because it runs more smoothly when I do that. I plug in the controller, it flashes orange for a minute, then turns off. Even plugging it into the wall to charge it, it does that. I have no idea what's happening to it.
I am on Xfinity xFi platform and I want to say it works well until we have xFi Pods installed. Now my controller is having trouble linking to the Chromecast Ultra even though both are on same WiFi network. Is this issue a known issue with xFi Pods interfering with the functionality of the Controller?
If so, what are the workaround to have the controller successfully link and hold the link during the game.
Hello,
I have 2 stadia controllers a chromecast ultra and an applie time capsule running on 5Ghz. For the life of me I cannot get either of the controllers to connect. I have tried rebooting the accesspoint, the chromecast and even my phone, but nothing works. The setup app gives sometimes "Service connection error" or "No internet connection". I have many other devices connected to this network and none of them has any problems. It is only these controllers that give issues. Google, can you please rethink how the controllers are connecting or give me some indication of why a wireless network that works for everything else does not work for the stadia controllers ? I am losing my patience here.
Following up on my scenario where I had experienced issues with pairing the controller on my wifi network. Turns out my home network somehow had two separate wifi routers (one for telephone and one for xFi). Which created conflicting SSID broadcasts, causing some devices to show up on one network and not the other. Ever since we found out our telephony one has deactivated causing our phone line to cease working, we relocated the phoneline to xFi, then returned the telephony router. Ever since, we now have one SSID broadcast (2.4 and 5.0) from one source, allowing all devices to find each other on the same network. this resolves my Stadia controller not finding CCU correctly.
It does work fine on xFI as long there identical SSID for both 2.4 and 5 gHZ if you're using pods, or pair the CCU and Stadia controller to the same SSID to keep them together if you;re not using the Pods.
Hope this helps others. Cheers
Hey guys/gals,
I had huge issues with my Stadia controller not linking wirelessly to PC Chrome at all, neither on my desktop nor on my Chromebook.
The solution was this:
I am using uBlock+uMatrix (like all of you should :-p) and there is some sort of hidden domain that needs to be allowed for uMatrix so that wireless pairing works.
The uMatrix rule is:
stadia.google.com cloudcast-gmsg-prod.googleapis.com * allow
This took me quite a while to figure out because uMatrix did not show "cloudcast-gmsg-prod.googleapis.com" as a 3rd party domain most of the time, even when I tried to do the pairing. Once it showed up I allowed the domain and now pairing works flawlessly all the time.
Hope that helps someone ![]()