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.

[Ch484]

My path light stays on all the time now. It’s set to motion but never turns off even when there isn’t motion

[ShaunH]

I have 3 Nest Protect devices. 

One works fine with Firmware: 3.6rc8 located near some bedrooms. That detects occupants and the pathway light comes on and goes off as expected.

Two others fail to sense any Occupancy changes with Firmware: 5.0rc31

One near the Entryway, is stuck on Clear and fails to detect anything, the other near the Kitchen is stuck on Detected and refuses to go off.  The lines on both failed stuck graphs are where the devices were either reset or re-added to the app. 

Please raise a testing defect and roll back the firmware to 3.6rc8.  This is now a Production fault affecting real end users. 

[ShaunH]

All 3 devices are 2nd Gen hard wired.

[Mubble]

I have four Nest Protect devices in my home.  Over the past few weeks I have noticed the pathlight on three of them frequently remains lit at night after I've left the room, I have them set correctly in the settings to 'On' and not 'Always On'. I often have to re-enter the rooms and wave my arms in order for them to notice movement and then register I've left the room again.

The three affected by this are on firmware 5.0rc31.

The one which works fine is on firmware 3.6rc8.

[RoboPapa]

Hi, I have exactly the same issue. The Pathlight on the unit with Firmware Version 5.0rc31 only started staying on very recently. My second unit is on Firmware Version 3.6rc8 and Pathlight works as it should.

I cannot even find any details on Firmware Version 5.0rc31 listed anywhere.

Strange!

[SaraEs]

Hi there,

Thanks for reaching out to the community. I understand that you have four Nest Protects, and three of them frequently remain lit at night after you’ve left the room even though you have them set correctly, and you often have to enter the room again and wave in order for them to register the movement. No worries, help’s here.

To understand better the issue, I’d like to ask a few questions:

• Is your Nest Protect wired or battery, 1st or 2nd gen? Please refer to this article to check which one you have: How to tell which Nest Protect you have.

• Is the Nest app running on its latest version?

• Have you received any alert notification in the app?

I'll be waiting for your response.

Best regards,

Sara

[Lexxx83]

Hi @SaraEs,

I think this topic by @cs12ag :

Nest-Protect-firmware-5-0rc31-appears-to-be-broken 

Is about the same problem.

I myself have also been experiencing problems with 2 of the three Protects for 2 weeks now.

Nest App Version 5.86.3 (Apple)
Net Protects Model : Topaz-2.33 Wired
Software protects affected: 5.0rc31
Software protect working perfect: 3.6rc8
No notifications in the app that explain or clarify this problem.

What I have already tried myself:

Removing the Protects from the app and adding them again.
Completely resetting by holding down the button. Tried to force firmware updates by holding the button for 5 seconds. Tried this in various sequences and multiple times, but without result.

As mentioned earlier, nothing about firmware 5.0rc31 can be found anywhere... please explain how some people can run on a "non-existent" firmware.

We expect a solution as soon as possible, as a downgrade is not possible according to the documentation.

I also contacted Support, where I received an email stating that I would receive a response within two working days. Unfortunately, to date, still no response...

Best regards, 
Lexxx83

[Mubble]

All four are wired, Gen2 and running from Google Home on the latest software.

[RoboPapa]

I have Nest Protect Gen2 Wired devices.

My Nest IOS App is on Version 5.86.3.

I have two Nest Devices, one with Firmware Version 5.0rc31 with Pathlight not working correctly since upgrade 5.0rc32 and second device with Firmware Version 3.6rc8, with Pathlight working correctly as always.

Topaz-2.33 on both devices.

Kind Regards,

John

[DipsB]

Still no update from you, disappointing from Google.

[DennisLundberg]

@SaraEs You have now received multiple consistent reports of this issue, with the details you requested. All report points to a bug in the 5.0rc31 firmware across several different hardwares.

Can you acknowledge that you have received thet additional information that you requested?

Is there someone working on a fix for this bug?

When can we expect a rollout of a working firmware? Personally I'd be ok with rolling back to the working 3.6rc8 firmware, until a fix can be made to the 5.0 firmware.

[DennisLundberg]

Hi, I am experiencing the same problem.

We have 2 Nest Protect units, one with the older 3.6 firmware and one with the newer 5.0 firmware. The pathlight often, but not always, stay on after being triggered by motion for the unit with 5.0 firmware. This has never happened before the new firmware was installed.

[DennisLundberg]

Both our units are of model Topaz-2.7 wireless.

[Lexxx83]

@SaraEs Even now, it remains suspiciously quiet... 😞

