- Scheduled Reboot service: when configured, allows rebooting the gateway based on a
temporal basis specified by a CRON expression
- RPMs: This release will provide RPM packaging for all the supported platforms.
- Diagnostics bundle: included in all system distributions
- H2 Databases: This release will see the switch from HSQLDB to H2. This migration will allow for a number of performance improvements as well the ability to maintain multiple database instances.
- REST API for Kura Drivers and Assets: To allow more flexibility, REST endpoints will be added to Kura for interacting with the Kura Drivers and Assets instances.
- Embedded Artemis Broker: The addition of the Apache Artemis Broker will extend Kura's
- BLE via TinyB: To improve the reliability of BLE, Kura will switch to the TinyB library to support BLE via Bluez.
- Web UI Update: A new UI element will be added for managing and editing Drivers and Assets.
- S7 Industrial Protocol: A new driver will be added to the Eclipse Marketplace to support S7.
- BLE/SensorTag: A new driver will be added to the Eclipse Marketplace to support BLE on the TI SensorTag.
- MQTT publish rate improvement: A limit parameter will be added to the MQTT transport service to allow throttling of MQTT messages to prevent unnecessary congestion on the MQTT broker.
- Connection Monitor: A connection monitor will be introduced to the DataService to further improve connectivity reliability.
- BoltGATE 20-25 support.
- Terminal Services: Multiple instances, XON/XOFF support, and extra low-level options for socat.
- ESF v5.1.0 does not introduce API breakage with previous releases.
- This release does introduce a new set of APIs for TinyB for interacting with BLE devices.
Support for previous BLE APIs will still be present and functional.
- In ESF v5.1.0 it is possible to instantiate a Driver instance from the Drivers and Assets
section or from Wire Composer only if the following requirements are met:
- the Driver implementation class must implement the following interfaces:
- ConfigurableComponent or SelfConfigurableComponent
- the Driver must provide a component definition XML file that advertises that
the interfaces mentioned above are provided and that sets "required" as configuration policy.
It is advisable to update the deployment packages of non-compliant drivers if needed.
It is still possible to instantiate non-compliant drivers using the "+" button under "Services".