The latest update of the Bosch IoT Suite for Asset Communication package documentation, comes with various changes:
Hub to Things connection configuration change
Starting with 29 .09.2020 the default configuration of a connection established automatically after booking the Bosch IoT Suite for Asset Communication package, named “Devices via Bosch IoT Hub” has changed.
We have simplified the “to” header mapping for connection targets. Further, the implicit provisioning at the level of the Hub-Thing connection is now enabled by default.
Old versions are not migrated automatically. In case you create a new connection, it will get the new default configuration. Don’t forget to transfer afterwards all your custom settings and do disable or delete the old connection.
Tip: Choose the exactly same authorization subject, thus you avoid migrating the polices of your things.
The new and old configuration settings are documented at Hub to Things connection at Hub to Things connection – deprecated 2020-09.
Default policy change
Starting with 21 .09.2020 the default policy of things created via Device Provisioning API has changed.
In order to make implicit provisioning even easier, the “Devices via Bosch IoT Hub” need read permission on the policy to copy from. Therefore, the section DEVICE have now read permission on the policy:/ path.
Old things are not migrated automatically. In case you create a new thing, the new policy is created.
Bosch IoT Edge
Starting with version 10.2 Bosch IoT Gateway Software is becoming Bosch IoT Edge Services.
Full documentation on using the advanced edge services is available at the Bosch IoT Edge Services documentation.
Update in Digital Twin model mapping specification
The latest update of the Bosch IoT Suite for Asset Communication package documentation, comes with a new recommendation for Eclipse Vorto Information Models: use UpperCamelCase for the Function Block IDs.
As the upper and lower cases will be preserved, your feature ID will also be in UpperCamelCase; this improves readability.
See Specification digital twin model mapping.
The MightLamp example at https://vorto.eclipse.org/#/details/org.eclipse.ditto.examples:MightyLamp:2.0.0 is publicly visible.
At this occasion, various minor bugs have also been fixed.