Alarm (False Alarm) but No History In App?

[Arc315]

We have 11 Nest Protects set up in our house. They randomly just started going off saying there was smoke (in the middle of the night with sleeping kids) and then all went silent after about 30 seconds. The odd thing is that the app does not show any history of an alarm or smoke being detected in the last month. Because of that, I can’t even tell which of the 11 units may have caused this. I did go through every unit in the app and it looks like 3 of them the sensor was last “checked” right around that time… but that still doesn’t explain what happened and why it wasn’t logged in the app. What should we do here?

[micro00613]

Me too

[sicsacol]

Hi all,

Thanks for posting in the community. I understand you're experiencing false alarms with your Nest Protects in the middle of the night, reporting smoke detection without any corresponding history in the Nest app for each device when you checked it, making it difficult to know which one caused this. I appreciate you taking the time to check the history in the app. No worries, I'd be more than glad to assist you.

I recommend performing a safety checkup on your Nest Protect. This check helps ensure everything is working correctly and can sometimes help identify the cause of unexpected alarms. To do it, please follow these steps:

• Press the Nest button on your Nest Protect. The blue light should turn on, and it will speak to you.
• When it says "Press to test," press the button a second time.
• Your device will run a safety checkup, and then it will let you know the results and if it encounters smoke detection or activity.

Please visit the next helpful article to learn about Safety Checkup.

Let me know the results of the safety test.

Regards,
Jonathan 

[KJandu]

I follow all the steps but the beeping didn’t stop

[Olivier89]

Sorry, but this does not answer the question at all. Running safety checks is totally orthogonal to this problem.

In my case, I had to go to "Messages" in the app in order to see history for the device.

The "Protect History" screen broken down per device only show health check results, and that's a major shortcoming. We need to see the history of events to understand what's going on.