08-10-2024 05:48 PM
Hi Team, I have a replacement Nest Hub (2nd Gen) doing the same thing as my first one. Which is stuck on the startup spinning dots. I spent nearly 2Hrs on chat support the first time working through this issue. They believe my device was faulty and promptly replaced it. (Kudos for that.) The interesting part is when I first received my replacement it connected fine to m home account and was fully operational. It then received a push update from Google and rebooted fine. This is where it becomes interesting. I received a second push update shorty after like about 5min, I was standing there watching it receive the updates BTW, and boom reboots a second time and now i'm back to the same issue as my first device the good old spinning dots, I have volume control of the device and can reboot it via the home app, just no display or voice commands, I have a number of other Google enabled devices working on the same account. Can anyone share similar experiences around this last update?
08-13-2024 04:59 PM - edited 08-13-2024 05:04 PM
Hello @chris_sm,
Thanks for posting in the community.
I appreciate the details about the persistent issue with your Nest Hub. It's frustrating to experience this problem, especially after receiving a replacement device. I really appreciate your patience and effort.
Please try the troubleshooting steps below:
Please let me know how it goes. Thank you.
Regards,
Jorge
08-15-2024 02:42 AM
Hi Jorge, sorry about the delay. I have been busy with work. Please see below.
I am going to be straight to the point here, if you apply very straightforward logic, it's quite simple. Whatever firmware update it last received has caused the device to not function correctly. As these updates a pushed automatically then how can we roll the FW back to test this?
Cheers Chris
08-15-2024 10:03 AM
Hello again chris_sm,
Thanks for replying back.
It's true that having two Nest Hubs that aren't able to go past the boot-up screen is strange. Because of this, I suggest filling out this form. By doing so, you can get in direct contact with our team so we can gather more information about what's happening with your device and determine the best course of action.
It would be helpful if you could provide the previous case number from when your original Nest Hub was replaced. That way, we can take that information into account as well.
Let me know once you've filled out the form. I'll keep an eye out for your response so you can receive a response via email from our team as soon as possible.
Regards,
Angel.
08-16-2024 12:17 AM
Hi Angel, thanks for your prompt response. I have filled out the form and the previous case number is 4-9708000036976
Cheers Chris
08-23-2024 03:22 AM
Bump for the Google team
09-05-2024 02:20 AM
OK, so after extensive testing. I can confirm there is an incompatibility issue between the latest firmware for Google nest and TPLink Deco mesh systems. I set up a seperate SSID on my Nokia FastMile device and it connected and worked straight up. It has running flawlessly for nearly two weeks now.