I just finished integrating a demonstrator system that implements the OneM2Mstandards for connected devices, using the oneMPOWER platform. It’s a very complex, enterprise-level protocol and suite of specifications, and is designed for seriously large systems.
Winter is coming, and the Northeastern United States where I live can get cold! And the houses are often old and drafty. So I built a wireless sensor system tied to a Nest thermostat to keep me cozy, wherever I am in the house, instead of keeping my thermostat cozy, bolted to its wall.
Yeah, they call it Bluetooth Smart now, but I don’t like that name! LE for me. 😉
DeviceHive managed the device registration for Sensortags, to make it easy to add new tags and wrangle them, and the wot.io data service exchange piped the messaging to scriptr for some transform logic in a convenient cloud service. bip.io did visualization and Nest control, and Circonus handled data logging and analytics.
Update: I have a forthcoming three-part series of articles on Texas Instruments’ e2e blog that dives into some of the hardware engineering behind this, too. I’ll link them here when it’s finally published!
I’m a coffee snob. I admit it. I’m proud of it. Although, upon reflection I really think it boils down to appreciating deliciousness. And who wouldn’t?
I discovered my drip coffee maker sucks at temperature regulation, and my pourover and French press technique has improved quite a bit. So has the coffee!
Another recent demo I created used the Mediatek LinkIt One, which is an awesome little Arduino-compatible dev board that integrates a ton of useful hardware like GPS, GSM, WiFi, etc. With a tiny bit of code and some cloud data services connected via a flexible message bus, I had a prototype system up and running fast. It’s very simple in the first iteration, parsing NMEA sentences from the GPS unit, extracting data, and sending it off to logic and alerting powered by the data services. I’m still working on refining this, as it’s an itch I want to scratch for my own use.