1.3.0
This minor release introduces the following new features
- The LoraWAN protocol adapter now supports the ChirpStack provider.
- A MongoDB based implementation of the Tenant, Device Registration and Credentials APIs.
- MQTT adapter supports transformation of uploaded messages usign an external service (experimental)
- Protocol adapters can now rewrite addresses when opening links to the AMQP 1.0 network
The project leadership certifies that the APIs in this release are "Eclipse Quality".
As part of the 1.3.0 release we have made some changes regarding the way that command messages are being routed to devices. Protocol adapters no longer create distinct command receiver links per tenant but instead maintain a single command receiver link for all tenants. Command messages are routed based on information kept in the Device Connection service where individual devices are mapped to the protocol adapter instance that they are connected to. This way, the load on the Qpid Dispatch Router instances is further reduced because the number of links is now proportional to the number of protocol adapter instances instead of the number of tenants.
The logic for routing commands to target protocol adapter instances is currently implemented as part of Hono's standard protocol adapters. This makes it hard to implement (custom) protocol adapters using other programming languages because this logic would need to be re-implemented. We are therefore already discussing plans to rename the Device Connection service to Command Routing service and move all routing logic to it. This way, the routing would be isolated in one place and we could more easily improve the routing logic without affecting adapters.
The CoAP adapter now has a proper User and Admin Guide.
The LoRa adapter is still considered experimental which is also reflected by the fact that there exists no documentation yet. Nevertheless, some work is going on to make it easier to support additional LoRa providers in the adapter.