Cannot connect Nest Protect back to wi-fi

[trainman52]

Two of my 3 Nest Protects dropped off wi-fi for no reason. In attempting to reconnect them the dreaded error code P024(4.8). I tried all the suggestions to no avail. Spoke to a Google/Nest assistant. She couldn't resolve the issue. She connected me to the next-level assistant. She couldn't help me either; told me she would report the issue to the developers. From what I have seen about this issue and the dates posted, either the developers can't find the answer or they have given up. One YouTuber suggested taking the batteries out of the Protect not being programmed. That didn't work for me. Another suggestion was to delete the Nest doorbell add the Protects and then add the doorbell again. That didn't work either. Another suggestion was to add a second "home". Why? I don't want to have to switch between homes. And that didn't work in my case. Google/Nest can hire the most talented engineers. Do that and get this issue resolved for me and the many other individuals who have contacted Google/Nest over the years. Thank you

[cyber2steve]

We all need to start a class action suit, because the products are defective. I have devices that are 2nd gen , manufactured in 2022 that won't connect and this bug from Google is a danger to my family and I.

[Jonyeo]

I agree I have over a $1000 worth of smoke detectors that are useless 

[cyber2steve]

I have $750 worth of these detectors that are useless and now I have to be looking to finding an alternative brand for safety reasons. I should have known something was up when they separated the thermostat from the Nest app and put it in Google Home, then tried to keep the thermostat and detectors link together through the two different app.

[AndersC]

Hi @OptimistPrime,

Thank you for the update. I'm glad to know that you were able to fix this and your devices are working as designed. I also appreciate the tips you shared in this post so the rest of the Nest Community members can learn from this inconvenience.

@nestisbroken, I understand your point, and I apologize for the inconveniences you're experiencing. The team would like to learn more about this behavior. When you get a chance, please fill out this form and let us know when you’re finished. We’ll have someone reach out to you via email from there.
To help us assist you better, please include the link to your Community thread and your Community username.

Don't hesitate to reach out if you need help or have more questions in the future.

Regards,

Anders

[nestisbroken]

I doubt that OptimistPrime's Nest Protects are all 'working as designed'. Interconnect and push notifications are both broken.

I did reach out to Google Nest support, had a support ticket number, supposedly had it escalated to senior support staff, but nobody was able to resolve the problem. Do you have reason to suppose a new ticket # would fix anything?

[OptimistPrime]

FWIW, while all of mine are finally working.  I found a battery operated one that had been laying around, replaced the batteries and it does not work. 

I think it's significant that I was able to re-add all of mine at once but it seems what issue is preventing it from occurring is intermittent and I believe happens on Nest's side. 

[nestisbroken]

Are your devices sending push notifications? Can you start a remote safety checkup? Are yours all wired units?

[Biggus]

You're on the right track. Whenever I can add the first Protect and force it to do a network test it will claim it passed and show the green ring. However I'm staring at the MAC in my Unifi dashboard and watching 0 bytes to/from it. Tell it to perform the safety check within the app and the app claims it completed successfully meanwhile I've got the **bleep** Protect in my hands and it never made a sound or gave any indication it was alive at all. So the safety test wasn't performed at all. The Protect does still function as a smoke/co detector at least, I've just wasted a lot of extra money buying these instead of literally anything else for much cheaper.

[Biggus]

I'm ready to take a dozen of these and toss them into a fire. Same exact issue.
One randomly went offline. By the time I've finished all the stupid troubleshooting I have:

A new Google home, all of my products removed. A 2.4Ghz wifi network with ipv6 enabled. If you're reading this you've probably found the same "advice."
I can add a single Protect. I can never add another. It doesn't matter which of the 12 I own any of them will connect, but once that device is used to add another it fails. P024(4.8) every single time. NOTHING I have read or advice from Google online I have followed has worked. These pieces of garbage are no better than cheap disposable units you can grab at a grocery store.

[fthreef]

Same! Chasing my own tail with the factory resets, new 2.4ghz only network, ipv6, new batteries, etc---none of it has allowed for a second Protect to be added. Should have never tried to troubleshoot the one that was acting up. Hoping Google can give us some insight one way or another soon, as having so many expensive "smart" smoke detectors stuck on dumb mode is not what we paid for.  

