Ok what exactly is going on here

[Revollaer]

A little over 2 weeks ago my bedroom Nest Mini (gen 1) bricked its-self. It started saying "your google home isn't setup yet..." After literally dozens and dozens of reboots, factory resets, adding new rooms, creating a new home address, trying it on different Wi-Fi connections, hotspots i came to the conclusion it was just dead, and replaced it with a google nest hub mini 2. I'm relatively tech savvy, so i was already sceptical that this device was "broken" and yet i could still cast music and access/change the volume of the device through the app, just not actually use it for its intended purpose...

Now, as of today, a Gen 1 Nest Mini in the Office and a Gen 2 Nest Mini in the kitchen have both broken. "Hmm, something went wrong.." Same attempts to remedy the situation fruitless.

Now I'm happy to believe 1 nest device failed, despite how inexplicable the symptoms seem to be...But I'm calling you out with the addition of this new development. I find it ironic, that the 2 latest Nest Hub Mini's are fine, but my older devices, despite being of various age and generation are all dropping like flies; and it looks like i am not the only one with this issue out of the blue.

Someone else stated this seems like a deliberate attempt to force customers to upgrade and whilst i would normally disregard such conspiracy theories, this now certainly seems to add up.

So, what exactly is going on?

[BryanthePilk]

There is now half a dozen posts for the exact same issue on this notice board. Google is yet to respond to any of them

[Revollaer]

Indeed, its the lack of response from google i find concerning!

[Adrianmsmith]

We finally agree 😁😋🥰

[Revollaer]

I'm a photographer for a living, and home barista is my biggest hobby. We agree on more than you think, just not who should make concessions for a billionaire companies mistakes.

[Adrianmsmith]

Have we actually met elsewhere? I'm a photographer / install engineer for a living and home barista is a very major hobby of mine as well as Hi-Fi!..

And no I am not taking the p!! AVS evo leva mk2. Mazzer Philos. Niche due. We digress!

[Revollaer]

I know, which is why i brought up photography and home barista. You weigh'd in on a post on Reddit before coming here and your name was the same, its in your reddit bio.

I have the dual boiler, and the eureka mingon oro single dose

[Adrianmsmith]

Rightly or wrongly my name is the same just about everywhere!!

Did I upset you on Reddit as well? Or are we okay on there. 🫣🤭

[Revollaer]

Don't think so, you replied to turn off IPV6 and then followed the link i posted here. When i went back to reddit to clear the notification i noticed you were the same person

[Adrianmsmith]

So we both agree that nest or Google or whoever is responsible for the firmware  should be sorting this mess out. 

The thing we don't agree on is how to make the most of our equipment while we are waiting for Google to sort this mess out and I was just trying to point out to people that do not need IPv6 that this is one solution until  the  wait is over. 

Yes, I understand that some people do need IPv6 but it is for very specific use cases and I perhaps wrongly assumed that most of the people with nest, mini speakers, etc would not also have a use case where IPv6 is actually an advantage or requirement.

Looking at the reply I got from Google devs I am not expecting a solution this week 😎

[Revollaer]

Yes we do, though the biggest sticking point seemed to be that you disliked the word temporary solution. I agree changing to IPV4 is a good temp fix, especially for people with just minis but i say its a temp solution because the real solution is google fixing it, so we can all go back and enjoy IPV6.

I also agree that it does not look like we will be seeing our original functionality returning any time soon having a read through that.

[Adrianmsmith]

We understand it's frustrating to encounter the "Something went wrong" error. 
IPv6, the next generation of internet protocol, is still relatively new and can cause compatibility issues with some devices. 
Feel free to check this link for more information.
https://support.google.com/googlenest/answer/6361450?hl=en&sjid=3192520759623525202-NA

 Was from google devs.

[traycee]

My mini began telling me 'something went wrong' or 'there was a glitch' and required four, five sometimes 6 repeats to respond appropriately. With 20+ seconds to think about each request  before saygin it had an issue it was a couple of minutes for an answer (or for my one minute timer to activate - uselss!) 

My "Your Google Home isn't set up yet" began today - up until now I've only been using it as a bluetooth speaker beacuse that's all it could do. Now, after all the reboots and resets and uninstalls and reinstalls it doesn't even function as a bluetooth speaker. Everything LOOKS okay in the app, but nothing is okay. Bricked.

