Can't add a new (but old!!) Nest Protect

[Kreg0]

Hi there,

I just picked up an "old" Nest Protect (date 2015), but new in blister pack. Wanting to add protection in a bedroom this one would have done the trick for the 2 years it has left.
Unfortunately I can't add it to my account.
I already have a Nest Protect.
When I tried to add it from the existing Protect, I systematically got an error like : P019(0.65)

I've tried many things
Wifi 5Ghz
Wifi 2.4Ghz
Wifi band change
Wifi hotspot from a cell phone
Test from another router
Deleting my other Nest Protect
Create a new home on the app
Create a dedicated Wifi (2.4) with basic password just in case.
Deactivate all security (firewall, ips...)
Reset app.
Test from another freshly reset Smartphone

...

Impossible to add.
I get errors like :
Error P000 (0.65)
Error P008 (0.65)

If I reset/remove everything, I can easily add my first Protect

I have a big version difference between the two.
Not working (the new 2015 version) : 3.0.0.16
Working (my Protect already in place) : 3.5.0.3

How can I force an update? With the USB on the back ? I've run out of ideas other than that...

Thanks!

Kreg

[MplsCustomer]

@Kreg0 

You might be out of luck.

In four years as a Google Nest customer, I've never found a way to force an update of the firmware on a Google Nest device.  Google Nest seems to ONLY push updates out when they decide.  And that's when the devices are already installed.

There have been several recent posts from customers trying to install "new" (not previously installed) Google Nest devices that are several years old and therefore have out-of-date firmware.  It seems they sometimes simply cannot install the devices because the firmware is out of sync with the current software on the Google Nest app, the Google Home app, and/or Google Nest's servers.

[Kreg0]

Hello, ok I see. That's not a good news. it's a real shame

[MplsCustomer]

@Kreg0 

Well, I could be wrong, but I haven't seen anything in this forum indicating a way around out-of-date firmware when installing a "new" Google Nest device that's actually several years old.

[Kreg0]

What a beautiful consumer society we have.

I'm IT guy,  so I can understand the security aspect. But there should be an offline method to update this type of old equipments...

[EdmondB]

Hello Krego, 

I’m sorry to hear you’re having trouble with this. No worries; we'll check this out. For updating a firmware version on any Nest device, there is only one option, and you need to connect it to the Nest app. The USB on the back is only used to get the entry key code, just in case the QR code or entry key code is scratched. If the Nest Protect won't connect to the Nest app even using a mobile hotspot, this could be a problem with the device itself. Do you still have the receipt for this Nest Protect? 

Thanks for the help, @MplsCustomer. 

I look forward to your response.
 

Best,

Edmond

[Kreg0]

Hello,

I have once again tested from a 4G access IPv6, and it's still the same issue.
I have reset the Nest countless times.
I still get a P000 (0.65) error when setting up the Nest network.
Unfortunately, I do not have the invoice.
I do not think it is defective, I think it is just because the firmware is too old (3.0.x.x).
It's a shame. I will throw it away.

Best regards,

[EdmondB]

Hi there,

We deeply appreciate you sharing your thoughts and experiences, and we'll take it as feedback. We hope we can make it up to you in the future. Send us a message if you have any additional questions.

Best,
Edmond

[JPS23]

Did you use the NEST app (not the google home app)?

[Kreg0]

Yes... Of course...
If you had read, I have done many tests. So some futility like wireshark frame analysis.
For me, the problem is simple: the firmware.
I've opened an incident at Google, which unsurprisingly can't do anything for me.
So Google's solution is clear: scrap the equipment. So that's how this company deals with the subject of ecology.

[JPS23]

The only test I didn't see you confirm for sure was trying to use the old NEST app first (instead of Google Home app) to get the latest firmware.  Nest Protect doesn't work with Google Home at all (at least mine don't).  Since you are a security guy (as am I) you should also know the NEST cams (not sure if you have those too) use an outdated version of SSL/TLS making your cameras prone to eavesdropping.

Google is defiantly not the company they used to be. They are now forcing customer to buy new products by holding them hostage on simple things like firmware updates (that they could easily fix).  I'm so disappointed in Google.  Money hungry anti-consumer.  Last time I buy any google product.  I wasted over $500 on these cameras....even with the right firmware, they don't operate nearly as good as they did with NEST, years later even. Plenty of time to fix all the issues. Bye bye google.