[adobopete]

Your scenario is exactly what I experienced today. Called google support and they got to where you are and told me to change settings on my router.  I've tried everything everyone on this thread and many others have suggest.  Troubleshooting for over a day and can only add a single Protect no matter what I do.  I'm about ready to throw them in the garbage and find an alternative product.

[Jsh415]

Senior tech support wants me to replace one of my protects with a new one via RMA and then remove everything from the structure and start over while they are looking at logs. So they are at least trying to help. I have little faith but am going through the motions anyway. Will report back how it turns out. 

Are there any other products in this category that are worth a look?

[Wontprotect]

@AndersC Has there been any communication within Google about this issue. I too am experiencing the same issues as the others in this thread and am frustrated my 3 protects no longer connect.  

My Google Fiber was suddenly running slower so they sent me two new routers (WiFi Pro). What they didn’t tell me was I would have to delete all connected devices and rebuild a new network.  This created a couple hours of unexpected work but what is most frustrating is only one protect connects.

Years ago I made the conscience decision to go with all Google Nest products because of the integration, now it seems that was a mistake and deeply rooted issues are coming to light.  

I’d like to think Google will acknowledge and fix the issue or do the right thing and give me my money back. 

[trainman52]

Update....after reading the latest posts, I tried again to connect more than one Protect to my Nest app.  I could not. I still got the PO24(4.8) error message.  Having a multi-story house, I chose to connect the Protect that was on the middle floor. This was prompted by reading the post about burning up if there was a fire. Additionally, the Protect that is connected to the app, even though the app says "everything is okay" will not respond to a system check to test the alarm. I have to conclude, if, there was a fire in the house and I was away, I would receive no notification. Yes, I agree a class action suit may be necessary, not only to reimburse us the cost of the Protect, but also for the hours we have spent trying to get the device to work. Apparently, Google doesn't care as there has been no public reply to all the posts about the Nest Protect. And Google has so much money, a class action suit would be pocket change for them. 

[bonerfortuna]

Add me to the long list please

[trainman52]

you are added

[stormvoice]

I too am having the issue.   2 Wired and 6 battery Protects.   Only 1 can connect and no others.   Did all the suggested solutions... nada.   All cannot connect.   Worked with support for several hours with no solution but to create a "home" for each one.   Um...   not doing that.    Nothing changed on my side.    Looks like they Crowdstriked their platform.   Add me to the list!

[cyber2steve]

I don't think putting each detector in it's own home would still let them interconnect since they are in different homes...

[ramshock4932]

Same issue here P023.  No network changes just decided to drop from my network on 2/21/25

[b4tm4n]

Same issue, All gen 2.0 I have 6 of them Wired.  One will connect. then when trying to add any others I get P024(4.8) All were showing offline after a modem swap CONICIDENTALLY******2/21/2025*****.  I realized all the Nest Protect devices were connected to a different network due to the **bleep** wireless configuration.  Ie.. Only working with WPA/WPA2 - Personal and 2.4GHZ not 5 GHZ (online says they will work with WPA3 but this is untrue.)   I removed all Nest Protects (since they were all offline) REST ALL OF THEM.  only One can connect, trying to add any others result with P024(4.8)  I had had their products since V1 and been very pleased, this needs to be addressed as many have stated if there is a fire they all wont relay that there is a fire since they are no longer connected.  If there was a way to MANUALLY add each one that could work, it seems to be an issue when trying to pass the network config from the "CONNECTED" one to the new device. 

[stormvoice]

I'm actually surprised it took so long for their actions to catch up to them....    From CNN in January 2024...   

The layoffs are also hitting the hardware division that produces Google’s Nest, Pixel and Fitbit devices, with many of the cuts affecting Google’s augmented reality team, the company confirmed to CNN on Thursday.

My guess is they pushed a defective firmware update that wasn't tested and they have no idea how to fix it because all the people that wrote the original code are gone.   It was a good product while it lasted.   

[cyber2steve]

I think that's a good observation and may be the reason they can't fix the problem.  These are expensive detectors and now they are just a regular non-interconnected device...

[cyber2steve]

I have been researching replacement brands for my smoke and Carbon detectors and a brand called X-Sense has good reviews all over and are about 1/4 of the cost of the Nest detectors. Their WiFi version uses a base, you can also run checks and silence the alarm from the app. 

