Nest Protect P009(0.80) error

[Harrynewzealand]

Hi all

I recently purchased a second hand nest protect and have been unable to connect to it in the app, I keep get getting a P009(0.80) error. I have tried multiple factory resets, pairing it on a new home and have checked the wifi network but still no luck. I currently have one other nest protect which is connected fine.

Thanks

[Sparebrain]

For what it’s worth, I’m having the same issue today. Have multiple Nest protects. All were working fine. Updated my wifi network name so doing factory reset on Protects in the house. Setup the first one fine. Went to setup second one and it didn’t work (getting same P009(0.80) error). Tried multiple factory resets, reset router, reset app, reset phone. Nothing works. This specific Nest Protect was working on the same router earlier today (before I updated network name). Something strange is going on. Will try to add another one upstairs. 

using Google Fiber

2nd gen Nest Protects. 

[Sparebrain]

Getting same error on 3rd one I tried to setup. This is extremely frustrating. 

[corbind]

Mine also is giving the same error today. I wonder if it is a server issue?

[Sparebrain]

Perhaps. I’ve tried everything else I know to do. Weird that the first one I setup worked fine…a bit slow to “finish” but it worked. Went to 2nd one and that’s when I started getting error. 1st one is still connected. Hoping it’s just a Google Service issue (even though they show all OK). 

[corbind]

Exactly what I'm seeing too!

[nicksab96]

This is the same exact issue I am having today. Looks hoping that a fix will be in place soon.

[corbind]

I fixed the problem for my system. I bought 6 Protects. Day one I installed the first one and it updated its firmware to 3.5.0.3. Day 2 I attempted to install the others (v 3.4.0.6) but none would connect. I tried removing the first one (v3.5) and re-adding it; that always worked, but the others wouldn't connect. I finally removed the first (v3.5) and added some of the older ones (v3.4) and then they all could chain connect. 

I did also change some router settings, but they didn't seem to affect it. specifically, turning on IPv6 and multicast. 

[Levic]

@Sparebrain your issue mirrors mine completely. Did you ever find a workaround? Mine all seem to be the current firmware so I can't try adding those first.

[Spurgeon]

Same error here, Did anyone succeeded?

[zoeuvre]

Hi everyone, 

I’m sorry to hear you’re all having issues adding your Nest Protects in the Nest app. Let’s sort this out. Can you try the steps in this guide?
 

1. Reset the joining device to default.
2. Restart the modem and router.
3. Move all devices being used for pairing closer to the router.
4. Check the network settings.

Please let us know if that helps.

Best,

Zoe

[Jake]

Hey all,

I wanted to check in and see if you managed to see Zoe's post. Please let me know if you have any questions from here. I would be happy to assist, and make sure you are good to go.

Best regards,
Jake

[Sparebrain]

@zoeuvre  / @Jake 

I did try all of those steps. See abbreviated first post above.

I have not tried to go through the setup since my last post...but will try again tonight and see if things have changed or if I get the same error. I'll circle back here with any updates.  I may also try what @corbind suggested above about removing the first one I connected (it's still connected) and add a different one to see if they all chain connect.

[Jake]

Hi Sparebrain,

I wanted to follow up with you. Were you able to troubleshoot the devices? Let me know if you have any new details, as I want to ensure you are good to go.

Best regards,

Jake

[Sparebrain]

@Jake / @zoeuvre

I was finally able to try adding the remaining Nest Protects to my new WiFi network today and everything worked. No P009(0.80) error.  What was different this time was that the first one I tried adding was able to use the network information from the first one I added 2-weeks ago.  Below is a summary of what I did in case it helps anyone in the future:

1. Two weeks ago, we updated our WiFi network name which was different than what our Nest Protect (NP) devices were using (thus requiring me to add them to the 'new' network).
2. I was able to add the first NP to the new WiFi network without any difficulty.
3. When I went to add the second NP, I received the P009(0.80) error...thus my initial post above.
4. I tried multiple strategies found online, but none of them worked. These strategies included the following:
   1. Erase the data on the NP I was trying to add (holding down button for 10-seconds, etc)
   2. Reset my router/modem. Check network settings. Putting NP near WiFi router, etc.
   3. Reset my phone Nest app...logout/login, close the app, etc.
   4. Turn off my phone, turn back on my phone, etc.
5. The combination of the above steps did not help no matter how many times I tried the exact steps above and variations of the above steps. I kept getting the P009(0.80) error. 
6. So I waited...the second NP set on my dresser for the last two weeks. I did not do anything else with the NP.
7. Tried again today...and it worked.  The difference was that it automatically detected the first NP (added two weeks ago) and used its network settings to add the new (second) NP.  Two weeks ago, when I was trying before, I had to select the new network, enter network password, etc...but not today.

My guess is that it just needed time.  Perhaps the first NP that I added needed to refresh to the Google Nest servers(?) or somehow otherwise sync with my network in order for the second NP to recognize it and 'borrow' its network settings(?).  Who knows...but I have successfully added all other NPs in my home (6 total).  All is working as expected at the moment.  My advice to anyone else having the same P009(0.80) error after adding their first NP...wait...just let things sit for a while and try again later. For me, that was two weeks...but I hadn't tried again until today so perhaps it doesn't take two weeks for others. Hope the above is helpful to others.

[zoeuvre]

Hi folks, 

Awesome! I'm glad to hear that everything has already been sorted out, @Sparebrain and thanks for sharing to us the steps you did. 

@Harrynewzealand, @Spurgeon, and @Levic, can you try to follow the steps that Sparebrain did? Let us know if that works.

@corbind, how's it going with your Nest Protect? In case you have an update, let us know and we'll be happy to help.

Thanks,

Zoe

[zoeuvre]

Hi everyone, 

We haven’t heard from you so, I'll go ahead and lock this thread within 24 hours. If you run into any more issues in the future, please feel free to create a new thread.

Best,

Zoe