I agree with you, Larry. Having a fully integrated system where home automation meets home security would justify the cost of such an upgrade. Having this wireless technology is also easier to integrate into existing and new homes, condos, and other systems (such as dorms and other larger infrastructures). What's interesting to me is that this article and the smart parking sensor article (tech like that is implemented in SF, the usual early adoptors) are originally appearing in EE Times Europe. I'm hoping other places will adopt it. I do realize that developing countries and places with either older or up and coming internet infrastructures will have a harder time adapting to this because their networks are possibly not as protected or widely connected. In addition, any information that is wireless will need special encryption, protection, and require server fail-over or back-up power. Also, with the "green" movement, how energy will the automation/monitoring be?
What I like about Android@Home is the fact that they are building a software stack that isn't hardwired into a physical layer. Where would Google be now if they had had to build a new Internet to run their software? They understand building on top of existing infrastructure.
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. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.