<?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>topic Device set up on 2.4Ghz still looking for 5G -- why?? in Nest Wifi</title>
    <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Device-set-up-on-2-4Ghz-still-looking-for-5G-why/m-p/557838#M49724</link>
    <description>&lt;P&gt;A device I just got (Yoto kids audio player) said it required 2.4Ghz to set it up. I was finally able to do so after reading some previous forums about this issue (unplugged a few of our pucks and went far away from the router). However, now even when I power the device on, it says it is offline - presumably because it is trying to connect to the 5G. My question is why would this be happening and is there something else I can do on the router's end to force it to only connect to the network that it was set up on?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 08 Dec 2023 20:00:24 GMT</pubDate>
    <dc:creator>erinnmont</dc:creator>
    <dc:date>2023-12-08T20:00:24Z</dc:date>
    <item>
      <title>Device set up on 2.4Ghz still looking for 5G -- why??</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Device-set-up-on-2-4Ghz-still-looking-for-5G-why/m-p/557838#M49724</link>
      <description>&lt;P&gt;A device I just got (Yoto kids audio player) said it required 2.4Ghz to set it up. I was finally able to do so after reading some previous forums about this issue (unplugged a few of our pucks and went far away from the router). However, now even when I power the device on, it says it is offline - presumably because it is trying to connect to the 5G. My question is why would this be happening and is there something else I can do on the router's end to force it to only connect to the network that it was set up on?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Dec 2023 20:00:24 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Device-set-up-on-2-4Ghz-still-looking-for-5G-why/m-p/557838#M49724</guid>
      <dc:creator>erinnmont</dc:creator>
      <dc:date>2023-12-08T20:00:24Z</dc:date>
    </item>
    <item>
      <title>Re: Device set up on 2.4Ghz still looking for 5G -- why??</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Device-set-up-on-2-4Ghz-still-looking-for-5G-why/m-p/557979#M49731</link>
      <description>&lt;P&gt;This behavior is caused by the client device not having Wi-Fi capabilities implemented properly, not Nest Wifi.&lt;/P&gt;
&lt;P&gt;Nothing more you can do on Nest Wifi about it. Only thing I can think of that &lt;EM&gt;can&lt;/EM&gt; help with troublesome devices is to turn off WPA3, if it's enabled. Worth a try at least.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://support.google.com/googlenest/answer/6309220?hl=en" target="_blank"&gt;https://support.google.com/googlenest/answer/6309220?hl=en&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;But WPA2 is still enabled when WPA3 is enabled, so devices only supporting WPA2 should handle it.&lt;/P&gt;</description>
      <pubDate>Sat, 09 Dec 2023 07:24:57 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Device-set-up-on-2-4Ghz-still-looking-for-5G-why/m-p/557979#M49731</guid>
      <dc:creator>olavrb</dc:creator>
      <dc:date>2023-12-09T07:24:57Z</dc:date>
    </item>
  </channel>
</rss>