[Revollaer]

Yep, and still not a word about it. I now have 3 bricked speakers within 3 weeks, 2 Gen 1's and a Gen 2, the only ones working are the screen hub devices. I took back the new screen i bought to replace the dead mini now that i realise its a google issue; I'm not paying them a penny more.

Currently the bricked speakers have different moods, sometimes "There was a glitch!" mostly "Something went wrong..." but their fan favourite for today is "Your google home isn't setup yet...".

Imagine pouring hundreds in to smart speakers only for them to all inexplicably die at the same time out of nowhere and the company that runs them just keeping their mouth shut...

[AxelD]

Hi folks,

Thanks for posting in the community! Sorry to hear that your Nest Mini's Gen 1 and Gen 2 aren't responding. I completely understand all these devices are really important to y'all. No worries, help is here! Let's try some troubleshooter steps: 

1. On the side of the device, unplug the power cord >  wait 10 seconds > plug the power cord back in > wait until the 4 LEDs light up.
2. Repeat the first step, 8 more times.
3. On the side of the device, switch the mic off. The LED lights turn orange.
4. Press and hold the top of the device (where the LED lights are).
5. After 5 seconds, the device begins the reset process.
6. Continue to hold the top of the device for 10 seconds more or until the Google assistant confirms that the FDR has started.
7. Wait until the device announces “Welcome to Google Home" >  use the Google Home app to set up the device.
8. After the setup is complete, advise the customer to test the device with any voice command.

Let me know how it goes.

Regards,

Axel. 

[Revollaer]

All of these have been tried.

• Powered on and off more than 30 times, left off over night out of frustration several times.
• Factory reset over 20 times, and reconnected.
• Connected to different "homes" under the Home app and different rooms.
• Connected to 2.6ghz wifi and 5ghz wifi separately
• Connected to WiFi Hotspots on phone and tablet.
• Tried setting it up from a Samsung phone, Samsung tablet and iPhone.
• Taken to friends house and connected to different internet and home account
• Opted in to the BETA, hoping to get a new Firmware that fixes it, but no such firmware available.
• Reset internet connection and tried multiple changes in my router (Despite the fact i should not need to do this)
• Sworn at them multiple times

End result: 2 Gen 1 mini's and 1 Gen 2 mini all screaming "THERE WAS A GLITCH!" or "YOUR GOOGLE HOME ISNT SETUP YET!" across the house every time i say "Hey google"

[80sTechGuy]

I found that I had trouble with all of my speakers with ipv6, so I reluctantly turned it off at my router.  That didn't entirely fix the problem though.  The only way to make then work reliably is to have 8.8.8.8 as either the primary or secondary DNS server.

[Adrianmsmith]

It diesnt. Need to turn off ipv6!!!!!!!

[Adrianmsmith]

@traycee 

Mine did the same.

I disabled ipv6 in my router.

Magically everything working again.

If tou have no specific use case for ipv6 turn it off and try.

[Russellguthrie]

Yeah what gives Google?  I've now had 4 minis and my main Google home all brick in the past month.  Basically one right after another.  So what did you do and more importantly what can WE DO to get this back?  Factory reset does nothing.  Please advise!

[alexm2321]

I’m having this same issue with my Google Home Mini (1st Gen I believe bought in 2019ish) I found it today and decided to get it set back up, my chrome cast connected just fine after a rest but the Home will not no matter how many times I reset it. When I go into the Google app it will find the device but then it won’t connect to it and it will tell me to factory reset it even tho I’ve tried that at least 50 times by now. Also what I thought is odd that when I reset the home it doesn’t ever annonce “welcome to Google home” etc whatever else it says

[Revollaer]

For those following this thread, this has been posted on another thread about the same issue:

Hello  Everyone,
 
Thank you for your patience and understanding as we work to resolve this issue. I apologize for the inconvenience caused by Google Home Minis.

I understand the frustration of encountering this issue, especially after trying various troubleshooting steps. Your case has been escalated to our specialized support team for further investigation.

I will provide updates as soon as more information becomes available. In the meantime, if you discover any additional details or encounter any changes in behavior, please don't hesitate to share them with me. Thank you. 
 
Best Regards, 
Mario.

[layjent]

So here's the background:

A relative of mine has had two google home minis for a number of years and has really enjoyed having them. After coming back from a vacation they suddenly started responding saying that they needed to be activated and to download the google home app to do so, but not clear what changed.

