P.009(0.80) Error

[blingerf]

Trying to add nest protect to profile. Gets all the way to the final step then fails. From other threads it appears this is a bug in the firmware update 3.5.03. Is google actively working to correct this issue? Is there a way to revert pack to previous firmware versions?

[Grandgt]

Hi @zoeuvre, that fix did not work for me.

i reset my modem/gateway- factory reset the protect, moved it 4 ft away from my router, and it failed. When i created a new home its adds successfully regards of my home network or distance to the wifi router.

It seems rather that a certain nest device already added/paired in the home is causing that error when adding the protect. Thats why we all can add it under a new home and it works. 

[Chucky44]

I was able to successfully add my nest protect today by removing all Nest devices from the Nest App (nest device only, not Google Home) and added the Nest Protect as the first device and it worked.  I then went and began to re-add the other devices again, started with the doorbell which for some reason acquire me to select the nest protect button it so it can connect to it again then tried to connect the doorbell after, even though the Nest Protect was added already.  Not sure if it uses it as a doorbell chime, which might be the reason it didn't want to connect the first time.  Then I added my other Nest Camera's one by one.  What a nightmare to go through this for just adding a simple device.

[Emperor]

Yes @zoeuvre the only thing that works (if you want to keep your existing house setting) is removing everything and adding the NPs first. It’s a very annoying workaround definitely if you have numerous devices. 

[rhapsody]

That is a nightmare situation. If you have more than 20 devices and they're mounted in inaccessible areas that is not feasible.  Google-- please release a working firmware for these protects!  Its past due.

[Daniel72023]

I have tried all the steps in the help to add these smoke alarms. Obviously by the posts here, Google knows they have a problem. The only way to get these things to add to our account, is to create a new home. That is not a solution at all. We have 8 other Nest products and I am in no way excited about removing them all, and starting over. I will however be doing exactly that, because it is possibly less trouble than returning the three Nest Protects we just purchased, and going with another product. 

That said I don't think I'm going to be as generous with my recomendations of google products in the future and may possibly be looking at other products for our family. 

For the price of these products they should work seamlessly and when for some reason they don't the company should fix the problem not spout bs about moving things closer to the router or reset the device. 

[JBru77]

Now coincidentally after getting it all set back up my nest thermostat battery won't hold a charge.

[Grandgt]

Be nice if they could bump this thread to the top, new ones being created by other users having the same issue. Hopefully google support actually looks into this as we all can see its becoming a bigger issue

[Grandgt · Accepted solution]

After messing around with the devices, im pretty sure this error is caused by the nest door bell. For those having the issue do you have a nest hello doorbell? Can someone can try to remove only the nest door bell from the account and then try to add the nest protect. See if the error goes away when pairing?

[DM40]

I can try that tomorrow.

[Emperor]

I do have a nest hello. But I can’t verify if only removing the nest hello is enough. I deleted everything first and started over. Not going to repeat the process now 😀

[DM40]

That was it! I removed the Hello but kept the other camera and thermostat and all 3 protects paired without issue.

[Emperor]

Thanks for the update. Next time this happens I know I will just remove the Hello doorbell. 

[blingerf]

This did it for me as well. Was able to add the protects and then add the doorbell back at the end.

[htypelet]

This worked for my install as well.  How bad was this firmware update that it requires you to remove other parts of your system to work?

[rhapsody]

I removed the nest hello/door bell and the protects still error out even after resetting.  

[ric67]

same problem with my nest protect error code 009 I remove my nest camera in my home account then try to add NP boom solve the problem. I add my NP with out error

[bernhardlenz]

Same issue for me. I'm hesitant to remove my Nest Doorbell just to install the Nest Protect as the Doorbell has tons of faces stored and I don't want to loose them. This issue plus that Nest Protect doesn't work with 5Ghz networks makes me lean towards returning the Protect. @zoeuvre is there a fix in the works? 

[Chucky44]

I removed my doorbell to install it and it didn't delete the faces stored for Nest.  It did delete the History videos for my doorbell though.

[Grandgt]

I can confirm, it kept familiar faces saved aswell for me after i added it back

[Toddrich]

What a PIA! I removed both cameras, factory reset all 3 of the protects then added the cameras back.

Issue 1: For some reason one of my Protects has a yellow ring on the app. It says, "Couldn't verify the alarm sound. Couldn't verify the voice". I ran a test but it still says this. Do i start over with it?

