What's New

Device Management is now live in IoT

Share this post:

I’d like to tell you about a major new enhancement we’ve just made to the Internet of Things Foundation service. We call it Device Management, and it’s all about making it easy and efficient to manage lots of IoT devices.

What is Device Management anyway?

When I talk to customers about their IoT plans, they generally mention the phrase “device management”. It doesn’t matter whether they’re talking about connected cars, connected light bulbs or connected refrigerators, there’s usually device management in there somewhere. So, what does it mean and why does everyone want it? Well, it includes things like:

  • Bulk operations on many devices at a time
  • Rich device metadata and status information
  • Diagnostic information, both for connectivity and for the devices themselves
  • Device management actions, most notably firmware update

And all of these things need to be made easily accessible via APIs and dashboards.

Managed devices

In order to benefit from device management, your devices need to be a bit smarter. Specifically they need to be managed devices. A managed device has a piece of code called a device management agent which exchanges special device management messages with IoT Foundation over MQTT. There’s nothing very complicated about a device management agent. The device management messages are quite simple, and you need only use as much or as little of the capabilities as your device requires.

We will provide sample implementations of device management agents, and you can use these as the basis of the agent for your own devices. That typically will mean adding a few lines of code to the sample. The step from an unmanaged device using MQTT to a managed device with a basic device management agent is very small indeed. We will also provide recipes for device management.

At a minimum, a device management agent needs to send a message to IoTF telling it that it wants to be a managed device. This message also includes a summary of the device’s capabilities, such as whether it can have its firmware updated.

You can pick and choose the features of device management that you want to use. For example, if you want your device to be able to send diagnostic information to IoTF, you add that capability to your device management agent. If your device is mobile and you want it to update its location information in IoTF, you can add that feature to your device management agent.

Device metadata

Imagine that you’re producing a new range of connected blenders. Each blender has a manufacturer, model and serial number. So that the blenders can connect to IoT Foundation, you add them as new devices to your IoTF organisation. When you do this, it would be nice to be able to associate the serial number and so on with the devices. Then, you can tie back information from a device in IoTF to the actual blender you produced.

These are examples of device metadata. As the number of devices increases, having the ability to associate metadata with the devices helps you manage the devices efficiently. For example, if a customer calls the service line with a blender problem, you can ask for the serial number and then use this to find the device in IoTF which corresponds to that blender. You can dive down into the diagnostic information for the device and perhaps work out how to resolve the problem.

Another example of device metadata is called descriptive location. There’s longitude and latitude too, but in many cases a less rigorous idea of location such as “Building 43, floor 2” is much more useful. That’s a much more descriptive way of expressing location.

Diagnostic information

If you’re managing a large number of devices, some of them are bound to have problems. These might include connectivity problems, or perhaps an unexpected situation discovered by the device firmware.

We’ve added connectivity logs to our API and dashboard. These let you see significant connectivity events for devices, such as why a device disconnected. If you are having connectivity problems, these logs will help you figure out what’s wrong.

Devices can also report diagnostic information to IoT Foundation. The simplest are error codes. These are just numbers which represent error conditions, suitable for the simplest devices. If a device notices an error, its device management agent can send the error code to IoT Foundation.

More sophisticated devices can report error logs instead. Each error log entry includes a timestamp, a description of the problem and perhaps a block of diagnostics data captured by the device.

When a device reports an error code or a high-severity error log, IoT Foundation automatically highlights the device as being in an alert state in the IoT Foundation dashboard. This makes it simple for the operator to notice the problem and act on it.

Again, it’s all about efficiently managing devices.

Device management actions

Device management actions are a way of remotely managing devices from IoT Foundation. There are four actions supported initially:

  • Reboot
  • Factory reset
  • Firmware download
  • Firmware update.

You can initiate device management actions from the API or the dashboard. You can perform an action on up to 5000 devices at a time in a single request. Of course, a request such as rebooting 5000 devices doesn’t complete immediately, so you can see the requests in progress and whether the devices successfully performed the action.

Managed devices don’t have to support any actions, but if they do, the device management agent is responsible for receiving the initiation command and performing the action. For example, to reboot a device, it’s likely that there’s a system call in the device firmware which actually reboots the device. The device management agent would simply invoke this system call when it receives the command from IoTF. Once the device has rebooted, it reconnects to IoT Foundation and sends a message indicating that it’s back. This completes the device’s part in the overall management request.

Building your own tools with our API

As part of this, we’ve massively enhanced our API. Having an easy-to-use API is important because it makes automation simple. We had three principles in mind:

  • The API must work well even if you have millions of devices. So, there is filtering of results (“give me a list of the washing machines of type ‘WM123’ at firmware level 17”) and paging so you can get a huge set of results in manageable chunks.
  • Everything we do in our dashboard UI can be done with the API. Soon, in the dashboard, we will add “API” buttons which you will be able to press to reveal the API calls we use to request the data shown in the dashboard. If you’re trying to create your own tools based on the IoTF API, this will be a big help.
  • Whenever possible, the API follows REST principles. Basically, this means that the behaviour of the API is predictable to developers familiar with REST. For example, resources are grouped into collections. If you use HTTP GET on a collection, you get a list of the resources in the collection. If you use HTTP GET on a single resource such as a device, you get the details about that device. In neither case are any resources modified, so you can safely use these operations.

Also, we have documented the API using a notation called Swagger. There are a lot of tools for Swagger, so whether you want an easy-to-browse view of the API or a generated client library so you don’t have to use HTTP directly yourself, having a Swagger definition is great.

Designing the service

In the IoT Foundation team, we put a lot of effort into designing the service so it meets the needs of specific target users. We have people dedicated to designing the user experience and the visuals of the dashboard. You can clearly see the importance we place on the experience when you first start using the service. Sophie Riches, who is a User Experience Designer in our team, will tell you much more about this soon.

What next?

A good place to start is the documentation about device management in IoTF which can be found here.

If you’re already using Internet of Things Foundation, you’ll notice the changes in your dashboard. You can convert existing unmanaged devices into managed devices by adding a device management agent. We will be providing sample implementations of device management agents, which you can refer to or use as the basis of your own agent.

We will be adding new recipes for device management over the coming weeks, so if you’ve already got experience with using IoT Foundation, you’ll easily be able to start using device management also.

More stories
April 30, 2019

Introducing IBM Analytics Engine v1.2 and Announcing the Deprecation of IBM Analytics Engine v1.0

We are excited to inform you about the new version of IBM Analytics Engine v1.2 that will be available starting May 15, 2019. Along with this release, Analytics Engine v1.0 will be retired.

Continue reading

April 23, 2019

Announcing the Deprecation of the Watson Machine Learning JSON Token Authentication Service

We’d like to inform you about the deprecation of the Watson Machine Learning JSON Token Authentication service. This method of authentication will be retired on May 30, 2019.

Continue reading

April 19, 2019

Introducing IBM Cloud Object Storage Firewall: Further Secure Your Data

IBM Cloud Object Storage (COS) is giving you more control over who can access your data. We have introduced a new capability allowing you to configure your buckets with trusted IP address(es) that will dictate access to the data in COS.

Continue reading