Nest Protect firmware 5.0rc31 appears to be broken

[cs12ag]

Hello,

It appears that firmware 5.0rc31 is not doing occupancy and history properly.

It is difficult to determine within the Nest app when this firmware was applied to my Protects, but I believe it was in the last few days. I have no 'Protect History' in the Nest app for two of my Protects, starting from 22nd March for one and 19th March for the other. I also have no occupancy detection for these two Protects, appearing to start on the same dates for each Protect device respectively (I am determining this using the unofficial Nest Protect plug-in within Home Assistant). My third Protect is still on 3.6rc8, and has full history within the Nest app and is still able to detect occupancy as expected.

I have successfully performed the 'safety check' on all three of the Protects. I don't want to factory-reset my devices with the higher firmware as I have no indication this will solve the problem.

For reference, this problem has been noticed by the unofficial Nest Protect plugin users, discussion here: https://github.com/iMicknl/ha-nest-protect/issues/476

Please can this be escalated within the support desk? Is this a bug in the firmware? Or is this a breaking change in the API, that apparently the Nest app hasn't been uplifted to support yet?

Thanks in advance.

[RodrigoBC]

Hi there,

Thanks for posting here in the community! I understand the issue you're describing with your Nest Protect Pathlight. It seems like while the motion detection usually works fine, the light has recently started staying on for hours at a time during the night before reverting back to its normal behavior. You've noticed it seems to be inconsistently switching between modes without reason. Additionally, you pointed out a discrepancy in the logs: while your other devices completed a Sound Check on Saturday the 18th, this specific unit only performed a standard check. Don't worry, I am here to help!

To better understand the situation, I'd like to ask a few questions:

• Did you change batteries after that?
• Did you check the expiration period date?
• Did you try to do a manual test to check possible errors of the Nest protect? Here you can follow the steps to perform it Manually test Nest Protect

In the meantime, I recommend following these steps to rule out potential issues interfering with your Nest Protect’s nightly functions:

• Check for obstructions: Ensure nothing is blocking the sensor, as this can cause false activations.
• Clean the device: Inspect the Nest Protect and ensure it is free of dust or debris.
• Perform a Factory Reset: If the issue persists, you will need to perform a factory reset and set it up again in the Nest app. Please note that the Nest Protect does not have a "soft restart" option—only a manual test or a full factory reset. Refer to this article: Reset Nest Protect and erase all settings.

After all steps feel free to let us know more relevant information 

Regards,
Dominic

[robgbc]

See this thread: https://www.googlenestcommunity.com/t5/Nest-Protect/Nest-Protect-firmware-5-0rc31-appears-to-be-brok...

[harrydn]

My nest protects with the updated firmware are also not working properly - this is not related to the nest but must be related to the firmware version...