Issue#2: Will Google Home show the Protects eventually? 

Thanks Google for the loss of time .

[Toddrich]

Cancel issue #1, I removed it then readded it and it shows green on the app. Who knows why? 

[zoeuvre]

Hi folks, 
 

I know it's been a while, and I’m sad to hear that others still have the same situation. I’d like to take a look at this more for all of you. 

@Chucky44, @DM40, @Grandgt, and @blingerf, I appreciate you being ahead of the troubleshooting steps and I’m glad that everything has been sorted out. 

For others who still have the same situation, aside from connecting the troubleshooting steps stated above, if you don’t want to remove your Nest Doorbell as others did, you can also check the network settings of your router by checking this article to learn more.

Let me know how it goes. 

Regards, 

Zoe

[JBru77]

Zoe,

Thank you for the response, but many of us verified the network settings from the article mentioned and that did not fix the issue.

The issue is related to the nest hello(doorbells). For whatever reason, having the nest hello set up in the home app prevents adding the nest protect to the home app. After removing the nest hello the nest protect connects to the home app immediately. 

[zoeuvre]

Hello everyone,
 

Don't give up on us yet. We'd like to further check on this. Could you fill out this form and let me know once you're done? 

Thanks,

Zoe

[DM40]

Hey Zoe,

FYI the NA009(0.80) error with the Nest Connect is also solved by removing the Hello doorbell from the app prior to setting it up just like the Protect. 

[gipnyc]

This did not work for me. I have 2 Hello Doorbells and removed them, and I still get P009 (0.80). I also have 2 cameras (1 first gen and 1 IQ) that are remotely mounted I cannot afford to easily delete/readd. Now I have to go back and dismount 2 doorbells to re add them. Lots of fun and hours lost. 

This is a bit ridiculous. This ecosystem gets worse by the day. Also had a Google Home outage last week where Nest Hubs could not play media. Additionally, I've not been able to join Google Home preview. All these errors are a joke!  😡😡😡😡😡😡😡

[rhapsody]

any updates on this??? many of us have tried everything on here and nothing works. This appears to be a backend issue with Google/ Nest and a firmware that hates the Nest Hello. 

[Temmy]

Just to add to this, I've just changed the Wifi setup in my house which meant a bunch of Google devices needed to be reset. I also couldn't add my Nest Protect (3.5.0.3) and kept getting P009 at the last step.

The only way to fix it was to remove the doorbell first, and then add the doorbell after the Protect.

Google needs to do a much better job. Problems like this should not exist.

[rhapsody]

once you have one protect successfully added can you re add the door bell and then re add more detects easily?

[Chucky44]

Yes, I added the Doorbell again after adding the nest protect. I bought another nest protect the following week and added it no problem. 

[rhapsody]

I tried this workaround.  I had no luck.  Even after removing the nest doorbell, the nest protect could not be added. I reset the NP, I restarted the router, I tried only using 2.4ghz, I crossed my fingers and toes and counted to ten while holding my breath. 

This is insanity and Google should have fixed this last month.

WHAT'S THE DEAL GOOGLE? 

[rhapsody]

any updates to this?  This is crazy to buy a new device and they all won't connect. 

[JP76]

I also have this error P009 have try everything even removing nest hello door bell and no luck in re-adding my nest protect back to my account

[rhapsody]

Thank you for chiming in.  The more the merrier.... 

Google an update on this would be super. 

[gipnyc]

It was madness. Removing the doorbell(s) on my account did not help. I had to create a whole new home, start with the Nest Protect and then get up on ladders to readd my cameras, thermostats, etc and then move dozens of light switches and other integrations. It also lost all my Nest Aware video recordings and familiar faces in the process. 

Really nuts, but now I have everything together.

[JP76]

I'm not about to remove all 25 device and keep going up and down the ladder just to see if i can re-add the nest protect again. 

[rhapsody]

Yea, especially as there's no guarantee even that will work.   They can fix this on the back end. 

[htypelet]

It has to be on the backend too.  I tried another SSID on another VLAN, still the same result.  I tried another router, fully disconnecting my current setup, same result.  The only commonality is the backend, everything else was changed.

[rhapsody]

I most logical is a backend issue, maybe also related to a firmware issue as well... but... regardless they can fix this on their side.... 

[JP76]

I read some said it was firmware, have try searching away to roll back with no luck. If it is firmware hope they provide us a way to update the firmware since we cannot connect the device to online