-
Notifications
You must be signed in to change notification settings - Fork 5
Interfaces
The Asset Tracking Management testbed can be extended in several ways. This page aims at listing the different interfaces in place.
Out of the box, any TI SensorTag sensor(s) in proximity of an Eclipse Kura gateway running the "com.redhat.iot.demo.package" app and with BLE enabled, will be collecting values and uploading them to the Kapua/EDC cloud backend. Values reported to the cloud are: humidity, light, and ambient temperature (see "Interface to the cloud" section below).
In order to add support for other kind of shipment sensors to the testbed, one will need to develop a Kura plug-in that interfaces with the sensor on one hand, and publishes data using the Kura CloudService on the other.
Depending on the sensor technology, different protocols might be considered. Below is a quick reference of the protocols supported in Kura and associated API and documentation/examples:
- Bluetooth Smart / BLE: API, sample code.
- SPI, I2C, GPIO: through the Device I/O API
- CAN-bus: API
- OPC-UA:
- Modbus: API, sample code
Data is being pushed from the Eclipse Kura gateway over MQTT, using Kura's MQTT topic & payload format. The Kura payload is a set of metrics corresponding to the different values being sensed (e.g "Acceleration X", "Humidity", "Ambient" temperature, "Pressure", …).
Depending on the sensor effectively being used, different metrics might be collected. At a minimum, it is expected that the following metrics will be reported:
- "Humidity" - humidity level (float: 0-100)
- "Light" - light level in lx (float)
- "Ambient" - temperature in C (float)
The topic where data is being published should be of the form:
{accountName}/{deviceId}/demo-kit/assets/{asset-id}
- Account name:
eclipse - Device ID: The ID of the device/gateway that is publishing the data, ex.
john-raspberry-pi - Asset ID: The UUID (e.g MAC address) of the asset being tracked, ex.
B0:B4:48:00:00:09
If you are interested in joining the Testbed and connecting your own solution, please contact benjamin@eclipse.org to get the credentials you will need for publishing to the cloud backend used by the sandbox.
Data uploaded from the gateways is made available through Eclipse Kapua's REST API, as well as directly by the MQ broker in case one wants to access raw streaming data. More information on the REST API can be found in the Eclipse Kapua user guide.
If you are interested in joining the Testbed and connecting your own solution to the publicly hosted version of the testbed, please contact benjamin@eclipse.org to get the credentials you will need for connecting your field devices/gateways and start using the APIs.