[NestProtectFan]

I can provide a larger dataset.  I have 11 Nest Protects, broken down as follows:

• 2x wired Topaz-2.33, running 3.6rc8
• 1x battery Topaz-2.33, running 3.6rc8
• 1x wired Topaz-2.34, running 3.6rc8
• 3x wired Topaz-2.7, running 3.6rc8
• 1x wired Topaz-2.7, running 5.0rc31
• 1x wired Topaz-2.9, running 3.6rc8
• 2x wired Topaz-2.9, running 5.0rc31

The pathlight works correctly on 100% of the units running 3.6rc8 

The pathlight stays continuously illuminated in the dark on 100% of the units running 5.0rc31

In my professional opinion, this is clearly a bug in 5.0rc31

[julyadadoll]

Hi, have you tried any possible resolution?

[Lexxx83]

@SaraEs any update?? 

[Mubble]

Two weeks and no update. Good service Google.

[DipsB]

Absolutely terrible by Google. 

It makes you wonder if this is the reason they have stopped selling Nest's!

[Aaron40]

Same problem here, for a bout 2 weeks the path light is staying on. I have 2 x wired nest protect detectors on  version 5.0rc31.

Please can google fix

[EduardoN]

Hi there,

Thank you very much for contacting the community. I understand that you have recently had issues with the Nest Protect 2nd Gen; for the past few weeks, it has been unable to detect occupancy changes since the firmware was verified as version 5.0rc31. I appreciate all the information you have provided. Based on those details, I want to inform you that our engineering team is investigating the issue and working on a solution; we will keep you informed as soon as updates become available.

Best regards,
Eduardo

[Lexxx83]

Good morning EduardoN,

Thanks! Finally a response; hopefully the software department won't take as long to find a solution, since they had working firmware.

Hoping for a quick response with a solution!

Kind regards,
Lexxx83

[MeshMinded]

Seeing your acknowledgment of the issue stopped me from looking into filing a formal complaint with the Consumer Product Safety Commission.  I think most would agree this is ultimately a safety issue and should be addressed in a timely manner. Especially those of us with battery units. 

[LorianNod]

I have this issue too. On 5.0rc31

[DipsB]

Hi. 

Good to hear something is happening, but oi believe Google do not want anything to do with Nest products anymore. 

Google stopped selling these products and their I don't believe they will support these items.

[DanielV]

In addition to the pathlight being broken, the one Protect out of my 3 that has 5.0rc31 also reports that alarm is broken (as in "Can't verify the alarm aound").

With a safety check I can hear the alarm, so no issues there.

I suspect now that's more to do with faulty firmware than the microphone actually being broken.

Would be good if the firmware could be downgraded.

[KablammoNick]

One of mine did the same a couple of times, although now seems to have corrected itself and showing all ok...

[LorianNod]

It can go a couple of days without issue then come back

[Clabbe]

I also have this issue, On 5.0rc31.

Hope for a fix soon.

[JBrady]

I have same issue with one of my three lights staying on at nighttime. Having to walk back out to restricted it before it goes off again. I have two nest protects version 2 on firmware 

3.6rc8 

and the faulty light coming on is on firmware 5.0rc31

[Garjen]

I have the issue also, pathight is now staying on. Can clear using a torch, then it triggers again and stays live 

[Mubble]

One month to get a simple software fix is unacceptable.

[yetkopempo]

I have exactly the same issue....

[mekk]

Same issue on my protect 5.0rc31. No problem on my other one which runs on 3.6rc8. Definitely an issue with the firmware.

[LorianNod]

@SaraEs any update for us on this?

[Marcusbiel]

Same issue here since the 5.0rc31 firmware update, path light stays on

[robgbc]

I have 2 battery powered Topaz-2.34 Nest Protect and they both have pathlight staying on issue since updating to 5.0rc31

As noted by other users, when pathlight is stuck on, walking into range of the device again will often cause pathlight to turn off.

Pathlight does appear to time out at some point overnight, but I've experienced it staying on multiple times for 30+ minutes, total stay on-time unknown.

[Slimjim1980]

Same issue. This is annoying af!

[WillieB]

My Protect Pathlight is set to on and was turning the light on when it detected movement and turned off shortly after.  Recently it has been acting correctly but during the night it goes on and stays on for hours.  It will then turn off and reacts to motion again.  It may then turn on for an extended time.  It seems to switch between the different modes.  It started recently. In looking at the history, I see that all my other Protects did a Sound Check on Saturday the 18th, but this one only did a normal check.  Is there a way to do a soft reset?