For most releases, migration can happen without requiring major changes. However, sometimes, manual changes cannot be fully avoided for system operators or users of the REST API. In these cases, the following guide lists all required manual steps for upgrading a tenant or its users from an earlier to a later release.

Release compatibility

Dependencies compatibility

The following table illustrates compatibility of the last few thingsHub releases with its base depenencies, i.e. Kubernetes, PostgreSQL and InfluxDB.

4.0

4.1

4.2

4.3

Kubernetes

≥1.12 & ≤1.17

≥1.15 & ≤1.18

≥1.12 & ≤1.18

≥1.12 & ≤1.18

PostgreSQL

≥9.6 & ≤11.11 (≠10.10)

≥9.6 & ≤11.11 (≠10.10)

≥9.6 & ≤11.11 (≠10.10)

≥9.6 & ≤11.11 (≠10.10)

InfluxDB

≥1.7 && ≤1.8

≥1.7 && ≤1.8

≥1.7 && ≤1.8

≥1.7 && ≤1.8

Note that version 10.10 of PostgreSQL contains a regression that is not compatible with Grafana, so this version is explicitly not compatible with the thingsHub.

Network server compatibility

The following table shows which thingsHub release is tested with which release of the network servers.

4.0

4.1

4.2

4.3

Kerlink SPN

=2.3

=2.3

=2.3

=2.3

Kerlink WMC3

≥3.0 & ≤3.2

≥3.0 & ≤3.2

≥3.0 & ≤3.2

≥3.0 & ≤3.2

Loriot

≥4.0 & ≤6.0

≥4.0 & ≤6.0

≥4.0 & ≤6.0

≥4.0 & ≤6.0

MZ Connect

*

*

*

*

Sigfox

*

*

*

*

Swisscom LPN

*

*

*

*

The Things Industries

*

*

*

*

The Things Network

2

2

2

2

For the network servers marked with *, there is insufficient information provided by the network operator to state release compatibility.

3rd-party system compatibility

This table shows which release of the thingsHub is compatible with which 3rd party system, e.g.

4.0

4.1

4.2

4.3

Cumulocity

≥10.4 & ≤ 10.6

≥10.4 & ≤10.6

≥10.4 & ≤10.6

≥10.4 & ≤10.6

David

≥1.7 & ≤1.8

≥1.7 & ≤1.8

≥1.7 & ≤1.8

≥1.7 & ≤1.8

MQTT

=5.0 & =3.1 & =3.1.1

=5.0 & =3.1 & =3.1.1

=5.0 & =3.1 & =3.1.1

=5.0 & =3.1 & =3.1.1

MySQL

=8.0

=8.0

=8.0

=8.0

Migrating to newer releases

Migrating from release 3.x to 4.x

Establish suitable permissions for all users

Required actions

Release 4.0 introduced a role-based permission system. This means users can now have different sets of permissions depending on their role in the project or company. With these new roles it is necessary to make a decision which role each user should have. By default, for a maximum of security, no user will have a role assigned at all (except for the admin user, which has all permissions). As a consequence, the admin user will have to assign the most fitting role to each user after the system was upgraded. The new role “Tenant Owner” is closest to what users had before.

Migrating from release 3.8 to 3.9

Simplified labels for devices by removing the key and keeping only value

Usage Example

Before this change, device labels were key value pairs. Every key could be assigned once per device:

{
  {
    "id": "manufacturer:nke",
    "key": "manufacturer",
    "value": "nke"
  },
  {
    "id": "measurement:temperature",
    "key": "measurement",
    "value": "temperature"
  },
  {
    "id": "location:office",
    "key": "location",
    "value": "office"
  }
}
CODE

With version 3.8 and later, labels are simple strings, more akin to tags:

{
  "nke",
  "temperature",
  "office"
}
CODE

Migration of existing data

Existing labels are migrated to the new schema by concatenating key and value with an underscore:

Required actions

  • Consumers of the REST-API need to adapt their data model as described above.

  • Queries to the REST API which use query parameters to filter by device labels need to be adapted to use the new style of labels.

Added endpoints for easily creating/updating/deleting labels on a device

Usage example

Up to version 3.7, labels were managed using the API endpoint for the device which they label:

PUT /api/v3/devices/:device-id
{
  "labels": [
    {
      "key": "X",
      "value": "Y"
    },
    {
      "key": "A",
      "value": "B"
  ]
}
CODE

Starting with version 3.8, labels are managed with dedicated endpoints using the CRUD pattern. E.g. labels are created with the verb POST to the resource /api/v3/device/:id/labels:

POST /api/v3/devices/:device-id/labels?labels=foo,bar
CODE

Retrieving labels

GET /api/v3/devices/:device-id/labels
CODE

Deleting a label:

DELETE /api/v3/devices/:device-id/labels/:label-id
CODE

Data migration

Not applicable.

Required actions

  • Consumers of the REST API need to be migrated to the new interface.

Added selectors for integrations that will match devices labels

Previously, device selection happened by an integration's label.

{
  "labels": [
    {
      "key": "foo",
      "value": "bar"
    },
    {
      "key": "myxl",
      "value": "plyx"
    }
  ],
  ...
}  
CODE

From 3.6 on device selection happens by dedicated selectors.

As of now, only logical disjunction (with $or is supported).

{
  "selectors": {
    "$or": [
      "foo_bar",
      "myxl_plyx",
    ]
  },
  ...
}
CODE

Data migration

Not applicable.

Required actions

  • Consumers of the REST API need to be migrated to the new interface.

Disabled public endpoints for device information and device activation

To the best of our knowledge, this API has not been in use.

Required actions

  • Adapt consumers of the REST API to manually create devices.

Migrating from release 3.7 to 3.8

Device ID are now unique strings instead of integers

Valid IDs have a maximum length of 63 characters and may contain alphanumeric characters and dashes.

Before 3.6, devices used numerical IDs.

{
  "id": 4,
  ...
}
CODE

Starting with 3.7, devices use strings as IDs.

{
  "id": "device-4",
  ...
}
CODE

Data migration

  • Existing devices IDs are converted to IDs of the pattern device-<int>, e.g. the numeric ID 4 of a device is transformed to the string device-4.

  • Device created through auto-activation will get an ID of the pattern <network-server-id>-<network-device-id>-<unique-int>, where the network server ID is the thingsHub's ID of the network server and the network device ID is the network server's device ID. A unique integer is appended to ensure collision cannot happen.

Required actions

  • Consumers of the REST API need to be migrated to the new interface.

  • User-created Queries to the time series database, e.g in the visualizer, which reference devices by ID need to be modified to use the new device ID schema.

Disabled public endpoints for device information and device activation

To the best of our knowledge, this API has not been in use.

Required actions

  • Adapt consumers of the REST API to manually create devices.