Device management

There are thousands of devices that support IoT Open and several new ones can be integrated. How these are authenticated differs from device to device. Some devices, such as LoRaWAN, have their own key on each device that must be entered into the platform when connecting in order to connect. Other devices 'pair' with a gateway depending on the protocol and the gateway is authenticated to the platform.

Gateway is provisioned in connection with start-up as it connects to the platform, exchanges security details, establishes secure communication and reports its properties such as MAC address, serial number, current software versions. In the platform, an administrator legally connects the gateway with its local resources to current activities in an organizational tree.


IoT Open uses something called DeviceX to manage devices. Different metadata can be registered on each device. Only a few are mandatory and the user or integrator can add their own metadata to each device e.g. position, mounting height, battery type or software version. Everything can be done via a well-developed and simple API. In addition to the devices already supported in the platform, others can be easily added.


Whether a device can be updated online depends on the node and TH1NG has many years of experience working with exhibited devices and upgrading remotely. In some cases, software components are automatically downloaded or upgraded when a new type of rule / service logic is to be used for edge computing. After a new configuration or updated software has been downloaded, the gateway can, if necessary, act autonomously / offline. More operational software components and security patches can also be automatically downloaded and installed in the gateway when a connection is available.


All devices in the platform can be monitored. This can be done with different resolution depending on how often the device sends data or is available. For example. uptime or battery status can be reported in different views and / or send alarms in different ways. Some battery-powered devices should communicate minimally, while other devices send reports more frequently. This type of settings and considerations are made together with the customer for the current application.