09-03-2023 08:52 AM
How infuriating.
I just bought two nest protects to replace my old Smoke and Carbon Monoxide detectors. I figured having a "smart" solution for protecting my home even when I'm away could only be a good thing.
I've tried for an hour to get these two Nest Protects added to the same network. You add one, great. That's on the network.
You try and add the second and it's like you're asking the impossible. You always get a P030 or P024 error when trying to add the second device. Even when they are next to you, you're sitting next to your router, and you've followed the instructions to a tee, nothing.
I've tried:
Nothing works. It's been less than 2 hours since they arrived and I'm about ready to pack these up and send them back to Google. If I can't even get their products to talk to each other how the hell am I supposed to trust that they'll tell me when something is wrong?
Why has the product design team decided that they needed to talk to each other to join the same network? Surely that should come AFTER they're on the same network and registered against the same nest account? How did this pass QA?
Answered! Go to the Recommended Answer.
09-04-2023 11:20 AM
I just had a nice chat with Google Support. Basically if your router doesn't support IPv6 your network can only support one nest product. I have a basic router supplied by my ISP (Virgin Superhub 4) that doesn't support assigning IPv6 addresses, so I guess my options are:
It's odd that as far as I can see this key piece of information is not published anywhere. It's not in the manual, product page, Nest documentation, Nest App, Nest error code documentation, Google Store page or any of the community forum posts that pop up when you google "Nest P030 error" or "Nest P024 error".
Hopefully this information helps someone, or at very least saves them time.
09-04-2023 06:32 AM
Similar issue as you. I've installed a new modem/router and all my Protect products are offline. I've tried all the suggestions and nothing work.... no one here to help... spent three hours already
09-04-2023 10:28 AM
Since the first post I've also tried
Nada, zip, nothing.
And ofc, not a peep from their community support.
What a massive waste of time and money.
09-04-2023 10:57 AM
I'm having the same problem. I tried the same things and then tried my partners phone, just in case. I have 7 of them sitting iny house, and only the one is working.
09-04-2023 11:20 AM
I just had a nice chat with Google Support. Basically if your router doesn't support IPv6 your network can only support one nest product. I have a basic router supplied by my ISP (Virgin Superhub 4) that doesn't support assigning IPv6 addresses, so I guess my options are:
It's odd that as far as I can see this key piece of information is not published anywhere. It's not in the manual, product page, Nest documentation, Nest App, Nest error code documentation, Google Store page or any of the community forum posts that pop up when you google "Nest P030 error" or "Nest P024 error".
Hopefully this information helps someone, or at very least saves them time.
09-04-2023 01:04 PM
Hey @CR1128
This is listed in the help centre but is a bit hidden. You can find it in the "7. Check the settings on your Wi-Fi router or access point" section here:
Can’t connect Nest Protect to the app or Wi-Fi - Google Nest Help
I’d encourage you to also send this feedback directly to Google. You will not receive a response, unless Google need more details from you, however the team are still reading the feedback. In addition, I've flagged to the community team it would be beneficial to consider including this kind of information in the main setup help article.
09-04-2023 01:23 PM
@David_K If an IPv6 capable router is a pre-requisite to having a functioning network of Nest IoT devices then it really shouldn't be hidden. Surely Google appreciates how frustrating it is for their customers and how damaging to their customers trust a problem like this is.
I notice on the linked page that error codes P030 and P024 are not featured on that page either. Meaning nobody stood a chance of equating the error codes provided to a network protocol issue.
I still don't understand why IPv6 is required for a home IoT device. I don't think any home is in any danger of using up every IP address on their home networks subnet. It seems like a weird line in the sand the Nest product team made for seemingly no reason at all.
09-23-2023 05:27 AM
I have the same issue (P30) with a twist. I have 3 Nest protect and all worked for 5-6 years without any problems. All of a sudden 2 dropped off from the network and I cannot reconnect them. The third one works fine. I did not change my router, or anything in the router setting (IPv6). And although they claim that it does not work with 5Ghz, mine did work until now. I created a 2.4Gh network trying to solve the problem without any luck.
09-23-2023 06:10 AM
After a long struggle, I managed to connect all 3 Nest protect to the network (after 2 dropped off). I got the infamous P30 error code many times. It seems that the only way you can set up additional devices if you wake up the one that is already connected to the network. What I did, I got all 3 side by side, woke them up (blue ring circulated) and then finally all 3 (one by one, 2 separate processes) connected to the network. I have to say that the whole system worked well until the product was managed by Nest and not Google. Draw your own conclusions....