Skip to content

2.2.0

Compare
Choose a tag to compare
@sophokles73 sophokles73 released this 29 Nov 14:14
· 234 commits to master since this release

New features

  • All Hono components now support reading ECC based keys from PEM files that contain the Base64
    encoded DER-encoding of an ECPrivateKey as described in
    RFC 5915, Section 4.
  • The build process now supports creating container images for the arm64 platform. Please refer to the
    Developer Guide for details.
  • The LoraWAN protocol adapter has been extended with support for Chirpstack V4 provider.
  • Hono components now support producing JSON formatted log messages. Please refer to the
    Admin Guide for details.
  • Hono components can now be configured to use the OTEL Jaeger Remote Sampler extension which allows
    the sampling strategy to be retrieved from a Jaeger back-end dynamically during runtime.
    Please refer to the Admin Guide for details.

Fixes & Enhancements

  • Documentation for versions up to 1.11 is removed as outdated.
  • Optimized handling of MQTT and AMQP protocol adapter shutdown. The purpose is removal of redundant
    operations for devices which maintain a permanent connection during the restarting of adapter
    instances. This prevents delays and possible errors due the higher rate of invocations of the
    unregister Command Consumer operation on the Command Router service.
    When shutting down, the adapters no longer explicitly unregister Command Consumers and no longer send
    disconnectedTtdEvents. Instead, the Command Router now sends the connectedTtdEvent and
    disconnectedTtdEvent on behalf of the protocol adapters.
    The Command Router now also sends a disconnectedTtdEvent when a command is received that is
    targeted at a device that got disconnected (and didn't reconnect) when a protocol adapter was
    shut down. This happens only once - during the processing of the first command.
    The Command Router configuration now also requires hono.messaging configuration if AMQP 1.0
    based messaging infrastructure is being used.
  • The Mongo DB based device registry is now continuously tested to work with Mongo DB 5.0.