cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

I can't connect a Google Wifi point after factory reset

Mackenzo
Community Member

Using Google Home for setup, I have the router working and one point.  When trying to setup the second point, everything stops when trying to connect to the point through wifi.  I keep getting the message, "Connection Failed.  Couldn't connect to the device.

Thanks for any help,

Ken

4 REPLIES 4

ChopChop
Community Member

Interesting. I had this same problem today. I kept trying and a couple of factory resets later it connected, but move on to a different error.  My thread here https://support.google.com/chromecast/answer/3213084  (in case anyone is looking for patterns)

Jeff
Community Specialist
Community Specialist

Hey, Mackenzo.

Sorry for the issues you're having with the WiFi point setup. I know how frustrating it can be when things won't connect. Let's take a look at the situation and come up with a fix.

As ChopChop said, this is actually an issue that's popped up for a few others. While it can be time consuming, a few people have found success by performing the factory restart and by reinstalling the Home app before going through setup once more. Try going through that full process, and if you are still having issues, let's look at additional steps we can take.

Thanks.

 

ChopChop
Community Member

I have done the full factory reset a  few times - following the process that others have posted here. I've probably tried this 7 or 8 times in total trying to solve the issue with periodic disconnects  

 

It was the last time trying this that resulted in me being unable to reconnect the WiFi point. I'll try it again at the weekend and see if it at least resolved that issue but I would be incredibly surprised if it somehow solved the disconnect issue this time 

 resulted in the 

Jeff
Community Specialist
Community Specialist

Hey, ChopChop.

I sent a response through to you on your thread on this issue. In that instance, I've passed it on to another team for more help.

As this is now a duplicate of the same issue, I'm going to go ahead and close the thread. We'll continue to use the single thread to manage updates.

Thanks.