Everyware Software Framework Developer's Hub

Everyware Software Framework (ESF) is an enterprise-ready IoT Edge Framework distributed and supported by Eurotech. Based on Eclipse Kura, the open source Java/OSGi middleware for IoT gateways, ESF adds provisioning, advanced security, remote access, diagnostics monitoring. It supports ready-to-use field protocols (including Modbus, OPC-UA, S7, FANUC, J1939, J1979, BACnet, IEC 60870-5-101, IEC 60870-5-104, DNP3, M-bus), MQTT connectivity, and a web-based visual data flow programming to acquire data from the field, process it at the edge, and publish it to IoT Cloud Platforms. ESF features full remote device management through its integration with Everyware Cloud, Eurotech’s IoT Integration Platform.

Get Started

Ti SensorTag Driver

ESF provides a specific driver that can be used to interact with Texas Instruments SensorTag devices. The driver is available only for gateways that support the new Bluetooth LE APIs.
It can be used in to the Wires framework, the Asset model or directly using the Driver itself.


The SensorTag driver can be used only with TI SensorTags with firmware version >1.20. If your device has an older firmware, please update it.


The SensorTag Driver can be used to get the values from all the sensor installed on the tag (both in polling mode and notification):

  • ambient and target temperature
  • humidity
  • pressure
  • three-axis acceleration
  • three-axis magnetic field
  • three-axis orientation
  • light
  • push buttons

Moreover, the following resources can be written by the driver:

  • read and green leds
  • buzzer

When a notification is enabled for a specific channel (sensor), the notification period can be set.


As the others Drivers supported by ESF, it is distributed as a deployment package on Eclipse Marketplace. It can be installed following the instructions provided here.

Instance creation

A new TiSensorTag Driver instance can be created either by clicking the New Driver button in the dedicated Drivers and Assets Web UI section or by clicking on the + button under Services. In both cases, the org.eclipse.kura.driver.ble.sensortag factory must be selected and a unique name must be provided for the new instance.
Once instantiated, the SensorTag Driver has to be configured setting the Bluetooth interface name (i.e. hci0) that will be used to connect to the device.

Channel configuration

The SensorTag Driver channel can be configured with the following parameters:

  • enabled: it allows to enable/disable the channel. If it isn't selected the channel will be ignored.
  • name: the channel name.
  • type: the channel type, (READ, WRITE, or READ_WRITE).
  • value.type: the Java type of the channel value. The value read by the Driver will be converted to the value.type. Conversely, in write operations the Driver will accept value of this kind.
  • listen: when selected, a listener will be attached to this channel. Any event on the channel will be reported using a callback and the value will be emitted.
  • sensortag.address: the address of the specific SensorTag (i.e. aa:bb:cc:dd:ee:ff)
  • sensor.name: the name of the sensor. It can be selected from a drop-down list
  • notification.period: the period in milliseconds used to receive notification for a specific sensor. The value will be ignored it the listen option is not checked.

Updated about a year ago

Ti SensorTag Driver

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.