BLOG / Oct 2015
/
wot.io,
shipiot,
ti,
texas instruments,
sensortag,
cc2541,
cc2650,
beagleboard,
beaglebone black,
node.js,
python,
devicehive,
device management,
bluetooth,
bluetooth low energy,
nest,
demo,
tutorial,
circonus,
scriptr,
bip.io,
javascript
/ Posted By: wotio team
Hardware Recap In Part One of this demo, we took two Texas Instruments Sensortags, connected them using Bluetooth LE to a Beaglebone Black, ran a Node.js gateway to connect to DeviceHive1, and saw it all work. This is the diagram of our hardware setup, as completed at that point: Fantastic!...
One of the key benefits wot.io provides is interoperability between different connected device platforms. One really interesting advantage of the wot.io architecture is that it allows developers to take both IoT data from connected devices as well as data from web-based feeds and combine them in interesting ways using dynamic...
This post is part 2 of our series on connecting gaming devices with the wot.io data service exchange™. Routing Gameplay Event Data with wot.io In the last post we saw that after retrofitting an open source chess application to connect via PubNub, connecting data services was easy since wot.io already...
BLOG / Dec 2015
/
Smart City,
ARM,
ARMmbed,
scriptr,
bip.io,
thingworx,
Elasticsearch
/ Posted By: wotio team
Data Service Providers In part 1 of this series, we went over the various ARM devices that were combined with open data from the London Datastore to represent the connected device side of our demo. In part 2, we described how to use employ one or more device management platforms...
BLOG / Dec 2015
/
MQTT,
protocol adapters,
Elasticsearch,
thingworx,
bip.io,
scriptr,
ARM
/ Posted By: wotio team
One long-overdue lesson that the Internet of Things is teaching younger engineers is that there are a whole host of useful protocols that aren't named HTTP. (And don't panic, but in related news, we have also received reports that there are even OSI layers beneath 7!) Since we have posted...
