<?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: hmm, something went wrong in Speakers and Displays</title>
    <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/123398#M22866</link>
    <description>&lt;P&gt;There is a huge problem with the 2nd gen minis&lt;/P&gt;&lt;P&gt;Google is not willing to fix it, they keep on blaming it on external factors. This is not true as the 1st gen works flawlessly. So either there is a hw problem or sw problem it is as simple as that.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Mar 2022 11:09:58 GMT</pubDate>
    <dc:creator>Dzardon</dc:creator>
    <dc:date>2022-03-15T11:09:58Z</dc:date>
    <item>
      <title>hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/123250#M22825</link>
      <description>&lt;P&gt;Keep on getting&amp;nbsp;&lt;SPAN&gt;hmm, something went wrong on my 2 Google Nest Minis, and my 2 gen 1 Google Homes, rebooted device, rebooted router, no fix, bloody annoying and a known fault, please fix it. Also my Gen 2 hub is now getting&amp;nbsp;hmm, hmm, there was a glitch please try again in a few seconds error, these devices started out OK, but are now a bloody joke!&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2022 23:48:51 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/123250#M22825</guid>
      <dc:creator>Inzomniak</dc:creator>
      <dc:date>2022-03-14T23:48:51Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/123398#M22866</link>
      <description>&lt;P&gt;There is a huge problem with the 2nd gen minis&lt;/P&gt;&lt;P&gt;Google is not willing to fix it, they keep on blaming it on external factors. This is not true as the 1st gen works flawlessly. So either there is a hw problem or sw problem it is as simple as that.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Mar 2022 11:09:58 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/123398#M22866</guid>
      <dc:creator>Dzardon</dc:creator>
      <dc:date>2022-03-15T11:09:58Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/134015#M24816</link>
      <description>&lt;P&gt;Hey folks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for sharing details about the issue here. Apologize for the late response.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I know how frustrating it is when your device is not working the way it should. Let's dig deeper - when did the issue start? Is it happening to all commands? Does the same thing happen when you use the Google Assistant app on your phone? Does the same thing happen when connected to a different network like a mobile hotspot? Also, please provide the current firmware version of your device.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To check which firmware version you're on, follow these steps:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
 &lt;LI&gt;Make sure your mobile device or tablet is &lt;A href="https://bit.ly/3rMOv0X" target="_blank"&gt;linked to the same account&lt;/A&gt; as your speaker or display.&lt;/LI&gt;
 &lt;LI&gt;Open the Google Home app &lt;IMG src="https://bit.ly/38QtoCU" alt="Google Home app" /&gt;.&lt;/LI&gt;
 &lt;LI&gt;Touch and hold your device's tile.&lt;/LI&gt;
 &lt;LI&gt;At the top right, tap Settings &lt;IMG src="https://bit.ly/38Nb2ma" alt="" /&gt; &lt;IMG src="https://bit.ly/3ttrCRE" alt="and then" /&gt; Device information.&lt;/LI&gt;
 &lt;LI&gt;Under "Technical information," find&amp;nbsp;Cast firmware: X.XXX.XXXXX.&lt;BR /&gt;&amp;nbsp;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Looking forward to your responses.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Muddi&lt;/P&gt;</description>
      <pubDate>Sat, 02 Apr 2022 07:44:30 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/134015#M24816</guid>
      <dc:creator>Muddi</dc:creator>
      <dc:date>2022-04-02T07:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/134181#M24853</link>
      <description>&lt;P&gt;The issue is simply connecting to the speaker directly with one's voice, nothing to do with a phone. The Google mini is sitting on the counter and you say 'OK Google' and then something like what time is it. It responds with&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;“Something Went Wrong...”. Then when you try the command a second time it works. If you don't give any more commands and come back later it has the same issue again.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 02 Apr 2022 14:35:32 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/134181#M24853</guid>
      <dc:creator>sbsmith</dc:creator>
      <dc:date>2022-04-02T14:35:32Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/135957#M25037</link>
      <description>&lt;P&gt;Hey sbsmith,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for that information. I wanted to isolate the issue with Google Assistant itself, and it is best if you could try it on your phone. Also, to isolate network issues, please try setting up your device using a mobile hotspot. Please note that you will need two mobile devices for this setup (one will serve as a router and the other to be used to set up your Google Nest Mini).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Keep us posted.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Muddi&lt;/P&gt;</description>
      <pubDate>Mon, 04 Apr 2022 22:41:48 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/135957#M25037</guid>
      <dc:creator>Muddi</dc:creator>
      <dc:date>2022-04-04T22:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/138322#M25518</link>
      <description>&lt;P&gt;Hey sbsmith,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Checking in to see if the troubleshooting steps shared helped? Let us know by updating this thread, and the community will be happy to assist you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Muddi&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2022 13:53:02 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/138322#M25518</guid>
      <dc:creator>Muddi</dc:creator>
      <dc:date>2022-04-08T13:53:02Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/138334#M25521</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Very strange, hasn't worked for over a year without the 'something went wrong message'. Suddenly started working normally, no change to network / wireless configuration. I remember it working for a few days and stopping, over a year ago, can't remember date. Well see if it continues to work as wanted.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2022 14:21:00 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/138334#M25521</guid>
      <dc:creator>sbsmith</dc:creator>
      <dc:date>2022-04-08T14:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/139202#M25664</link>
      <description>&lt;P&gt;Hey sbsmith,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the update. I'm happy to know that your device is now working properly. Let me know if I can assist you with anything else. Otherwise we can consider this one complete, and I will lock the thread.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Muddi&lt;/P&gt;</description>
      <pubDate>Sat, 09 Apr 2022 14:57:55 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/139202#M25664</guid>
      <dc:creator>Muddi</dc:creator>
      <dc:date>2022-04-09T14:57:55Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/141992#M26186</link>
      <description>&lt;P&gt;Hey sbsmith,&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I wanted to check in and see if you had any questions. Please let me know, as I will be locking the thread in 24 hours due to inactivity.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Jake&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2022 19:29:22 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/141992#M26186</guid>
      <dc:creator>Jake</dc:creator>
      <dc:date>2022-04-13T19:29:22Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/142049#M26214</link>
      <description>&lt;P&gt;I finally discovered that turning off beamforming in the meshrouter works. 1st gen can work with this setting, 2nd gen can't.&lt;/P&gt;&lt;P&gt;So there is still an issue with the devices, but i managed to find a Workaround&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2022 20:18:47 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/142049#M26214</guid>
      <dc:creator>Dzardon</dc:creator>
      <dc:date>2022-04-13T20:18:47Z</dc:date>
    </item>
    <item>
      <title>Re: hmm, something went wrong</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/154889#M28725</link>
      <description>&lt;P&gt;Hey Dzardon,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for providing the helpful information for the community. With the thread not having any activity in a while, I am going to lock the thread at this time. If you have any questions from here, please feel free to create a new post.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Jake&lt;/P&gt;</description>
      <pubDate>Tue, 03 May 2022 17:54:52 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/hmm-something-went-wrong/m-p/154889#M28725</guid>
      <dc:creator>Jake</dc:creator>
      <dc:date>2022-05-03T17:54:52Z</dc:date>
    </item>
  </channel>
</rss>

