[hono-dev] Eclipse Hono 1.3.0-M1 Milestone

["Hudalla Kai (IOC/PAP-HU)" <Kai.Hudalla@xxxxxxxx>]

Dear Hono community,

today we have created version 1.3.0 milestone 1 of the Eclipse Hono [1]
project.

Hono aims at providing uniform service interfaces for connecting large
numbers of IoT devices to a (cloud) back end. It specifically supports
scalable and secure data ingestion (telemetry data & events) and also
supports sending messages to devices.

Here are the release notes for the changes and improvements since 1.2.2
which are contained in this milestone:

New Features

* The LoraWAN protocol adapter has been extended with support for the
  ChirpStack provider.
* Hono's integration tests can now be run with a Jaeger back end in
  order to collect tracing information.

Fixes & Enhancements

* An admin guide for the CoAP adapter has been added.
* The Prometheus based resource limits checker now supports configuring
  a query timeout.
* When sending a command message to a device, the AMQP adapter now waits
  for a configurable period of time (default is 1 second) for the
  acknowledgement from the device.
  If none is received, the AMQP link to the device for sending commands
  is being closed.
* The client for storing device connection information to a data grid
  now supports configuring the name of the cache to store the data in.
* When the connection to a device is closed or lost, a protocol adapter
  instance will now stop listening for commands targeted at the device.

API Changes

* The getRemoteContainer method in
  org.eclipse.hono.client.HonoConnection has been renamed to
 getRemoteContainerId.
* The getName method in org.eclipse.hono.connection.ConnectionFactory
  has been removed and an additional connect method has been added.
* The "set command-handling protocol adapter instance" operation of the
  Device Connection API has been extended to support an additional
  parameter which can be used to indicate the maximum amount of time
  that the given information is to be considered valid.

Binary artifacts are available from the Eclipse Repository [4] and from
Maven Central [5].

However, the easiest and preferred way of using Hono is by
means of using the Helm chart that is available from the Eclipse IoT
Packages project. Installation instructions can be found in the Hono
Deployment Guide [6]. Plain Docker images are also available from Docker
Hub [7].

If you want to give Hono a try, please follow the Getting Started guide
on the project web site [8].

Please refer to the project page at Eclipse [9] for Hono's release plan.

[1] https://www.eclipse.org/hono
[4] https://repo.eclipse.org/content/groups/hono/
[5] https://search.maven.org/search?q=g:org.eclipse.hono
[6] https://www.eclipse.org/hono/docs/deployment/helm-based-deployment/
[7] https://hub.docker.com/u/eclipse/
[8] https://www.eclipse.org/hono/getting-started/
[9] https://projects.eclipse.org/projects/iot.hono/governance

-- 
Mit freundlichen Grüßen / Best regards

Kai Hudalla

Software Developer - Bosch IoT Hub

Bosch.IO GmbH
Ullsteinstr. 128
12109 Berlin
GERMANY
www.bosch.io

Registered Office: Berlin, Registration Court: Amtsgericht
Charlottenburg; HRB 148411 B
Chairman of the Supervisory Board: Dr.-Ing. Thorsten Lücke;
Managing Directors: Dr. Stefan Ferber, Dr. Aleksandar Mitrovic, Yvonne
Reckling