News for hackers. Stuff that matters.
Re:We're hearing about troubles at Nest by Eiriksmal on Monday February 15, 2016 @04:00PM (#11105927)
That's a horrible experience.

But, to be fair, many newer structures have all their smoke detectors wired together so when one goes off, they all go off. I experienced that in my house, built in '97, which was extremely disorienting and stressful when it first happened. Growing up in a house built in the 80s, only the kitchen's smoke detector would go off if you burned something. I understand the perceived safety enhancement, but waking up the sleeping baby because dumb ol' dad smoked too much oil when stir frying something... Ugh.

Edit: formatting.

Re:We're hearing about troubles at Nest by Animats on Monday February 15, 2016 @05:26PM (#11106515)
Yet industrial/commercial grade hard wired smoke detectors work just fine. I've worked in industrial facilities where there were thousands of smoke and fire detectors, and a zero false alarm rate. Yet, one day, when a HVAC unit overheated and smoked, all the right stuff happened. The local alarms went off, and the duct dampers slammed shut to contain the smoke. But because there wasn't confirmation from a second detector, or water flow in the sprinklers, the full emergency power off and building evacuation sequence didn't trip. We got to the HVAC unit and pulled its main switch before things escalated.

So why can't Nest meet that standard of performance?

Re:We're hearing about troubles at Nest by a3n on Tuesday February 16, 2016 @12:53AM (#11108139)
Because they're disrupting thermostats.
Re:We're hearing about troubles at Nest by derrida on Tuesday February 16, 2016 @01:13AM (#11108200)
Success.
Re:We're hearing about troubles at Nest by jordache on Monday February 15, 2016 @06:30PM (#11106867)
the team consists of a bunch of industrial designers and *hitty electronic engineers?
Re:We're hearing about troubles at Nest by IgorPartola on Monday February 15, 2016 @04:05PM (#11105965)
This is why I like the FirstAlert wireless detectors: mesh network so they all go off, but you program each one to announce with a voice which room the trouble is in. They even announce which one has the low battery instead of chirping in the middle of the night.
Re:We're hearing about troubles at Nest by Klathmon on Monday February 15, 2016 @04:27PM (#11106143)
Well much of that was the "dream" of the nest protects...

It announces where the "alert" is, you can wave to dismiss it, it has the app for your phone to alert you if you are away from home, and they all link together (without needing any wiring in the house, making it easy to retrofit).

Sadly in practice it's a mess, nothing works, so much so that I've lost all confidence in the product to do it's minimal function, detect smoke...

Re:We're hearing about troubles at Nest by phil21 on Tuesday February 16, 2016 @01:08AM (#11108187)
It's a bit ridiculous when you could have basically taken any old mass produced el-cheapo smoke detector circuit, and instead of tripping an alarm have it just feed into gpio pins on some wifi/whatever controller that has the "smarts".

Literally all that was needed to get 100% of the reliability of the billions of detectors out on the market, while working out all the kinks on the "cloudy" sort of stuff.

I have to admit I re-invent the wheel more than I should, but man. This one seems simple :)

Re:We're hearing about troubles at Nest by cowsandmilk on Monday February 15, 2016 @07:13PM (#11107035)
Here is what I think is a sane timeline:

(1) smoke detector in kitchen goes off, only sets off in kitchen

(2) after 1 minute, other rooms start saying "smoke in kitchen"

(3) after 2 minutes, alarm goes off in other rooms

Timeline could be shortened if necessary for safety, but this doesn't seem like it would be difficult to implement.