• Sorry for the length excerpts below, it took me a bit of reading to get my head around this. This is article talks about how to handle data coming from edge devices, and claims there are two models.The “Pass Thru” model just filters the data around rules and passes what is appropriate; the “REST” model sucks all the data in to the vendor’s cloud and then presents an API to access that data. 


    The idea is that there is a [Application Enablement Platform (AEP)] made up of an edge agent on one side and cloud storage and API servers on the other. The small device side agent is placed on an IoT edge device…. That edge agent exposes an application level API to the IoT application itself and it hides the “complexity” of the cloud protocol from the application. In this manner it simplifies the edge device on-boarding and the secure sending of data from the edge device to the AEP cloud platform.


    On the cloud side the AEP’s have two main data handling strategies: “Pass thru” and “at Rest”.

    In the “pass thru” model the AEP is an intelligent pipe that is in essence a smart 2-way filter and applies rules as to when to actually transport the data from the edge device to the customer’s back-end and back. For example in the pass-thru model one could tell the AEP to pass temperature readings to an gas tank monitoring service only if the temperature exceeds 32 degrees C two times in a row and in this case to also configure the edge device accept a command to activate a cooling mechanism originating from the customer’s back-end. This allows a service provider to take an edge device and quickly integrate new business logic on top of an existing back-end and implement an over the top IoT solution.

    The second data handling strategy is the “at REST” strategy. In this case the customer’s edge devices do not send the data directly to the customer’s back-end, rather they send them to the AEP cloud. The AEP stores all the customer’s data and handles all issues of scale,  secure transmission and data storage. The AEP in turn exposes a set of web service APIs on top of which the customer back-end application can be built.

     
  • Interesting article on the state of IoT Platforms. Too long to summarize. Includes a meta-directory of IoT Platforms.

     
  • Another hmmm, wot?


    One example would be your fridge self-regulating its heating settings by “chatting” with thermostats in your kitchen or checking the weather conditions using Wi-fi to save energy and costs.

     
  • It’s a Raspberry Pi based voice recognition system Kickstarter. Doesn’t ship until next summer though. $25 for early access to the software, $100 ($130 after early bird) for the hardware. With 10 days to go, they’re still $25K short of their $100K goal unfortunately.

    The advantage of a system like this is you lose the Internet dependency for hardware like the Amazon Echo.

     

  • Autodesk said it will sell and support the SeeControl platform and integrate the technology in its design tools for manufacturing and building industries. The aim would be to allow designers to create structures that would incorporate the Internet of things. SeeControl is a white label, cloud platform used by industrial product makers looking to integrate smart sensors and services.

     
  • Notes: 1

    Tags: Administrivia

    Back!

    Spent the last week racing sailboats. 

     
  • TL;DR they can make service calls, which are actually useful.

     
  • Choose from Apple’s HomeKit, Google’s Brillo, Intel’s IoTivity, or Qualcomm’s AllJoyn. It would be more fun if they showed what Things are actually supported. Also, why not Samsung’s SmartThings?

     
  • Notes: 1

    Tags: RFIDDIY

    DIY stuff, because I plan to play with RFID in the fal..

     
  • It’s about really really good WiFi? I dunno, I got nothing.

     
  • Of note, medicine, privacy and security are mentioned, but you probably just want to read the whole thing. No major new ground covered here.

     
  • Now called “Samsung Smart Things Hub”, costs $99, works with the Amazon Echo. No shipping date? First comment on the announcement is “one thing I can’t seem to find in the description…what does the new hub do that the old hub doesn’t do?” of which there’s a hint that it doesn’t have a cloud dependency.

     
  • Ummm.

     

  • Rather than discarding this forgotten batch, they decided to test it by building batteries using these particles. It turns out they have potentially solved the problem of using aluminum for the anodes in the battery. The extra long soak meant the anodes did not expand and contract, in fact they created a battery that over 500 charge/discharge cycles retained up to four-times the capacity of the equivalent graphite anode batteries. These batteries last considerably longer in terms of usable lifespan and, according to MIT, can hold up to three-times the energy.

     
  • Good article, read. We need Connected Devices, not Smart Ones. If there’s multiple Smart Things competing for control of the house, it’s impossible for us to have a “mental model” of how it’s actually working = confusion & agony.