I find this hilarious. Google just paid through this nose to get this company and now a basic feature of the device is considered a flaw. When I first read the specs and saw the video on how to use the device I laughed out loud. What would keep it from shutting down when your four year old goes twirling across the floor underneath the device? Bad product design is bad product design. No marketing BS can overcome that. Goggle purchased a big smoking pile of dung. Not the first waste of money for them and surely not the last. I can only hope I'm on the receiving end of their idiotic purchase plans.
The beauty of a connected device is that the problematic feature can be disabled by a remote software update without requiring the user to rip the device off the wall and send it back to the manufacturer.
@Max this would be good to discuss on Friday? It's almost an issue of augmented reality?
I find this information alarming and amusing at the same time.
I have designed and installed fire detection equipment for a great number of years.
The funny thing is that the detector, to get to market, probably had to pass a whole host of EMC tests.
The alarming thing is where was the safety critical assesment tests for usage?
Just from reading the article, it looks like the software teams got thier silence and isolation issues mixed up.
If I designed a software strategy like this then it would only be a silence option and then only for a limited time interval, such as allowing the detector to clear smoke after burning toast. I do not think I would even do a gesture silence for Carbon Monoxide.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.