This offer is only addressed to commercial customers including freelancers and entrepreneurs. All prices are exclusive of value added tax (VAT).
  • Share via email
  • Subscribe to blog alert

Eclipe Vorto and Device Provisioning API changes

The offering at https://github.com/eclipse/vorto/tree/development/models/#/ will be discontinued.

Please migrate your models to https://github.com/eclipse/vorto/tree/development/models until June 30, 2021.

 

The Device Provisioning API v1 has been improved to allow referencing a Github repository hosting predefined models, from where we can derive a thing structure.
This is achieved by offering a new optional parameter definitionResolver.


Example

Let us assume you want to provision a new device based on a model which is already available in the Eclipse Vorto Github repository, e.g.
https://github.com/eclipse/vorto/tree/development/models/com.bosch.iot.suite.example-VirtualDemoDevice-2.0.0.infomodel

Activate the new parameter¬†definitionResolver to “vorto”.

The request body might look like in the following snippet:

{
  "id": "my.demo.namespace:my-device-4711",
  "hub": {
    "device": {
      "enabled": true
    },
  "credentials": {
    "type": "hashed-password",
    "secrets": [
      {
      "password": "yourPassword"
      }
    ]
   }
  },
  "things": {
    "thing": {
      "definition": "com.bosch.iot.suite.example:VirtualDemoDevice:2.0.0"
      "attributes": {
        "manufacturer": "Robert Bosch GmbH"
      }
    }
  }
}

Upon success you will get status code 201, the JSON result aggregated from Bosch IoT Hub and Bosch IoT Things, as well as various response headers.

With the same update, the skipVorto parameter is deprecated.