<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Grevane Tracker</title>
    <link>https://community.stadia.com/ysfdd67284/tracker</link>
    <description>Grevane Tracker</description>
    <pubDate>Mon, 16 Jan 2023 10:26:06 GMT</pubDate>
    <dc:date>2023-01-16T10:26:06Z</dc:date>
    <item>
      <title>Re: Controller cant link to any code over wifi</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Controller-cant-link-to-any-code-over-wifi/m-p/49559#M2328</link>
      <description>&lt;P&gt;Glad you got it sorted.&lt;BR /&gt;It's probably worth noting that if a device can't connect because of a router issue, there is nothing that Google Stadia will be able to provide information while in alerts, notifications or logs as it's failed to connect to Stadia because of the router (i.e. it never connects to Stadia) other than some sort of "no device detected" message.&lt;BR /&gt;I had similar problems on a brand new BT FTTP Service with the BT Discs. My controller would struggle to connect with the discs turned on. With them turned off things improved. With the Wireless Disc service disabled on the router by BT, things started working better.&lt;BR /&gt;Ultimately, getting rid of my BT Router and Discs and changing to an Asus&amp;nbsp;&lt;SPAN&gt;RT-AX92U gaming router fixed all of my issues and Stadia has been flawless since.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jan 2021 22:16:12 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Controller-cant-link-to-any-code-over-wifi/m-p/49559#M2328</guid>
      <dc:creator>Grevane</dc:creator>
      <dc:date>2021-01-04T22:16:12Z</dc:date>
    </item>
  </channel>
</rss>

