03-16-2024 10:11 PM
I have 14 Nest Protects in one building. A carbon monoxide heads up went off mid day during some carpet cleaning from the fumes. I silenced the alarm twice using the app. It's about 10 hours later but all Nests in the building are still flashing yellow reporting the heads up on a button press. The original reporting Nest is not flashing yellow and reports no issues when pressed.
If I try to test in the app, it runs the check up but the alarm never goes off. Power cycling one of the Nests does not clear the flashing.
How do I clear this phantom error from every Nest?
03-16-2024 10:14 PM
Additionally, Nest app shows everything is ok on all sensors.
03-21-2024 07:23 AM
Hello Primitive,
Thanks for reaching out to the Community. Because you can't smell or see carbon monoxide (CO), when Google Nest Protect alerts you that there is carbon monoxide in your home, immediately move to fresh air. If an alarm signal sounds:
Important
This information is also available as a label provided in the packaging. Stick this label in a spot where everyone can see it, like the refrigerator.
Let me know if you have any questions.
Best,
Lance
03-25-2024 02:19 PM
Lance I don't think you addressed the question from Primitive. The Nest Protect units are no longer detecting any issues with their sensors. However, the units are still reporting a "false" "heads up" for an OLD detection. The question is how to clear those "heads up" notifications.
I have been having a similar problem. I have 8 Nest Protect units (gen 2). One of the units lost it's connection to WiFi. I have fixed that problem and it's not connected. However, whenever I test (push the button) of the other units, they flash yellow and report the heads-up that WiFi has been lost on the first unit. When testing the first unit, it tests ok. So, now each of the other 7 units continue to report the false "heads up" notice when I push the test button. The Nest app reports everything as green.
I read another community report that suggested removing the unit that had the original fault and doing a factory reset. I have tried this and continue to have the same problem. In fact, with the original unit removed and reset, the other units still continue to falsely report it even though it's not in the system. I tried resetting one of the other units, but it still reports the false head's up. I'm now going to try resetting all 8 units and hope that clears the problem.
Question: Is there a defined procedure to truly reset these units. Thanks
03-26-2024 12:46 PM
I was finally able to clear the stuck "heads up" from my Nest Protect units. I really did not want to reset all 8 units (therefore starting from scratch). So, I let it sit for a day. When I tested the units this afternoon, all but one had cleared the old "heads up" message. Why just one was still giving me a "heads up" alert when pushing the button, but the others did not. So, I waited a little longer and this unit finally was cleared of the old alert.
I'm not sure what actually caused the clearing of the alert, but I know that the units are supposed to use their own wireless network to sync the status of each unit periodically. Maybe that's what eventually happened. However, when the original unit that had lost the Wi-Fi was fixed, it was several days before things cured themselves. I don't know if one of my previous actions lead to the cure or it was just a matter of time. I have a mix of battery powered and AC powered units. As I understand the battery powered unit sync once a day and the AC powered units sync every 1-2 hours.
The question still stands - Is there a defined procedure to clear out old alerts?