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?

[Adrianmsmith]

@Revollaer "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."

So you clearly accept it is not Bricked!! .....

Yet you say it is. You seem confused!

Again, bricked is used to say "will not boot to any useable state".

You can cast to it, which is done via wifi only, Regardless of ipv4 or 6 being utilised downstream of your router , which is required to process any voice requests.

Im happy for the fix.  i will be happier when google fix the firmware to allow ipv6 to turn back on, even though it may be many years prior to me actually requiring ipv6 😎🤫  

[Revollaer]

No mate, you seem confused as i clearly said that we used the word "Bricked" when they were rendered unusable before a temporary solution of disabling aspects of our routers capabilities to accommodate googles downgrade were discovered. If you scroll up, the word "bricked" was used before any solution to this issue was discovered hence, at the time of the word being used; no one could use these devices at all. Though once again you have a very anti-consumer way of looking at life, I'll let you fight googles good fight. Just for the record, if a company push an update that renders a product that you have purchased totally unusable, its considered "Bricked" weather it can be turned on or not....obviously... If i buy a smart toaster, which then receives a mandatory firmware update that i have no choice but to accept without my knowledge; at which point the toaster stops toasting my bread....Its not "NOT BRICKED" just because the devices still switches on and the bread can still be pushed down...Then again you know that but it does not fit with your narrative hence, here we are.

Glad you're happy with the "fix", you do you. You failed to address literally any other aspects of the post because, there is no argument to be made so you'd rather side step it and continue your obsession with the word Bricked, so with that i'll take my leave.

[Adrianmsmith]

We are going to have to agree were never going to agree here!

You dont even read all of the post you are replying to prior to ranting!

Good luck!

P s  what are you using that requires ipv6 to operate.

Just asking so i dont purchase any prior to google / nest sorting the current mess out!

[Revollaer]

You're an interesting creature. You literally ignored about 7 different points to discuss the word bricked but everyone else apparently doesn't read.

Good luck to you to.

[Adrianmsmith]

It would help if people like you actually expanded on what they were saying instead of just leaving cryptic clues as to what they may be thinking. 

Actually try giving some answers instead of just finding fault in other people's comments.

[BryanthePilk]

Thank you for suggesting this solution! I have disabled IPv6 and it has worked . I look forward (as some of you) for a fix that allows me to reenable IPv6. 

In the meantime - happy family. 

[Jstern717]

Having the exact same issue. Have tried the re-boot, deleting, etc. Sooo frustrating. I even tried an older speaker- same. "Your Google Home has not been set up."

[Revollaer]

I'd try the temporary solution i posted above if you really need it working anytime soon. Other than that can only wait for acknowledgement/solution from google. If you have Thread or IoT devices like me you wont want to disable IPV6 though.

[Adrianmsmith]

Calm is temporarily restored to the universe 🥳

[Revollaer]

I've managed to get the minis working today by turning off LAN IPV6 and still keeping on overall IPV6 but will see how long that lasts. Didnt work at first but i noticed a reminder light came on, so i said "hey google, are you working now?" and she said "ALWAYS! I LOVE THIS JOB".....🙄

[MrCoal]

Don't know if this is related, but about 2 weeks ago all 4 of my Nest Hub (2ndGen) stopped working. After MANY resets, reinstalls, chats with support, sending videos to Google Engineering, etc. I could not get these devices working again (they had been working fine for 7 months). I was able to add the devices to my home and connect to them and see they were connected, but all I got on the display was a blank white screen.

I read on this thread about needing to disable IPv6, but on my (ASUS) router IPv6 was already disabled.

On a lark, I decided to ENABLE IPv6 on my router, and lo and behold, all 4 of my Nest Hubs were able to finish setting up and connect to my Google Home account. All 4 Nest Hubs are fully functional again.

I dont' quite understand what happened, but Google must have changed something on their servers to require IPv6. Probably only a coincidence, but, for me,  this all started when the CloudStrike issue shut down much of the internet.

[Revollaer]

I'd not be remotely surprised if Google decided to checkmate us by making the minis only work with IPV4 and the hubs only work on IPV6.

[Badarse73]

Google update made them fail. My google home failed last night and now only works as a Bluetooth speaker. So hence comms works but not to google home. I am also Tech savy. Bye google cant fool me. I love my sound so this won’t be used as a speaker. Rattles now after throwing it the bin 😝

[Adrianmsmith]

Get it back out and disable ipv6 for now on your router Lan side

[Russellguthrie]

This is worth a shot, sure.  But let's please stop pretending this is a solution.  It's a hack at best for something Google is unwilling to acknowledge they broke.  And many of us didn't even have ipv6 enabled.  Myself on a Google branded mesh network.  And so there's still make people with no workaround and Google still not acknowledging the problem.

[Revollaer]

Could not agree with you more. The fact that Google have taken hundreds of £ from people buying their devices and investing in their eco system, to rendering them inoperable with no option to reverse the firmware, nor acknowledge the issue; has to be a breach of something somewhere.

[Adrianmsmith]

Im also in agreement with both of you!!

I just jeep repeating the ipv6 stuff as its a short term help to some and noone reads anything more than a day old 😎🤭😜 

Yes they should be pushing out a fix by now.

Unfortunately all they seen to do  is  break stuff or turn stuff off recently.

Many complaints about recipes being turned off 

As for gemini, should he called exodus. Tried it for three minutes to find it cant do the thing i do most often, turn my coffee machine on.

Absolute garbage.

"I can't do that yet"

Garbage.

[Revollaer]

Tried any good Light Roasts lately? Might as well talk amongst ourselves while we wait for Google.