What I have tried:

I have factory reset the devices, upon doing so, I can connect to the google home mini via phone and change the speaker volume, but whenever I ask google assistant something, it comes back with that they need to be activated.

I tried uninstalling the google home app and reinstalling

I tried using a different device to install them

I tried resetting the wifi

I change the wifi username and password

I tried updating the firmware on the wifi router

I tried both 2.4 ghz and 5.0 ghz (even though realizing that the latter would not likely work)

I have also connected them to MY home internet (different house). At that point it activated correctly and worked without any issues. Went back to relatives house, factory reset, and again they wouldn't connect.

Any ideas? While I realize the devices are old, I'm concerned that buying a new device will have the same issues given that I could connect these ones to my network, just not to my relatives.

Thanks!

[Revollaer]

Re: Ok what exactly is going on here - Google Nest Community

Many people experiencing it, Google not saying a word. i think its the Firmware from 15/07.

[Jstern717]

That seems to be about when things got glitchy.

[AxelD]

Hi folks,

Good to hear from y'all! Sorry to hear that the troubleshooting steps above didn't work for you. Please Share feedback about Google Nest to report this situation. 

Regards,

Axel. 

[JJH68]

What is going on! My nest and mini speakers all stopped working also. Have tried all the steps given but to no avail. They just say hmm something is not right try again in a few minutes or google home is not set up yet. Mind you everything worked great until about the middle of July. The only speaker that still works is the google home max. I have read it has an older software that was not updated so apparently the new software is to blame.

[Revollaer]

Exactly this. Mini's are only effected, the newer products are not. My screen based hubs work just fine. The firmware came out on 15/07 which is around when most of the victims in this thread had all their mini's bricked. Still no official word; one thread has a community specialist say "its being investigated" this thread just says to report it, which is weird considering its apparently being investigated...Which leads me to wonder if its actually being investigated. 

[Revollaer]

@AxelD Is there any update on the situation? Can you confirm now that we have shared feedback and many have reported the same issue if this is:

A: Identified as a problem, a mistake, or faulty firmware update or a "working as intended" change to the system?

B: Is a fix being sought so that people don't need to fiddle with their router settings for temporary fixes?

C: An ETA on, providing this was not intended; the fix will be implemented?

Thankyou

[Adrianmsmith]

Hi @Revollaer 

Could you link the thread please, would like to follow the feedback. Thanks. Ade.

[Revollaer]

For those interested, their does seem to be a "fix" for this problem. This is NOT the solution, it is a temporary fix for those of you willing, which i am not.

If you login to your Router, and disable IPV6 (defaulting your internet to IPV4) it seems to be fixing the problem. This is a full on disabling of IPV6 not just DHCP.

The real solution is google having the decency to acknowledge there is a problem, and undo whatever they did in their firmware to make their mini devices incompatible with IPV6. Nerfing your entire internet connection to an older soon-to-be obsolete protocol to use smart speakers is not a solution, but a short term fix for those who rely heavily on them.

I will be leaving IPV6 on and waiting for google to sort it out.

[Russellguthrie]

Hope that maybe this solves it for some people but my router (a Google mesh system) has never even had IPv6 enabled to begin with.  And mine are all still bricked (except the doorbell and Nest Thermostat).  I really wish they'd just acknowledge they bricked hundreds of dollars of equipment for countless people.  Just fess up and give us some details and an assurance you're actually working on fixing this.

[Adrianmsmith]

Disabling ipv6 worked for me 3 weeks ago and has caused no issues to my network.

Id even purchased a new speaker to find it had the same issues my others!

For now disabling ipv6 is a real solution.

Ipv4 will not be turned off in the near future if at all 

[Revollaer]

I hear ya!!

[Adrianmsmith]

Have you all tried disabling ipv6 on your router.  worked for me and many others.

[Russellguthrie]

Yes sadly, I looked but IPv6 has never been enabled on my router (a Google mesh system no less).  I even enabled it just to be able to then disabled it on a Hail Mary, but that did nothing either.  So my devices are all still paperweights.  Glad that worked for some though.

[Adrianmsmith]

Bricked is different to what you describe.

Bricked is usually a failed or user terminated firmware update causing the item not to boot to any useable state.

Not functioning as you would like is not actually Bricked and does not help people simply glancing at posts.

