<?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>WarriorPKT Tracker</title>
    <link>https://community.stadia.com/ysfdd67284/tracker</link>
    <description>WarriorPKT Tracker</description>
    <pubDate>Mon, 16 Jan 2023 09:41:21 GMT</pubDate>
    <dc:date>2023-01-16T09:41:21Z</dc:date>
    <item>
      <title>Re: Controller can't connect to Wi-Fi</title>
      <link>https://community.stadia.com/t5/The-Stadia-Controller/Controller-can-t-connect-to-Wi-Fi/m-p/3837#M44</link>
      <description>&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Ironically, I'm using Google WiFi.&amp;nbsp; So much for ecosystem compatibility.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2019 14:49:01 GMT</pubDate>
      <guid>https://community.stadia.com/t5/The-Stadia-Controller/Controller-can-t-connect-to-Wi-Fi/m-p/3837#M44</guid>
      <dc:creator>WarriorPKT</dc:creator>
      <dc:date>2019-11-22T14:49:01Z</dc:date>
    </item>
  </channel>
</rss>