[RobRichards]

Im also getting the P024(4.8) error just trying to add a Nest Protect to my existing 7 Nest Protect network. I’ve replaced Protects several times before without any issues and I’m real curious how there can be a code (P024(4.8)) but no information that exists on the code. I’m running an EERO Pro 6 wireless network. 

[OS3]

Same issue as everyone else.  Four Nest Protects and only able to get one to connect to the app (is it truly connected?).

[stormvoice]

Anyone having the issue of connecting more than one Protect to a home, getting them to talk with each other, P024 (48) etc...    what is the software version you are running on your Protect(s)?    I am running 3.6rc6.  

[OS3]

I am also on 3.6rc6 and having problems.  The issue started for me when I rebooted my Wifi.  Previous to the reboot no issues with the four Protects and thermostat.  Only able to connect one Protect and the thermostat (Nest gen 2).  As per another post, not sure if the one Protect would even provide a notice to my iPhone is there was an issue.  The three non connected Protects now are not able to provide a "night light" when you wonder by one at night!

I noticed a post from 2022 from "support" that said to locate all the Protects next to the router and then reinstall.  Anyone tried this?  As I do not wish to climb up a ladder to remove them all and find out that this is a non-solution.

Where is Google and their support staff in correcting these bricked Protects??????

[Jsh415]

I’m on 3.6rc6 as well.

[cruisemikE]

WELL, I see I'm not alone in experiencing this "I can only add 1 next protect to my Nest App"!  My problem started just a few days ago and tonight I've spent nearly 5 hours trying every conceivable solution - and none of them work.  This is a huge Google problem and certainly needs an immediate fix.  What a disappointment for this to continue unsolved.  😞

[nestuser1827371]

Having the same issue.  I did some packet captures when trying to register a new Nest and it seems to fail when the other "helper" Nests try to communicate back to the app  on 11095/UDP and it throws an ICMPv6 "Port unreachable" and the whole thing stops.  One Nest Protect works ok because it skips that process.  My best guess is something in the latest firmware changed the behavior and now we're seeing the consequences.  I'm going to wait for either a new firmware or mobile app update as I don't think this has anything to do with wifi configurations or anything on the user side

[cruisemikE]

I agree.  I've spent too many hours reviewing every conceivable solution only to come to the same conclusion you mentioned: wait for Google to fix this problem they, in all likelihood, created.

[cyber2steve]

When you try the detector that is connected, did you also see that even though the home page of the app is showing connected,  if you click on the detector it is showing that the last it was connected was when you installed it to the app???  Also if you go to the page for "checkup" you will see that the detector cannot be reached...

[Jonyeo]

Yes , I tired that no difference 

[b4tm4n]

This is the problem right here 👆Great job troubleshooting NestUesr18276371.  I called and spent about 45 minutes to an hour with Google support how had me try so many different things all resulting in the same issue.  I even said can't you make it skip and allow manual network configuration that would fix this issue.  he said there was no other workaround.  I guess we wait for an update.  they said my issue was going to be escalated and he got all the required information, that was Thursday night, and I haven't heard back yet.   

[cyber2steve]

Try adding each detector in it's own home. They won't interconnect but you will still get notifications on the app when they trigger. 

[nestuser1827371]

Looks like my devices got a recent bump to version 3.6r8 and it's resolved the problem for me.  I was able to remove devices from the temporarily created homes to the main account and the process worked as it did previously.  Hopefully it stays this way, just wish I could prevent automatic firmware updates....

[OS3]

Thanks for advising.  Checked my one connected Protect and received the same update.  Also able to connect my two wired and one battery Protects to one Home.  Safety "Checkup"  also working correctly. 

Yahoo!

[cyber2steve]

How did you move it? Did you deleted it and start from scratch in the home that you wanted it in?

[scdemanett]

Can confirm that update fixes it for me as well. Have to get each one online to update first but holding the Nest Protect button until is says "checking the network" seems to force the update once connected.

[OS3]

I noticed a post from 2022 from "support" that said to locate all the Protects next to the router and then reinstall.  Anyone tried this?  As I do not wish to climb up a ladder to remove them all and find out that this is a non-solution.