I agree nest should be addressing this.

I gave a bad review on google store and received a long reply basically saying....

Ipv6 is new with many forms and implementations.

If its causing issues, disable it.

I did and now have zero issues.

Not saying its a fix for everything but what you describe above it will fix?

[Revollaer]

It is a failed firmware. These devices have been working with IPV6 since i  got them, and since i got my new internet provider over a year ago. Google have updated the firmware and since this day; their devices no longer work on IPV6.

• The Firmware has downgraded the functionality of the devices, they are no longer compatible with what they once were and now require an older protocol to use.
• We were not informed of this, nor has it yet been acknowledged as an issue
• People should not be expected to know how to use their Router to disable this protocol, though many using smart homes do.
• People should not have to simply downgrade their broadband, of which they pay good money for; to accommodate this situation.
• If my door keeps slamming, removing the door isn't the fix, its a temporary solution at best.
• If my Smart TV required me to limit my WIFI devices to 5 in order to connect, this would not be a fix, it would be a temporary solution.
• Removing features on your broadband to accommodate a downgraded firmware, which once worked just fine without the "fix" is not a fix. Change to IPV4 if you want as a temporary solution, but the real fix is Google simply restoring the functionality it once had.
• Comments like yours enable this kind of behaviour from companies like Google, next we'll be downgrading our wifi security to WEP as a "fix".

[Adrianmsmith]

@Revollaer 

Thank tou for your thoughts, most if which in principal i agree with.

The part you seem to be ignoring or choosing to ignore is most people do not require ipv6 except for a very few specific use cases and therefore disabling ipv6 is not a downgrade, it is simply learning to live with a new protocol that one day may have a single stable version. That day is not 2024!!

I stand my disabling ipv6 to get it working properly for now.

Leave it on and have issues if you prefer.

I will look out for a fix in the future and enable ipv6.

For now ipv4 does everything i require .

Maybe you could list the limitations having ipv6 disabled gives you. For me, absolutely none.

[Revollaer]

Well, IPV6 exists for a reason. Its the new, upgraded version of IPV4. If you want to get technical, theirs the elimination of NAT, routing efficiencies and QoS just to name a few perks of IPV6 over 4. Do many know what this means? No. Will many notice? No. It works in the background and does its thing, a lot like a routers firewall.

Older devices and new innovations do not mix, no ones expecting an abacus to turn into a calculator. If IPV6 rocked up and the Google Mini didn't support it, id be irritated but I'd get it.

Fact is, the minis are perfectly capable of using IPV6, because they have been, for years. This compatibility has been stealth removed, with no word or acknowledgement. We are still having to assume, that this is a bug and not a feature.

The more people make the concession of downgrading (which it is, a downgrade) the protocols our routers are capable of using to facilitate this bug (again we assume), the less insensitive the multi billion dollar company Google have to fix it, i mean; why bother? Its a temporary solution to googles problem. The real fix, is Google restoring the support that was already there.

I would also argue there is a legality issue at play. When you buy a Wi-Fi plug, or a Wi-Fi Vacuum etc, they all say the same thing, normally on the front of the box so it cannot be missed. "This device requires 2.4ghz Wi-Fi, and will not work on Wi-Fi 5ghz". It says this so people are aware that the common standard of Wi-Fi will render the device useless, and you'll either need to disable it; or split the frequencies. 

The Google Nest Mini 2 is still available to buy today, and there is no word anywhere that you'll need to disable IPV6 across the board on your Router, to make it work. This seems to be further evidence that its a bug (?) but again with no official word we are left guessing.

In regards to your earlier comment about the use of "Bricked" being used; this was used before a "temporary fix" was identified at which point, we could only assume the devices were bricked, as they were useless on any setting in any home on any (modern) Wi-Fi we tested it on.

Unrelated to your posts, I'd like to just randomly say I'm genuinely baffled by this IPV6 issue with the devices. The devices clearly connect to Wi-Fi, they are clearly remaining connected as they have channel utilisation and change channels like any other Wi-Fi as they get congested. They can be controlled over Wi-Fi, the Wi-Fi monitor clearly shows them disconnecting when you unplug it and clearly shows a spike in channel utilisation when you use the activation word to interact with it; so the entire issue seems to be the service end of what the speaker can do and nothing to do with the hardware/firmware interaction.