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.

MASTER THREAD for Problems adding multiple Nest Protects

Legolad
Community Member

 

INTRODUCTION

4 years and 44 separate threads about this specific issue and still there is NOTHING official from Google that explains exactly what is wrong or how to fix it. There are several different error codes, so it's not clear how many of these are actually the same problem, but they all have the same result: You cannot add more than one Protect to your home. 

In the hopes that this will help others who have this issue, I've created this master thread where people can see all the stuff we know so far.

 

TOO MANY SOLUTIONS

There is a lot of guessing going on and lots of anecdotal fixes, mostly having to do with IPV6 and mostly written by the community rather than Google. However, there has been NO definitive post or info from Google on this. Here are some examples of "possible solutions" given by Google and the community:

  • You have to create a new Home and then add all the protects there.
  • You have to keep 2 separate homes in your app.
  • You have to bring all the Protects to within 1 meter of the router before you do the setup.
  • You have make sure all the Protects connect to a 2.4 GHz  wifi radio.
  • You have to make sure your Router supports IPV6.
  • You have to actually turn IPV6 on in all your networking equipment (modem, router, switches, etc).
  • You have to use the latest version of the Nest app.
  • You have to update all the Protects to the latest firmware.
  • You have to restart the first Protect to refresh it's network settings.
  • You have to use an Android device because the iOS version has a known bug.
  • You have to manually enter the pairing key instead of scanning the QR code.
  • You have to use a different access point.
  • You have to update the firmware on the existing access point.

It's very difficult to know which, if any, of these ideas actually work. This is made worse by the fact that Google's responses are NOT consistent and there is no single blog post or fact sheet that spells out which of these things is related to which error code. Consequently, everyone who encounters this issue has to re-invent the wheel by reading every thread and trying every possible solution. Not a great way to handle your community, Google.

 

GOOGLE's "SOLUTION"

First

Here's the link Google says we should all use if we have this problem:

https://support.google.com/googlenest/gethelp

Second

Google say that they pushed a fix in 2023, but some people who did a full device reset while the bug was out there may still have issues. They say they are working on another fix for those people and that it should come out in early 2024.

 

LINKS FROM GOOGLE POSTS

Here are all the links I saw Google post for users who reported this issue. Note that some of these list all sorts of solutions or things to try, but none of them can say definitively which things work.

https://support.google.com/googlenest/answer/9249840?hl=en&sjid=15025473046573029198-AP#zippy=%2Con-...

https://support.google.com/googlenest/answer/9247146?hl=en

https://support.google.com/googlenest/answer/9263646?hl=en

https://support.google.com/googlenest/answer/9251232?hl=en-AU#zippy=%2Ccheck-your-routers-ipv-or-mul...

 

ONE POSSIBLE FIX

This process worked for me:

1. Remove all devices from the Nest app.
2. Try adding all the Protects to the Nest App before you add any other devices.
3. If this fails, remove the Nest app from your iPhone and re-install it.
(You can also try a different iOS device with a fresh install of the Nest app.)
4. Try Step 2 again.
5. If this fails, you need to update the firmware on all the Protects.
6. Gather all Protects in one place near your Wifi Access Point.
7. Remove all devices from the Nest app.
8. Remove the Nest app from your iPhone and reinstall.
(You can also try a different iOS device with a fresh install of the Nest app.)
9. Add 1 Protect to your home in the Nest app.
10. After it's added, press and hold the Protect button until it says "Checking the network".
The Protect will automatically take the latest firmware. You can see it change in the app.
11. After the firmware is updated, remove the Protect from the app.
12. Repeat steps 9-11 for each protect you want to add.
13. When all the Protects have been updated to the latest firmware, remove all devices from the Nest App.
14. Remove the app from your phone.
15. Re-install the Nest App.
16. Add 1 Protect.
17. When the app asks, add another Protect device.
18. AFTER all the Protects have been added, add other devices to the Nest App (thermostats, doorbells, etc.).


