Part of the problem with the IoT is the wide variety of protocols, like 6LowPAN, CoAP, DASH7, EnOcean, Insteon, Zigbee, and Z-Wave mentioned in the article. Any grouping of IoT devices will likely be heterogenous, with each one possibly needing to be addressed and controlled in a different way.
What's the difference between home and industrial applications? For the purposes of what is being done, nothing. They are simply seperate instances of a general problem: addressing and controlling a network of IoT devices.
Developing DeviceJS might have been the single biggest part of WigWag, but once done, many things are possible. And WigWag stated plans to make it open source, so developers encountering things the library doesn't support can contribute updates to add them.
The underlying notion - abstracting the underlying IoT devices behind a JS library - strikes me as broadly applicable beyond what WigWag is doing.
@mcgrathdylan, Allwinner is by far the number one tablet apps processor company in China. The company has big ambitions. Obviously, Allwinner wants to get into the smartphone business (and automotive). But it is interesting to learn that it appears to keep an eye on IOT.
More on Allwinner, please go to the following link. It's based on my visit to the company located in Zhuhai.
It could be useful if used in a two-stage development. Initial prototype implementation is done using the libraries. Then, following market validation that there is a significant market, start stage 2 - code, resource, cost, performance optimized implementation.
The catch is not getting caught up in release/update cycle, and allocating sufficient time and resources for State 2 development.
Seems its a prerequisite nowadays for a chip company of any size to have team in China.
I thought it was an interesting design win for Allwinner. My perception of that company is that it makes relatively inexpensive apps processors for tablets, but it seems as though there is more to it than that.
As we are moving to a world where just about everything can have an IP address and be connected by TCP-IP, I see all sorts of potential beyond the stated use case here.
The small startup like WigWag already has a team in Wuxi, China, and the software runs on Allwinner's chip, aside from that of Freescale, speaks volume for the anticipated IoT pickup in the Chinese market.
Only if the IoT product developers want it to work, would be my answer. This quote kind of says it all:
"Home automation is almost a dirty word among some technophiles because it's been tried and tried again and hasn't taken off."
I would say "home integration" rather than "home automation." I have PLENTY of automated appliances in my home already, including a fancy new toaster oven, but I have no need or inclination to integrate them. Even creating an IoT, for some of these home appliances, does not necessarily mean that there's any need to integrate among them.
This discussion is somewhat related to the one about automobile hacking. Next thing you know, we'll see a frenzy about the potential security holes that COULD emerge in homes, IF your kitchen faucet is tied to your washer, drier, and power meter.
Although parenthetically, it might make sense to tie your cold water kitchen faucet to the garbage disposer, to prevent the latter from being switched on in the former isn't open. Whether the Internet and your Facebook page need to know about this is something else again.
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.