2018 Release notes

Dec 10th, 2018

The new service release comes with various changes, as for example:

  • Deletion of a namespace
    This includes the full deletion of all entities whithin this namespace
    Find details at Solutions - Namespaces
  • Preparation for ready-to-use telemetry and command and control scenarios in coop with Bosch IoT Hub
  • Changes on the service broker for the Bosch IoT Cloud

At this occasion, various minor bugs have also been fixed.

Nov 27th, 2018

The new service release comes with various changes, as for example:

  • Booking a Starter service plan via AWS Marketplace
    Starting point is https://bosch-iot-suite.com/things
  • New support of Hub command and control scenarios.
    Try it out by creating a new Hub connection via Dashboard > Solutions > Connections.
  • New structure of our documentation pages.
    Use the search in case your old bookmarks are outdated.

At this occasion, various minor bugs have also been fixed.

Nov 8th, 2018

The new service release comes with various changes, as for example:

  • Booking Free service plan for AWS
    Starting point is https://bosch-iot-suite.com/things
  • Protocol enhancement
    A new thing can be created with a new policy, which is copied from an already existing thing.
    The parameter is called _copyPolicyFrom and can hold:
    • either the policy ID itself,
    • or the thing ID, using the notation {{ ref:things/[thingId]/policyId }}
  • HTTP API for Relations deprecated
    Find details at Relations - deprecated
  • New Swagger UI based on Open API 3
    Find details at HTTP API updates
  • New Things-Client 3.2.1 which fixes a minor reconnection bug.
    Find details at Things-client 3.2.

At this occasion, various minor bugs have also been fixed.

Oct 22nd, 2018

The new service release comes with various changes, as for example:

  • Device-authorization for integration with Bosch IoT Hub based on “same ID convention”
  • Memory consumption in gateway for search operations
  • Placeholder for the solution ID {{ request:subjectId }}
    The previous notation ${request.subjectId} is deprecated.
  • Preparations for booking Free service plan for AWS

At this occasion, various minor bugs have also been fixed.

Oct 1st, 2018

The new service release comes with following changes:

  • New MQTT connections.
    Find details about the MQTT 3.1.1 binding, which can be used for messages from and to an external MQTT service.
  • New conditional headers If-Match and If-None-Match at the HTTP API.
    Find details at Updates at the HTTP API.
  • New Things-Client 3.2.0 which supports conditional requests via the Java API and event filtering.
    Find details at Things-client 3.2.
  • Enhancement: The solution management UI supports authentication via Bosch ID. Additionally there will be also a policy at solution level.

At this occasion, various minor bugs have also been fixed.

Aug 16th, 2018

The new service release comes with following changes:

  • New Things-Client 3.1.0 which supports managing feature “definitions” via the Java API.
    (This was previously only available via the HTTP API.)
    Find details at Things-client 3.1.
  • New placeholder approach for connections, to allow more fine-grained per-device access control.
    Subjects for incoming messages (sources) can be configured separately to subjects for outgoing messages (targets).
    Find details about placeholders, which can be used for authorization subjects for sources, and placeholders, which can be used for targets.
  • Documentation of header fields used by the Things service,
    which your applications should avoid to set.
    Find details at Protocol specification.

At this occasion, various minor bugs have also been fixed.

July 18th, 2018

The new service release comes with following changes:

  • New user interface to easy managing permanent connections with external systems
    Find details at Manage your connections.
  • New sub-resource at HTTP API to manage permanent connections
    Find details at Solutions resources.
  • Support for payload transformation for messages
    • Incoming messages that require mapping from their binary or text representation before being applied on the digital twins
    • Outgoing messages that can be mapped from our normalized format to the structures you need
    • The transformations are defined using JavaScript and are applied automatically on each incoming/outgoing message without the need for you to setup/provide a separate runtime environment.

Highlight: Integration with Bosch IoT Hub - another service of the Bosch IoT Suite family.

June 30th, 2018

In case you are using a free or starter service instance and need to manage your namespace, you might be affected of our latest change. Find details at Manage your namespace.

 

May 21st, 2018

The Bosch IoT Suite portal offers the possibility to subscribe a free service instance of various services of the Suite family.
Starting May 21, setting the namespace is not any longer enforced while booking the Bosch IoT Things free plan, but you can do it at a later point in time.
Find details at How to book the service?

 

April 26th, 2018

The new service release comes with following changes:

  • Support for AMQP 0.9.1 connectivity
    Find details at Protocol bindings.
  • Dashboard in new Bosch style.

At this occasion, various minor bugs have also been fixed.

February 8th, 2018

The new service release comes with following changes:

  • New search parameter at the HTTP API
    Find details at Search > namespaces.
  • Refined concept of the feature definition
    Find details at Feature definition.
  • HTTP messages resources support the request-response pattern as well as fire-and-forget semantics.
    Find details about the optional timeout parameter at Messages resources

At this occasion, various minor bugs have also been fixed.

January 17th, 2018

The new service release comes with following highlights

  • Java API and Client
    • New things-client and things-client-api:
      • New Maven coordinates, see Bosch IoT Things Java API.
      • Provides more features, see Which API to use?
      • Support now twin and live communication
      • Use Eclipse Ditto dependencies under the Eclipse Public License v 2.0.
    • The previous Java client and API are deprecated
      • cr-integration-client - deprecated
      • cr-integration-api - deprecated
      • cr-model - deprecated
      • cr-json - deprecated
    • Find migration details at Bosch IoT Things Java API > Things-client 3.0
  • Updates at the HTTP API 2
    • All entities need a specific namespace as a prefix of their ID.
      Find a summary at News > Namespaces.
    • Policies: The usage of a JWT issuer as a subject ID prefix is deprecated.
      We recommend to adapt your existing policies according to the Policies documentation.
    • Solutions: Reserve various namespaces for a solution and define a default namespace.
      See Solutions resources.
      The Manage your solution UI was updated respectively to support you on such tasks.
  • WebSockets protocol:
    • The new Live channel allows to send commands and messages directly to a live device.
    • Now that we have incorporated the Eclipse Ditto artifacts at our core, the Things service fully uses the Ditto protocol.
      Find details at WebSocket binding.

January 3th, 2018

The new service release comes with various bug fixes and operational improvements.

Archive 2017

Archive 2016

Archive 2015