04-21-2023 10:26 AM
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?
Answered! Go to the Recommended Answer.
04-29-2023 07:40 PM
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?
04-21-2023 05:28 PM
I’m experiencing the same issue. All of mine fail to connect with p009 error. I’ve made all the necessary changes to my wifi as well. Please fix this Google.
04-21-2023 10:20 PM
same here 😞 I even returned the first nest protect thinking it was defective. Grabbed a replacement, same deal, error - P009(0.80) Always happens right at the end of adding the device. From what I've seen the support folks just close alot of these threads, clearly is a major issue, not sure why not investigate this issue.
Lets wait for one and see what happens
04-22-2023 01:22 AM
Same here... last step (adding the device to your account) fails. Could it be possible we have to connect our NP to our computer and do a firmware update? What is your version number people?
04-22-2023 01:24 AM
I'm on 3.4.1.1
04-22-2023 01:54 AM
Firmware 3.5.0.3. Same issue as everyone else.
Does factory reset take NP back to factory installed firmware? If not is there a way to step back a version. Obviously we now can’t get an over the air update can’t connect wirelessly. Port on back of device?
04-22-2023 03:02 AM
Maybe the WiFi config is added because it's only the last step that fails, which is adding the NP to the account. We may still get OTA updates. Have you tried connecting the NP using the port on the back to a PC?
04-22-2023 08:49 AM
I haven’t yet. Will wait for possible solution from google/nest first. Also don’t think I have a cable and unsure if proprietary protocol used.
04-22-2023 03:05 AM
My NPs are on 3.4.1.1, and they experience the same issue. The final step (adding to the account) fails. I do hope we get a new OTA update soon.
04-22-2023 01:02 PM
Factory reset (holding button down for 10 seconds) does nothing. Did it multiple times. Same outcome.
Ive had a older nest protect which expired and i repurchased a new one as it was so easy to use…. Clearly someone dropped the ball on this firmware or hardware as its next to impossible to add to the network. Which sucks cause these units start to expire as soon as they are packaged up by google.
pretty much bought a unit thats is losing valuable time each day, and we cant even use it
04-22-2023 01:08 PM
Just to add, my nest hello, and nest thermostat have all been working. Went with this company as i lived how everything can be connected under one app. So its def not the network or anything else, this problem is on nest’s end. Dont even bother wasting hours trying to troubleshoot the problem on your end. Spent majority of my day yesturday doing all the recommended troubleshhoting steps.
Even reset my entire network, split 2.4 and 5 ghz signals separately. Removed the app on my phone re downloaded it. Tried different devices with the app. Nothing worked
04-22-2023 03:01 PM
I'm getting the same error. Just bought 3 Protects today and I cannot get any of them to added to my main "Home" within my account. Just to see what would happen, I set up a separate home with only the Protects and that worked. Having 2 homes set up in the app is not a solution as it defeats the purpose of buying devices specifically so they can communicate with each other in an emergency.
04-22-2023 05:56 PM
The other threads detailing this issue are hilarious. No one from google actually engages. They wait for a community member to resolve the problem then close the thread.
04-22-2023 06:37 PM - edited 04-22-2023 06:38 PM
LOL, i know right!
Its like they dont engage the chat until someone mentions a possible solution. Then its filled with google support asking for people to try it and then they close the thread. Usually its a patchy fix that really doesn't seem to be a permanent fix.
04-22-2023 07:03 PM
I just received mines yesterday and I'm sad to see a lot of people have the same p009 issue.
04-22-2023 08:35 PM
DM40 fix does work, i just tried to create a new home within the app and use that to successfully add the protect. So it seems its not a network issue. Something on their end forsure.
04-23-2023 06:49 AM
Got my protect added. Not having all nest products under main home is annoying. Google please fix this
04-23-2023 07:28 AM
Did you have to remove all other nest devices? Including any nest devices in the Google Home app?
04-23-2023 10:43 AM
I caved in and moved all my devices to a new home, had to factory reset my nest hello and nest thermostat. Just to find out you cant use your nest aware when you create a new home, tell you to pay for a whole nee subscription. FML
04-23-2023 08:35 PM
Not a great solution, but I was able to add without creating a new home by removing the 2 existing devices, adding the nest protect and then re-adding my other devices. It's a pain, especially if you have alot of devices, but it works.
Google please fix this.
04-24-2023 05:52 AM
Wow, that would mean removing several cameras, a doorbell, and several smart plugs. Not something I am keen on doing in a hurry.
04-24-2023 01:35 PM
I understand. Creating a new home or removing existing devices are both just workarounds, not solutions and is very inconvenient for those like yourself that have many devices.
05-03-2023 07:49 PM
What devices did you remove? I have a doorbell and thermostat
05-03-2023 08:16 PM
I only removed the doorbell. I left the thermostat and my camera.
05-26-2023 07:38 PM
For us it was the doorbell. Once we took that off all 6 protects set up easily.
04-23-2023 10:25 PM
@JBru77 Thank you so much, this resolved the issue for me (I was getting a P009 (0.80) error setting up a Nest Protect as well). Out of curiosity, what were the two existing devices you already had on your home?
04-24-2023 01:38 PM - edited 04-24-2023 01:38 PM
Just a thermostat and a doorbell, so it was inconvenient but if I had more devices it would have been much more painful. But it's an alternative for those that have an aware account and/or don't want to create a 2nd home.
04-24-2023 11:40 AM
Same here. Error P009 at the end. Factory reset multiple times, used 2.4GHz, held my mouth correctly, nothing works, used appropriate adult words... I have 15 other devices and not the time to remove and rebuild my home. I will give it a couple days for a fix through here and then I will return the 3 NPs I bought.
Impatiently waiting.
04-24-2023 11:57 AM
There is a workaround that worked for me. Also mentioned above I think.
In the nest app add another home. Same details as the home you’re in already and then add the Protects in the usual way. Seems to work. It’s a little bit rubbish and hopefully works with alerts going to same account etc.
04-24-2023 07:43 PM
If you have a nest aware, it will ask you to purchase a whole new subscription when creating a new home. Its anther headache.
I creating a new home and moved all my devices over, ruined my sunday just find that out
Atleast i can try Jbru77 fix now, since my original home is now empty lol
04-24-2023 08:03 PM
I agree, it works but is a cheesy way to get these expensive devices to work. I hope there is a fix so I can add them to my main House.
04-25-2023 08:18 AM
Let's hope Google starts to notice our conversation here. Maybe we should post ad nauseam?
04-25-2023 10:40 AM
I agree. This is something that Google should be able to fix on their end.
04-25-2023 12:22 PM
This probably sounds nuts but I’ve had the same issue. Use brand new batteries!!! Also, if setting up from scratch, connect the first one, the use that to assist the next one. Once that’s set up pull the batteries from the first and use the second one to assist the third and so on. But my biggest belief is that if the batteries are even six months old they are not powerful enough to connect to the Wi-Fi and it fails.
05-26-2023 07:41 PM
If you have a doorbell on the system try to remove it then do the protects. That was the trick in our case. We switched to a new internet provider hence having to re-add them.
04-25-2023 11:14 AM
Luckily most of my devices were already configured using Google Home, so I only had a doorbell and 1 IQ camera to delete. I can confirm that after deleting those, I could already add the first NP to my account.
04-25-2023 11:56 AM
Update: I have successfully added my 4 NP, and they all show WiFi connected (all checks are green, and before, there was a red x next to WiFi). However, when I press one, it says that some NPs are offline. I believe he is still referencing the old configuration.
04-25-2023 01:30 PM
I am new and trying to set up the first of 4. I get the same error and this device has the previous software
04-26-2023 04:54 AM
Same issue for me, bought new Nest Protect and get the error P009(0.80) at the very last step.
Tried adding to a new home and that worked, but I want to add it to the current home without moving everything and I have Nest Aware.
04-26-2023 11:09 AM
Hi everyone,
I know it's been a while, and I’m sorry to hear that you’re having trouble with your Nest Protects.
Please follow the steps below:
Let us know how that works.
Best,
Zoe