• Not sure if these all qualify as startups any more:

    • Smart Things
    • Ayla Networks
    • ioBridge
    • Arrayent
    • ThingWorx
    • Ducere Technologies
    • Symplio
    • Canary
    • Octoblu
    • Scanalytics
     
  • For future reference. “We’re building an end-to-end encrypted database that lets you run queries without exposing the decrypted data to the server”

     
  • I.e. away from AllJoyn, the Industrial Internet Consortium, and the Open Interconnect Consortium. What this means is anyone’s guess, but if there’s one thing we need, it’s another standard - maybe even two or three.

     
  • September 6-9, 2015 in Waterford, IE. €1,000 but you get a lot for it.

     
  • October 1 & 2, 2015 in Portland, Maine. Call for proposals here.

     

  • Usually, instead of aggregating  ALL of the data from all of the sensors (think about what that would mean for GE’s Durathon battery plant, where 10,000 sensors dot the assembly line!), the data is originally analyzed at “the edge,” i.e., at or near the point where the data is collected. Then only the data that deviates from the norm (i.e., is significant)  is passed on to to the centralized data bases and processing.  

    That’s why I’m so excited about Egburt, and its “fog computing” sensors. As with sooo many aspects of the IoT, it’s the real-time aspect of small data that makes it so valuable, and so different from past practices, where much of the potential was never collected at all, or, if it was, was only collected, analyzed and acted upon historically. Hence, the “Collective Blindness” that I’ve written about before, which limited our decision-making abilities in the past. 

     
  •  
  • A lot of Smart Home stuff is dubious in value. But that’s OK, as long as the price of adding connectivity to the Thing gets low enough. And this is the time for experimenting with Things.


    A few years back, someone sent me a news release about a Wi-Fi-enabled slow cooker. I was intrigued, but I ultimately declined the offer to test it, for one simple reason: I couldn’t figure out what I’d do with a Wi-Fi-enabled slow cooker that I wouldn’t be able to do with a regular one.


    I’ll be even more interested to see what other uses manufacturers manage to find for Wi-Fi. There have to be a lot of things that we could do with networked kitchen gadgets, if only some bright folks in the labs could figure out what — and explain it to consumers. But I suspect this will take some time, precisely because Wi-Fi has the potential to be so transformative: Really using its capabilities may, in many cases, mean re-imagining the entire appliance. And American consumers aren’t all that imaginative about their kitchens, so imagining is just the first step. Getting the things onto countertops and teaching consumers to cook differently will take even more time than inventing the next great kitchen app.

     
  • Adventures in Smart Scales (I sympathize).


    Unfortunately this isn’t always the case. I was a little alarmed to have Fitbit tell me that my partner, who was in different city at the time, had used my scale late at night. The person using the scale must have been equally alarmed when the scale greeted them using the wrong name.

    …In the case of my Aria scale, I didn’t realise my daily log was being shared, and the scale’s guests have no idea that I can easily check their weight. Products that share any data between multiple users based on their household proximity or family relationship have a responsibility to communicate clearly and upfront what exactly is being shared and how.

     
  • Interesting. I’m using a passwordless system with HomeStar with texting a numeric code one of the options.

     
  • Another Smart Thermostat (that almost certainly won’t work in my home). They’ve announced an IFTTT integration and an API. It’s not entirely clear where the API actually is: on the LAN or in the Cloud? 

    Someone has already hacked their own LAN API.

     
  • PDF. Legal stuff.


    This Article argues that the evolution of software—and the looming age of the “Internet of Things”—will allow manufacturers of software and of consumer goods to make use of consumer monitoring technologies and restrictive software licenses to more perfectly price discriminate. A number of commentators are urging changes in the law to prevent monitoring and restrictive software licenses. This Article takes a novel and contrarian view by explaining that the current law surrounding software licensing, which will facilitate more perfect price discrimination as technology evolves, is mostly beneficial. Because the marginal cost of software distribution approaches zero, facilitating more perfect price discrimination is particularly valuable to society because it facilitates much more widespread distribution of software—especially to poorer consumers. Some commentators worry that as more and more consumer goods contain software, manufacturers will use restrictive software licenses in an attempt to control consumers’ abilities to use and resell consumer goods. This Article explains that this generally will not happen because it would be against the manufacturers’ financial interests. We show that in some cases, manufacturers will indeed restrict use of a product to facilitate their ability to engage in price discrimination. The Article argues that such price discrimination will likely be welfare enhancing and will definitely improve cross-subsidization from rich to poor so that poor consumers can get more products for lower prices. The Article also demonstrates that the traditional policy reasons to disallow restraints on personal property do not apply to software-enabled devices. We conclude that rather than discouraging the use of restrictive software licenses, the law should adapt to better facilitate such licenses and the more perfect price discrimination that goes with them.

     
  • Interesting. Similar to Paho?


    The Vortex Gateway addresses the problem of making data seamlessly flow across systems and technologies while adapting format, content, and QoS. The Vortex Gateway is the best choice for integrating DDS based systems with other messaging technologies, such as JMS, as well as for integrating with proprietary and Web Technologies such as W3C Web Services and RESTful Web Services.

     
  • TL;DR massive interest on Stack Overflow, O’Reilly Strata, and Hacker News - despite surprisingly little commercial interest. FYI: “Apache Spark is a fast and general engine for large-scale data processing”. 

     

  • The Azure IoT Suite is an integrated offering that takes advantage of all the relevant Azure capabilities to connect devices and other assets (i.e. “things”), capture the diverse and voluminous data they generate, integrate and orchestrate the flow of that data, and manage, analyze and present it as usable information to the people who need it to make better decisions as well as intelligently automate operations…

    Additionally, the Azure IoT Suite will provide a simple and predictable pricing model despite the rich set of capabilities and broad scenarios it delivers, so our customers can plan and budget appropriately. This approach is aimed at simplifying the complexities that often exist with implementing and costing IoT solutions.