My home has 7 Nest Protects. I recently tried a "real-world" test using a blown out match to create smoke at one of the Protects. The Protect detected the smoke and sounded the alarm (an actual "emergency" alarm--not a "heads up"). However, the alarm did not sound on any of the other 6 Nest Protects.
The response I received from Nest support wasn't inspiring. The first (escalated) rep told me that Nest doesn't recommend testing the system that way and disconnected the chat. A second phone rep escalated to their safety team and told me they would respond within 24 hours, but I haven't heard anything.
If this is a Nest bug, it's obviously a major safety issue (as well as violating at least my local fire code).
Has anyone else run a similar test recently? I don't see how this could just be an issue with my system, but I also find it hard to believe Google's QA could be so bad that it would release software with this problem.
This is a huge deal. I’m trialing one smoke detector at moment before I invest into 9 more alarms. If they do not communicate then I will look elsewhere. Would love to see a response from google on this. Also curious if the WiFi router is down will they still communicate or are they dependent on being connected to router to communicate
They form their own network to connect to each other Joel, so you would be okay there. As for the smoke, and interconnection, it will set off the alarm at the point of fire initially, as well as broadcast to your phone and other devices. it will all depend on the "level of smoke and heat" detected how the alarm goes off, dont forget these arent just dumb alarms, they detect both heat and smoke. A small amount of smoke can be expected near a kitchen for example. The other day I made lunch while my wife was at work, and burnt bacon a little bit, it set off the smoke alarm near the kitchen, but the others did not go off, however both my wifes phone as well as mine alerted of smoke near the detector, so it worked as expected.
As for the smoke, and interconnection, it will set off the alarm at the point of fire initially, as well as broadcast to your phone and other devices. it will all depend on the "level of smoke and heat" detected how the alarm goes off, dont forget these arent just dumb alarms, they detect both heat and smoke. A small amount of smoke can be expected near a kitchen for example. The other day I made lunch while my wife was at work, and burnt bacon a little bit, it set off the smoke alarm near the kitchen, but the others did not go off, however both my wifes phone as well as mine alerted of smoke near the detector, so it worked as expected.
That's consistent with my experience where only one detector sounded its alarm. Have you ever tested if more smoke will cause all the detectors to go off?
I know the Nest Protects give a warning (both voice and phone notification) when smoke is first detected, but I can't find anything that says there are two behaviors when the alarm actually goes off (one detector and all detectors) or that this is even legally compliant:
Personally my system has never gone past the Heads Up alert, which is what you have described. If you see a yellow ring that is the heads up alert, where as an emergency alert (red light) is the one that is broadcast everywhere. There is a good article about this linked below. Also yes these are compliant to california law, see the link to the google KB below as well.
Ashepherson, have you heard anything back from Google on this? They are completely ignoring my inquiries about the status on this issue--My only guess is their attorneys may have told them to keep quiet because of the liability issues involved.
I have purchased some canned smoke and verified that this behavior is consistent across my system. Nest is only sounding the alarm on the Protect which detected the smoke--not the other interconnected Protects in the house.
Has anyone else in the community tried this test? I'd like to know how widespread the problem is. At this point, I think the only way to get a response from Google will be an article in the New York Times.
I should add that the reason I was testing this in the first place is that some alarm systems (eg Ring, Abode) integrate smoke alarms by listening for the T-3 tones from a nearby detector and then reporting this to the central monitoring service. If all the detectors do not sound, fires will not be reported until the detector next to the listener sounds its alarm.
Steve, what do you mean when you say "reporting this to the central monitoring service"? How is a central monitoring service connected to your Nest Protect system? I thought when you disconnected the third wire from your alarms, the central monitoring system (if you were connected to one) was disconnected, also. At least mine was.
A few different issue here:
The third wire was used to physically interconnect smoke detectors so that all the alarms could sound when smoke sensed by any one detector. Nest detectors use a wireless interconnection for this function rather than the third wire (which is the functionality that is not working on my system). Some burglar alarm systems could also be attached to this third wire to allow them to report a smoke detection condition back to the central monitoring service.
Some newer alarm systems (eg Abode, Ring) can also integrate your smoke detectors. These work by placing a microphone near one of the detectors and listening for the sound of the alarm going off. When they hear this sound, they will report the condition back to their central monitoring systems. However, if Nest only sounds the alarm at the Protect that senses the smoke, the "listener" will not hear the sound and report the alarm (unless it is next to the Protect which detected the smoke).
Let me flag this up for you, in fairness I have not experienced this with my protect system. Can I ask, have you tried resetting the units and re setting them up to see if that might correct the issue? I'm wondering if the mesh network somehow failed? I'll still escalate again of course.
@Brad can either of you two provide assistance?
I haven't tried a full reset. I have done the built-in test (by pushing the button on one Nest Protest). That does cause a test to run successfully on all the other Protects in the system. So it seems like the interconnect network must be functioning correctly.
This feels to me like a software bug. I just don't know if it's widespread or a corner case that's coming up in my system.
I certainly could try resetting everything and restarting from scratch. But the problem is reproducible right now, so if Google does want to investigate this would be the opportunity. And I'm in Cupertino so they could easily get physical access if they need it.
I just thought I would give a real world experience. I have 5 Nest protects installed with one in a guest house (fairly close to main house) and 4 in main. I had a very smoky kitchen fire in the main house and the Nest Protect in the guest house alerted me to the alarm. Needless to say I was very pleased with the technology.
Thanks rw. How long ago did that occur? I haven't yet been able to determine if this is a problem related to my configuration or if this is a more general bug introduced in a later version of the software. The function must have been working at some point since the Protects were able to pass their UL certification.
Nest support had me delete all the devices from the app, factory reset them and then re-add them to the app. That did clear up the issue, although didn't provide any info on how they got into that state in the first place or any assurance that they won't return to it.
Since the Nest Protect internal tests didn't detect this condition and reported the system as working even when it wasn't, I'm going to periodically test my system using canned smoke to ensure they don't return to the non-functioning state.
This issue is still occurring.
We just purchased three "Nest Protects" with the express intention of monitoring our outbuilding at night. We placed one unit in our detached office, one in our main house kitchen, and one in the main house upstairs. The distance between the office and kitchen units is about 30 feet.
After going through the initial setup process successfully the application showed all units online and functioning properly.
Next we burned paper safely in the office to test the system. The office alarm activated as expected and we ran inside to listen to the other units. The other units were all completely silent.
This is a big problem. I will try the delete/reset/re-add workflow mentioned by Steve to see if that fixes the issue. More soon...
Went through a support process... turns out our "office" device (where I was initiating the smoke condition) was offline while the other two units were online.
Unfortunately it seems you cannot use the app to determine if a device is offline. All my devices looked "green" and the app said "Everything is OK" even though my "office" device was offline.
The technician showed me how to run a manual network check on each device. You press the button to wake the device and wait for it to respond with "press to test". Next you long-press the button until it says "checking the network". Then it will run a diagnostic after which it will produce either a green light (online - good) or else a yellow light and the words "try again later" (offline - bad).
The solution was to go into the wifi settings on the "offline" device and manually choose the correct wifi network and enter the password. I suppose perhaps there was corruption when it tried to automatically get those settings from my mobile device during the initial setup process.
Anyway, all the devices work as expected now. I hope this helps someone...
We never discovered why the Nest's didn't work. Whatever the issue was, it wasn't detected by Nest's diagnostics. It was a fluke that I discovered the issue and it was only resolved by completely rebuilding the system. So it wouldn't surprise me if other people have systems in this state but just don't know it.
Given the potential safety hazards, I found Google's response to be very cavalier. Google initially ignored it/responded with misinformation. I filed a complaint with the Consumer Product Safety Commission (Report No. 20211108-6853C-2147358868) and they generated a report to which Google was require to respond. At that point, Google sent a tech to look at the situation. But even though the issue was repeatable, they didn't identify the root cause. Rather, they just reset/rebuilt the system so that it operated correctly again.