larryllix Posted April 4, 2016 Posted April 4, 2016 Watch the video. http://bgr.com/2015/02/18/google-nest-smoke-alarm-video/
KeviNH Posted April 4, 2016 Posted April 4, 2016 Interestingly Brad Fitzpatrick is apparently still employed by Google after slamming 1st generation Nest on twitter and youtube.
Scottmichaelj Posted April 4, 2016 Posted April 4, 2016 Watch the video. http://bgr.com/2015/02/18/google-nest-smoke-alarm-video/ Too funny, love it!
Teken Posted April 4, 2016 Posted April 4, 2016 I'm more curious to find out what the root cause is for such a multiple failure. I suspect if history is any kind of indicator its a poorly crafted firmware bug in the system. I know its all the rage to buy things from some random company that has no proven history in making life and safety items like this Nest Protect. But people really need to take pause and consider the safety implications of doing so. Companies like Kidd, First Alert, have been doing this for ages and offer many price / features that suite anyone's budget. Lets see what Google has to say about the fault . . .
jerlands Posted April 4, 2016 Posted April 4, 2016 Hate to see this guy during slow traffic Seems a bit contrived to me though? Nice house though. Jon...
elvisimprsntr Posted April 4, 2016 Posted April 4, 2016 Not to mention that per NFPA/NEC code you have to replace residential smokes every 10 years. I have 9 smoke/co in my home per code. $100x9=$900 vs $10x9=$90 every 10 years.
larryllix Posted April 4, 2016 Author Posted April 4, 2016 From the video it just seems like user not following the verbal instructions. Notice, if you listen closely, all the smokes adding the word "here" n the end of the instruction. It would seem to me. and logically make sense that the system wanted him to go to the triggered smoke detector area to acknowledge it there but he didn't. Why, after all the units had been punched and taken down no system acknowledgement was had may have been a defect in design, or maybe they cannot be acknowledged once they are disconnected from the common traveller wire, used to make them communicate as a system. I went through the same thing years ago and smoke units will ring under capacitor carryover for half an hour. No Nest required.
jerlands Posted April 4, 2016 Posted April 4, 2016 The guy is supposedly a google staff engineer and what does he do but go around in a panic wildly pressing and punching the device. You think he'd at least attempt to show some troubleshooting skills... maybe begin by pulling the batteries in the master bedroom unit to stop the signal then attempt to hush the rest? Jon...
Teken Posted April 4, 2016 Posted April 4, 2016 The guy is supposedly a google staff engineer and what does he do but go around in a panic wildly pressing and punching the device. You think he'd at least attempt to show some troubleshooting skills... maybe begin by pulling the batteries in the master bedroom unit to stop the signal then attempt to hush the rest? Jon... I really didn't want to comment on what the guy was doing because it just made me shake my head. Regardless of his lack of real trouble shooting he doesn't explain whats really happening. Also, to be fair to NEST / Google this hasn't been reported or seen elsewhere. So have to say this just might be a bad batch unless someone comes in saying he was pushed a unannounced OTA update. That would be priceless . . .
larryllix Posted April 4, 2016 Author Posted April 4, 2016 Truth be know this is probably the latest brainchild of the google marketing team. Makes google look honest and caring by releasing an immediate and planned fix while generating popularity via the latest medium with a totally studio driven fake video. It works really well for the oblivious techie crowd. Sent from my SGH-I257M using Tapatalk
Teken Posted April 4, 2016 Posted April 4, 2016 Not sure how many still believe the whole *No such thing as bad press* ideology. I can't honesty say this is something a sane person would entertain in hopes of generating hype or awareness of a product. Speaking as a lay person it in no ways instills confidence in the product. I do concede the form factor and some of the high technology features are cool - but they are very much nice to have. In no way does it supersede the need to have hardware that is battle tested and proven to work. Nest has proven since release their wares have lots of room for improvement and have no concept of testing. I am sure there are plenty of the iSheep who are eager to let past bugs pass like the failed OTA for the TSTAT. But, only rock head would let a smoke, heat, CO detector pass such hardware fault. Again, I have not seen this specific issue announced anywhere else so have to give Google / Nest the benefit of the doubt this could be a bad batch. If however its determined this was from a unannounced OTA firmware update to the hardware. Well, all bets are off and people need to go on line and shame the hell out of them. Only second to suing them for incompetence and pain and suffering. Then again the TOS restricts anyone from doing so and binds them to 3rd party arbitration which must be conducted in their home town. I can guarantee 99% of the iSheep haven't read that little caveat this company has mandated to use said hardware. Shameful to say the least . . .
Scottmichaelj Posted April 4, 2016 Posted April 4, 2016 One night I had friends over to enjoy some wine. All of a sudden one smoke kept beeping. I didnt feel like messing with it so I removed it from the ceiling and then took out the battery. Problem solved right? Ha not quite. Kept chirping. This was in my previous home and I had a courtyard with a water fountain out front. Annoyed as hell I threw it in the fountain outside and shut the front door. Hours later I walk my friends out to their car to say goodbye and the damn thing was still chirping in the fountain! We all had a nice laugh. Two days later took it out and put it in the sun to dry out. Put a new battery back in, tested it and it still worked. Hooked it up to the electrical again and used can smoke to test and the damn thing worked perfectly! Lol Kiddie for the win!
larryllix Posted April 5, 2016 Author Posted April 5, 2016 Not sure how many still believe the whole *No such thing as bad press* ideology. I can't honesty say this is something a sane person would entertain in hopes of generating hype or awareness of a product. Speaking as a lay person it in no ways instills confidence in the product. I do concede the form factor and some of the high technology features are cool - but they are very much nice to have. In no way does it supersede the need to have hardware that is battle tested and proven to work. Nest has proven since release their wares have lots of room for improvement and have no concept of testing. I am sure there are plenty of the iSheep who are eager to let past bugs pass like the failed OTA for the TSTAT. But, only rock head would let a smoke, heat, CO detector pass such hardware fault. Again, I have not seen this specific issue announced anywhere else so have to give Google / Nest the benefit of the doubt this could be a bad batch. If however its determined this was from a unannounced OTA firmware update to the hardware. Well, all bets are off and people need to go on line and shame the hell out of them. Only second to suing them for incompetence and pain and suffering. Then again the TOS restricts anyone from doing so and binds them to 3rd party arbitration which must be conducted in their home town. I can guarantee 99% of the iSheep haven't read that little caveat this company has mandated to use said hardware. Shameful to say the least . . . Bahhhhhhhh! brings to mind something about wool... . over eyes???
Recommended Posts
Archived
This topic is now archived and is closed to further replies.