cancel
Showing results for 
Search instead for 
Did you mean: 
Gchancey2
Stadia Player
Stadia Player

Trouble adding TV to Stadia

I’ve been playing Stadia on my laptop and Backbone for awhile now and recently purchased a Chromecast Ultra that came with another controller so that I can play on my tv. 

I’ve followed the prompts in setting up the Chromecast and successfully linked my stadia controller but it then takes me to this screen:

 

86694C30-3DB9-456A-81E7-3CEF84A6785A.jpeg

 I then go to my Stadia mobile app, tap on my avatar but my tv is not listed. 

If I turn off the controller I get this scene:

9C1C23CF-0F6A-47D4-ABE7-1131E0911EDD.jpeg

 I’m guessing I would like to click “A” and add account but when I turn the controller back on and link it it takes me back to the 1st screen telling me to add tv via the app.

Is there some kind of work around? What should I do?

I appreciate any and all tips or recommendations in this matter. 

 

1 Kudo
2 Replies
codekiln
Stadia Player
Stadia Player

I have observed the same behavior this morning @Gchancey2.

In my case, my iPhone 7 (iOS 15.1) + Google Home + Stadia App + CCU + Stadia Controller (CCU & Stadia via Stadia Premiere Edition shipped last February) were working earlier this morning, but the network connection was slow, so I reset the CCU over wifi after talking to Comcast XFinity technicians; after that, I can't get Stadia to work with CCU, and my images match those in your post. Here are some steps I took while debugging the issue. I'm sorry to say that like you, I am stuck; none of these solved the issue for me.

  1. iPhone 7 (iOS 15.1) Settings > Stadia > Make sure "Local Network" is enabled (it already was for me)
  2. iPhone 7 (iOS 15.1) Settings > Google Home > Make sure "Local Network" is enabled (it already was for me)
  3. Checked for updates to Google Home & Stadia apps; didn't find any updates. Presumably, have the latest versions.
  4. I used Google Home on my iPhone (iOS 15.1) to update the CCU firmware to >= 1.56.275994
  5. Successfully streamed from phone YouTube app to CCU - connectivity between iPhone, Google Home and CCU is working just fine
  6. Google Home > [select CCU > Ambient Mode > Stadia Controller linking code > Show (this was already checked, but I toggled it off and on just to make sure)
  7. I enrolled in Google Home > [select CCU] > Device Information > "Preview program", because I thought it might give me access to a bug fix related to this - no change.
  8. Restarted iPhone
  9. Did a "Hard Reset" of Stadia Controller - https://support.google.com/stadia/answer/9584135#zippy=%2Cprevent-your-stadia-controller-from-linkin... 
  10. I tried to re-add the controller in the Stadia app, it said no controllers found (my controller was not shown, even though it was formerly working with the app before I reset my CCU)
  11. Did a "Factory Reset" of Stadia Controller (same link)
    1. Google - Set up your Stadia Controller 
    2. Did successfully re-add the controller in the Stadia app and connected the Stadia Controller to my wifi (the same wifi as CCU and iPhone 7)
    3. Saw the same "Use your phone to add an account" screen shown in your first image. When I click on my avatar in the Stadia app and choose "Add Account to Chromecast," I again get "No nearby Chromecasts are ready to add an account," as before (and as shown in your second image).  
  12. Unenrolled in Google Home > [select CCU] > Device Information > "Preview program"
  13. Did another factory reset of both Stadia Controller and CCU
    1. Uninstalled and reinstalled both Google Home and Stadia (v3.41, released 2w ago) apps on iPhone 7
    2. Re-sync'd CCU with wifi using Google Home
    3. Re-sync'd Stadia Controller with wifi using Stadia app
      1. entered linking code on TV / CCU
      2. got "Time to play!" and clicked Done on app
    4. Use your phone to add an account
      1. same screen as before; not found
      2. got popup for local network; enabled
    5. Checked CCU firmware version Preview Program is "Off (Waiting for next public firmware update)"
      1. Turns out, it looks like one can't revert the CCU firmware to a previous version

Here are some resources I consulted while attempting the above: 

  1. Stadia Reddit - Dec 22, 2020 - "No nearby Chromecasts are ready to add an account" I have tried ever...
  2. YouTube - Nov 2020 - Stadia now has messaging AND how to get iOS 14 to talk to your Chromecast!
  3. Stadia Help - Link your Stadia Controller to a Screen
  4. 2019-11-19 - Stadia Community - Can't connect account from Stadia APP to Chromecast 
    1. Suggested answer says "From the Stadia iPhone app, launch a game and select the Chromecast ultra from the dropdown.  Doing that will bring up the "all this app to connect to devices on the network" prompt which you need to allow/agree to.  Once you've successfully launched a game your Stadia account will be linked to the Chromecast Ultra" - this does NOT work for me. When I try to "launch a game" from the Stadia app on my iPhone 7, I get a screen that says "Find a way to play" with a message "to play on a phone, install the Stadia mobile app on a supported mobile device."
    2. One response from 2020-12-02 mentioned XFinity, which is my ISP, and that the only solution was to set up port forwarding. I haven't tried this, since it seems to imply access to an XFinity rented router, which isn't my situation.
  5. https://www.lifewire.com/fix-when-stadia-cant-connect-to-chromecast-5116416  

Here are some things I have heard that might help, but have not tried, since I don't have access:

  1. Rebooting router
  2. Trying to set up Stadia & CCU on Android

 

1 Kudo
codekiln
Stadia Player
Stadia Player

Stadia had me verify that if I connected via a hotspot, I was able to associate the CCU to the Stadia Controller, and suggested that the inability to connect the CCU to the Stadia app was because our network is blocking ports 44700 - 44899.

The only problem with this hypothesis is that as far as I know, my network conditions haven't changed at all, and I was able to associate the controller with the CCU back in February just fine.

So either (at least for me) XFinity network settings changed, or Stadia's registration protocol changed, and it's difficult to substantiate which one is to blame. 

0 Kudos