1.4.0
This minor release introduces the following new features
- The protocol adapters now report connection attempts made by devices in a new metric. In particular, the metric includes a tag reflecting the outcome of the attempt to establish a connection and the reason for failure.
- A new Quarkus based HTTP protocol adapter is now available. This adapter version provides better memory consumption and startup times comparing to the existing one.
- The LoraWAN protocol adapter has been extended with support for the Actility Enterprise provider.
- The LoraWAN protocol adapter has been extended with support for the Orbiwise provider.
- Added metrics for tracking the RTT between sending an AMQP message to receiving the disposition.
- The CoAP adapter now supports configuration of the timeoutToAck parameter at the tenant level
in addition to the adapter level. If set, the tenant specific value is used for all devices of the
particular tenant. If not set, the value defined at the adapter level is used. - The Device Registry Management API has been extended now to support searching devices for a tenant with optional filters, paging and sorting options.
- The MongoDB based device registry now supports searching devices for a tenant with optional filters, paging and sorting options.
In addition to the new features, several bugs have been fixed.
The project leadership certifies that the APIs in this release are "Eclipse Quality".
The newly added Quarkus based HTTP adapter is the beginning of an ongoing effort to migrate all Hono components from Spring Boot to Quarkus. One of the main drivers for doing so is the reduced startup time due to the fact that Quarkus does not rely on reflection for dependency injection. We also hope that we can reduce the memory footprint of the components significantly, in particular once we are able to produce native (container) images. We will keep shipping the original Spring Boot based images unitl all components have been migrated.
The protocol adapters support the singleTenant configuration property which allows devices to omit the tenant identifier from endpoint addresses for publishing data and receiving commands. This feature has been deprecated with 1.4.0. We have no indication that anybody is using this (undocumented) feature so we will remove it in 1.5.0 altogether. It is, of course, still possible to run Hono with just a single tenant (explicitly) configured.