Nest protect will not connect

[snykamp]

I updated the wireless router and the new system has the same name and password but the nest protects will not reconnect.  They all get hung up in when trying to connect.  I tried testing the network connection manually and it also gets hung.  I deleted one, reset to factory settings and tried to reinstall it but it is looking for another product to help connect and it gets hung up at that step. 

I reconnected the cameras but I had to rescan the QR code to do so.

I have been through all the troubleshooting options on line with no success.

[KMJU]

Similar but different problem:  I've purchased two 120v wired Nest Protect smoke/CO alarms to install in two different areas of my condo.  So far, a super-colossal total freaking FAIL!!!!

First of all, I was assured before I bought the items that they would work with the Google Home app. (I own a Google Home Hub.)  To my dismay, the installation process required me to download and install the Nest app.  So fine.  I did that and followed all the directions to set it up and got through the pull-tab and test stage.

Then I get to a screen what wants me to enter the Nest Protect Network Name.  I do that and hit the Continue button....and all I get is the spinning wheel.  I believe it should be prompting me to enter my home network password but that's not happening.  Just can't get past entering the Protect network name,

So, I an officially FURIOUS!.  No apparent alternative but to reinstall the non-Nest detectors that I just took out.  

Would appreciate any solutions.

[KMJU]

Call off the dogs.  Troubleshot and found two issues:  1) The Nest app somehow didn't have camera access so it couldn't read the QR code.  My bad.  2) It turned out that the network router and one of the two detectors being replaced were on the same breaker.  (Who knew?)  I had cut the power to take down the two detectors being replaced, which meant that the network, unbeknownst to me, was also shut down.  

File under Lessons Learned.  Still not happy about the Protect devices apparently not being compatible with the Home app.

[EmersonB]

Hello everyone,

@snykamp thanks for reaching out here in the Community. You may follow these steps to update it from your Nest app:

1. On the Nest app home screen, tap Settings Nest settings icon.
2. Select your Protect.
3. Go to Device options and then Wi-Fi connection.
4. Tap Next. Nest will attempt to connect to your Protect, and it will start looking for nearby Wi-Fi networks.
5. Select your Wi-Fi network and enter the password. Your Protect should automatically reconnect.

In case these steps didn’t work, you may need to start over with setting them up again. 

Give these steps a try:

1. Remove your Nest Protects from your Nest apps. 
2. When setting up multiple Nest Protects they should be placed on a table near your Wifi router.
3. Perform a reset to factory default.
4. While pairing they should have a blue light pulsing, indicating that they are ready to be set up. If not, just press it one time. 
5. Remember the Nest Protects can only connect to a 2.4GHz Wi-Fi network.

@KMJU I appreciate you sharing your experience and what you’ve done to resolve the issue. As of the moment the Nest Protect can only be set up and controlled remotely with the Nest App. We're always looking for ways to improve and we'll take it as feedback. I'd suggest you send feedback about your concern using this form to let the Google Engineering team know about your concern. While they won't respond directly back to you, this is the best way to let them know about this.

Let me know if you have other questions in mind.

Best,

Emerson

[janthadeus]

Hey folks,

Checking in — did you get a chance to try the suggested steps provided by Emerson? If so, how did it go? Let us know if you need anything else.

Thanks for the help, Emerson.

Best,

JT

[KMJU]

Look at my previous response.  This case is closed.

[Jake]

Hey there,

I am glad to hear you are good to go from here KMJU.

snykamp, I want to ensure you are good to go, and everything is working properly. Please let me know if you are still having trouble, as I will be locking the thread in 24 hours due to inactivity.

Best regards,
Jake

[KMJU]

The connection issue is solved.  But the problem of the two nests alarming every time I light a fire in my fireplace is not resolved.  The detectors the Nest Protects replaced did not have this issue.  I'm actually getting close to pulling the Nest Protects out and going back to what I had.

[EmersonB]

Hi folks,

@KMJU, thanks for getting back to us. Some rooms in your home have conditions that are more likely to damage a smoke and carbon monoxide alarm or set off nuisance alarms. Regulations recommend against installing combination smoke/carbon monoxide alarms in these rooms:

Kitchens 

• If you want, you can install Nest Protect closer to cooking appliances than conventional smoke alarms. However, regulations suggest you place it at least 10 feet (3 meters), from cooktops or cooking appliances.

Unfinished attics 

• Smoke alarms are not designed to work in extreme heat or cold, or in areas where smoke and dust are common as it could damage the sensors of the alarm.

Garages 

• As they are usually not heated or cooled, the actual temperatures experienced in a garage may go above or below the temperature range that the alarm has been designed for. The smoke from engine exhaust fumes can also cause nuisance alarms and damage the sensors of the smoke alarm.

Furnace rooms, or any room that contains a water heater or a furnace. 

To avoid nuisance alarms, carbon monoxide alarms should be 15-20 feet from water heaters or furnaces.

I appreciate the help, Jake and JT.

Thanks,

Emerson

[EmersonB]

Hello KMJU,

We wanted to follow up and see if you are still in need of any help. Please let us know if you are still having any concerns or questions from here, as we would be happy to take a closer look and assist you further.

Regards,
Emerson

[Markjosephp]

Hi KMJU,

It has been a few days since your last reply, and we're going to lock the thread within 24 hours. If you have any questions, please feel free to create a new post.

Regards,

Mark