NOTES

  1. I went through my modem and network settings and enabled IPV6 before I found this solution. These changes did not appear to help at all, but it is possible that the changes took some time to propagate through my devices. I cannot confirm this so I cannot say that IPV6 is necessary. 
  2. Connecting the LOWEST firmware version first did not work for me but I never tried it from a fresh install of the Nest App.

 

ALL THOSE THREADS

Here are the related threads. Maybe someone at Google can finally analyze these and see that the solutions they have proposed DO NOT WORK and that this deserves a special blog post or fact sheet or whatever it is Google does with a widespread problem in their products.

https://www.googlenestcommunity.com/t5/Nest-Protect/2-of-3-Nest-protects-offline/m-p/549762

https://www.googlenestcommunity.com/t5/Nest-Protect/Nest-Protect-P009-0-80-error/m-p/548223

https://www.googlenestcommunity.com/t5/Nest-Protect/Nest-Protect-does-not-connect-to-Nest-App-Hint-f...

https://www.googlenestcommunity.com/t5/Nest-Protect/Cannot-set-up-second-Nest-Protect-P030-and-P024/...

https://www.googlenestcommunity.com/t5/Nest-Protect/Can-t-add-a-new-but-old-Nest-Protect/m-p/469536

https://www.googlenestcommunity.com/t5/Nest-Protect/Nest-Protect-Can-t-Add-Device/m-p/422815

https://www.googlenestcommunity.com/t5/Nest-Protect/cannot-get-next-protect-setup-through-nest-app-U...

https://www.googlenestcommunity.com/t5/Nest-Protect/Protect-can-t-finish-setup-various-error-codes/m...

https://www.googlenestcommunity.com/t5/Nest-Protect/Can-t-connect-my-new-and-first-Protect-Other-Nes...

https://www.googlenestcommunity.com/t5/Nest-Protect/Nest-protect-won-t-update-wifi-or-add-product/m-...

https://www.googlenestcommunity.com/t5/Nest-Protect/3-Nest-Protects-went-offline-and-won-t-connect/m...

https://www.googlenestcommunity.com/t5/Nest-Protect/Unable-to-add-Nest-Protects-P023-error/m-p/23174...

https://www.googlenestcommunity.com/t5/Nest-Protect/Nest-can-t-connect-to-app/m-p/234457

https://www.googlenestcommunity.com/t5/Nest-Protect/Nest-protect-unable-to-connect-to-WiFi-error-cod...

https://www.googlenestcommunity.com/t5/Nest-Protect/Bought-new-Nest-Protect-setup-fails/m-p/363819

https://www.googlenestcommunity.com/t5/Nest-Protect/Protect-Setup-Stalls-with-Error-P030/m-p/370141

https://www.googlenestcommunity.com/t5/Nest-Protect/First-Time-Protect-User-Bought-3-only-first-one-...

https://www.googlenestcommunity.com/t5/Nest-Protect/Issue-with-smoke-alarms/m-p/400312

https://www.googlenestcommunity.com/t5/Nest-Protect/Set-up-Nest-Protect-will-end-up-with-error-code-...

https://www.googlenestcommunity.com/t5/Nest-Protect/Nest-Protect-P009-Error-Cannot-Add-To-Account/m-...

https://www.googlenestcommunity.com/t5/Nest-Protect/nest-protect-error-p006-3-10/m-p/430339

https://www.googlenestcommunity.com/t5/Nest-Protect/Can-t-register-Nest-Protect-as-it-gives-a-P007-3...

https://www.googlenestcommunity.com/t5/Nest-Protect/Unable-to-add-more-than-one-Nest-Protect/td-p/57...

1 REPLY 1

David_K
Platinum Product Expert
Platinum Product Expert

This is a great post. To build on this, regarding IPV6, that's required if you're going to add multiple Nest Protects, as that's used for the wireless interconnect between them. It's technically not required to setup just one Nest Protect. It's normally not all that important, as most modern routers support IPV6 and have it enabled by default anyway. Just thought I'd add that info!