With all the challenges inherent in M2M, how does a developer focus on the areas where he or she is most needed? How is their time best used?
Controlling a dispersed, wirelessly connected field of devices is a daunting task. DeviceHive has already absorbed some of the time-consuming procedural work and developed an open source framework that can effectively manage such M2M connections. By laying the groundwork, it allows developers to put aside the implementation of protocols and messaging libraries and focus on the main functionality of the system.
In the following example, an EZ-430-Chronos watch - as a data source - is connected to an Android smartphone using Bluetooth. The data is available from anywhere in the world. Moreover, it is possible to access the worn device through a browser without resorting to any special technologies. It is accessed by way of a cloud API, an administrative portal, and a set of components and descriptions, including open descriptions of the exchange protocols used. This example shows how DeviceHive can be used remotely.
- Display acceleration divided by three axes from a built-in accelerometer in real time.
- Turn on the feature to control a computer mouse using the accelerometer (quite an interesting possibility, which may be useful for remote control).
- Configure a profile for remote control of PC programs using the watch’s buttons (iTunes and Media Player as an example).
- Synch the date/time with a computer.
- Emulate external wireless sensors.
- Wirelessly upgrade the firmware.
Imagine all the different tools this development would normally require. How much time would have been lost to integration with client/server software, data carriers and all the different hardware?
- Connection of embedded Linux using Python or C++ libraries and JSON protocol, or connection with different types of 8, 16, 32 bits microcontrollers, like AVR, STM8, PIC. These devices using lightweight C libraries and BINARY protocol
DeviceHive has also developed gateway middleware that allows interfacing with devices connected to it. Again, this will streamline the process of re-creating security and user protocols, and eliminate other basic coding tasks for each new solution.
DeviceHive makes building M2M solutions simple and transparent. Once you install all DeviceHive components, you can use an easily adjustable API to organize queing and delivery of commands between devices and client applications. You can download everything needed to start working with DeviceHive Github.
Leave the communications to DeviceHive so you can focus on product and innovation!