11-24-2023 11:34 AM
Hi. I am trying to connect the new 2nd Gen (April 2023 manufactured date) Smoke & CO detectors to my network and it's having a lot of issues. I had 6 x 1st Gen detectors in my previous house without any issues previously, and when I moved I picked up a brand new set. But these are giving lots of issues.
Problems I encountered:
1) The first smoke detector wouldn't connect to my primary mesh network with 802.11ax - no such issues with the 30+ other devices I have on this network. Read somewhere these units needed 802.11n, so connected to my guest network that's on a separate router with 802.11n and that worked fine. Annoyance, but ok.
2) Tried to connect my 2nd smoke detector, and the app forces me to connect to my 1st smoke detector, but not being able to connect properly (and yes, my android phone with app IS in the same 802.11n guest network for this part of the setup). The error code is P014. Sometimes I also see the app trying to connect to the 2nd new smoke detector and gives P021 (4.6) saying "check that the network you selected matches the Nest Protet network name shown in the back".
This is just so tedious. How can Google not have a good experience for something so basic. I literally wasted an hour of my time when this whole thing should've take 30 min for all 6 of my nest smoke detectors to setup. I do NOT want to create a 2nd duplicate address just to add these smoke detectors as a workaround. I see Google support suggesting this like a year ago and the fix is STILL not in? C'mon now.
Answered! Go to the Recommended Answer.
11-24-2023 04:21 PM - edited 11-24-2023 04:26 PM
So I fixed my own issue above. The "solution" was to use use one of my old Nest smoke & CO detectors that I had bought for my previous house years ago that was manufactured in 2019 as the main / primary. It was unused and sealed box item - so whatever firmware was running from back when. Accepted my 802.11ax wifi just fine and helped provision the creds to all the other "new" smoke & CO detectors. Clearly, Nest has somehow messed up the s/w in my current batch (3.4rc6 I believe). So a solution, but really a non-solution unless you have an old detector lying around.
11-24-2023 04:21 PM - edited 11-24-2023 04:26 PM
So I fixed my own issue above. The "solution" was to use use one of my old Nest smoke & CO detectors that I had bought for my previous house years ago that was manufactured in 2019 as the main / primary. It was unused and sealed box item - so whatever firmware was running from back when. Accepted my 802.11ax wifi just fine and helped provision the creds to all the other "new" smoke & CO detectors. Clearly, Nest has somehow messed up the s/w in my current batch (3.4rc6 I believe). So a solution, but really a non-solution unless you have an old detector lying around.
11-29-2023 11:33 AM
I would honestly return them all if you had to do that workaround to provision them. Nest is a dying ecosystem and thats a lot of money to have sunk in new detectors that arent going to gave the software support for that long.
11-29-2023 11:59 AM
Are you serious about no continued software support? That would suck. Did Google publish something about this?
11-29-2023 01:21 PM
It took them 3 years to rpely to a thread with hundreds of comments asking if they would do software development (to migrate to google home) and they only said "its on the roadmap." Then Google waits a bit for the thread fire to die down and they locked the thread.
There is no confidence they will maintain software for these detectors for another decade. And yet they continue to sell them.
(Just scroll thru a few pages of this forum. You'll see what's up.)
11-30-2023 02:09 PM
Hello folks,
@Phoeniyx, we appreciate your efforts in posting here your issues and concerns. We understand that you've been through a lot of steps and we're glad that it's resolved now. We’ll take note of it and ensure that we'll learn from your experience as we continually improve our products and services. Rest assured that we'll take this as feedback and learn from this to deliver a better process and experience in the future. Let us know if you have additional questions or concerns.
Thanks for chiming in, DanCoco.
Regards,
Emerson