Upgrade 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,
...
}
Starting with 3.7, devices use strings as IDs.
{
"id": "device-4",
...
}
Data migration
Existing devices IDs are converted to IDs of the pattern
device-<int>
, e.g. the numeric ID4
of a device is transformed to the stringdevice-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.