<?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 Re: Nest and Video-conferencing in Nest Wifi</title>
    <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/18855#M2189</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/13285"&gt;@tierneyjohn&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This kind of thing can be very difficult to diagnose remotely, but let me start by asking if you've run a mesh quality test in the Google Home app and what the results of that test were. You want to place your wireless mesh secondary units close enough to the primary that they both get a "great" rating on that test. They only talk to the mesh using 5GHz, which doesn't go as far as 2.4GHz does. That may mean they aren't right in the middle of an area where you have your clients, but they will provide 2.4GHz and 5GHz coverage from where they are.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you do get a "great" mesh quality rating, you might try&amp;nbsp;&lt;EM&gt;disabling&lt;/EM&gt; the video conferencing preferred activity to see if that helps. I have seen a handful of reports from people who needed to do that, so if that does help noticeably, please use the "Feedback" feature in the Google Home app to report your experience to Google so they can collect more information on this issue.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Sep 2021 15:00:23 GMT</pubDate>
    <dc:creator>MichaelP</dc:creator>
    <dc:date>2021-09-28T15:00:23Z</dc:date>
    <item>
      <title>Nest and Video-conferencing</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/18047#M2188</link>
      <description>&lt;P&gt;I recently installed a three-node Nest pack to replace a wifi extender. I made sure I checked the box to prioritise video-conferencing, but the connection is worse than before Nest.&lt;/P&gt;&lt;P&gt;I am repeated getting warnings of unstable internet connection even though the signal is rated 'lightning fast'. All video-conferencing software (Zoom, Teams, Webex, Skype) have the same problems - no camera or camera freezing, no sound transmitted or poor sound.&lt;/P&gt;&lt;P&gt;This has been very frustrating as the signal seems to be strong.&lt;/P&gt;&lt;P&gt;Any help would be welcomed.&lt;/P&gt;&lt;P&gt;Thanks, John&lt;/P&gt;</description>
      <pubDate>Mon, 27 Sep 2021 12:27:59 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/18047#M2188</guid>
      <dc:creator>tierneyjohn</dc:creator>
      <dc:date>2021-09-27T12:27:59Z</dc:date>
    </item>
    <item>
      <title>Re: Nest and Video-conferencing</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/18855#M2189</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/13285"&gt;@tierneyjohn&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This kind of thing can be very difficult to diagnose remotely, but let me start by asking if you've run a mesh quality test in the Google Home app and what the results of that test were. You want to place your wireless mesh secondary units close enough to the primary that they both get a "great" rating on that test. They only talk to the mesh using 5GHz, which doesn't go as far as 2.4GHz does. That may mean they aren't right in the middle of an area where you have your clients, but they will provide 2.4GHz and 5GHz coverage from where they are.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you do get a "great" mesh quality rating, you might try&amp;nbsp;&lt;EM&gt;disabling&lt;/EM&gt; the video conferencing preferred activity to see if that helps. I have seen a handful of reports from people who needed to do that, so if that does help noticeably, please use the "Feedback" feature in the Google Home app to report your experience to Google so they can collect more information on this issue.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Sep 2021 15:00:23 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/18855#M2189</guid>
      <dc:creator>MichaelP</dc:creator>
      <dc:date>2021-09-28T15:00:23Z</dc:date>
    </item>
    <item>
      <title>Re: Nest and Video-conferencing</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/19276#M2190</link>
      <description>&lt;DIV&gt;Hello Michael&lt;/DIV&gt;&lt;DIV&gt;Thanks for getting back to me. I know remote diagnosis is clunky.&lt;/DIV&gt;&lt;DIV&gt;We've had 'great' and 'lightning fast' ratings from the installation at the furthest point.&lt;/DIV&gt;&lt;DIV&gt;I have just disabled video-conferencing preference I adopted in the set-up (which is illogical) and will see how this goes.&amp;nbsp;&lt;SPAN&gt;I'll get back to you if that's OK?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;Kind regards, John&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 29 Sep 2021 01:08:59 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/19276#M2190</guid>
      <dc:creator>tierneyjohn</dc:creator>
      <dc:date>2021-09-29T01:08:59Z</dc:date>
    </item>
    <item>
      <title>Re: Nest and Video-conferencing</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/19285#M2191</link>
      <description>&lt;P&gt;That lightning fast result sounds like an internet speed test, which isn't measuring the WiFi connection or WiFi mesh interconnect. If you're getting a great rating from the mesh speed test, that's a good sign of the WiFi mesh interconnect quality. See how well disabling the preferred activity works and let Google know if it helps. Do report back here, but be aware I may be out for a few days. A community specialist should check in before long if I don't get to it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 01:36:48 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/19285#M2191</guid>
      <dc:creator>MichaelP</dc:creator>
      <dc:date>2021-09-29T01:36:48Z</dc:date>
    </item>
    <item>
      <title>Re: Nest and Video-conferencing</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/19309#M2192</link>
      <description>&lt;P&gt;Hello Michael&lt;BR /&gt;I just did another mest test and we've got a 'great connection' on the system. I've confirmed the video-conferencing is unchecked as a preference and will see the performance of our Teams/Zoom/Webex conference calls.&lt;BR /&gt;I'll get back to you just to close the loop.&lt;BR /&gt;Thanks, John&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 02:53:29 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/19309#M2192</guid>
      <dc:creator>tierneyjohn</dc:creator>
      <dc:date>2021-09-29T02:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: Nest and Video-conferencing</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/23446#M2202</link>
      <description>&lt;P&gt;Hey tiernyjohn.&lt;/P&gt;

&lt;P&gt;Thanks for updating the community about your progress and big thanks to MichaelP for the help so far. Hopefully you're back to 100% performance for good!&lt;/P&gt;</description>
      <pubDate>Thu, 07 Oct 2021 21:41:49 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/23446#M2202</guid>
      <dc:creator>Jeff</dc:creator>
      <dc:date>2021-10-07T21:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: Nest and Video-conferencing</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/27049#M2453</link>
      <description>&lt;P&gt;Hi, tierneyjohn.&lt;/P&gt;

&lt;P&gt;I just wanted to check in real fast to see if you needed any more help on this or if everything is resolved. If you still need help, please let me know.&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Oct 2021 16:50:54 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/27049#M2453</guid>
      <dc:creator>Jeff</dc:creator>
      <dc:date>2021-10-15T16:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: Nest and Video-conferencing</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/27887#M2529</link>
      <description>&lt;P&gt;Hello Jeff&lt;/P&gt;&lt;P&gt;Thank you for following up with me. At this stage, curiously, unchecking 'video-conferencing' priority seems to have fixed the issue. Kudos to you. Your help was much appreciated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards, John&lt;/P&gt;</description>
      <pubDate>Mon, 18 Oct 2021 00:46:28 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/27887#M2529</guid>
      <dc:creator>tierneyjohn</dc:creator>
      <dc:date>2021-10-18T00:46:28Z</dc:date>
    </item>
    <item>
      <title>Re: Nest and Video-conferencing</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/28076#M2541</link>
      <description>&lt;P&gt;Sounds great, tierneyjohn.&lt;/P&gt;

&lt;P&gt;As we have this sorted out, I'm going to go ahead and close up the thread. If you need anything else on this or in the future, please feel free to start up a new thread.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 18 Oct 2021 16:29:27 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Wifi/Nest-and-Video-conferencing/m-p/28076#M2541</guid>
      <dc:creator>Jeff</dc:creator>
      <dc:date>2021-10-18T16:29:27Z</dc:date>
    </item>
  </channel>
</rss>

