Version 2.22 (2018-02-06)

Important notices

Technical documentation available online

All technical documentation for Managed IoT Cloud, including API specifications, Release notes and Getting Started Guides, are available online:


Support for LoRa networks based on the TTI (The Things Industries) network server

We are introducing support for LoRa networks based on the TTI network server. MIC is driving the provisioning, allowing users of MIC to provision and ensure communicate with LoRa devices in a seamless way, all driven by MIC App Board and APIs. LoRa devices are mapped to MIC Things. To connect a LoRa device only a few simple steps is needed

  • Create a Thing in MIC, then app_key, app_eui and dev_eui are generated automatically. dev_eui can be defined by the user in the External ID field, e.g. when device has pre-defined Device EUI.
  • TTI automatically creates the device representation with app_key, app_eui and dev_eui values from MIC
  • Enter the app_key, dev_eui and app_eui in the device firmware and connect to the LoRa network (TTI network server).

Since version 2.6, MIC supports script field type for Thing Types. This is used for payload encoding and decoding, i.e. translating the LoRaWAN byte buffers <=> JSON documents that can be interpreted automatically by MIC giving a seamless experience visualizing the sensor data in dashboards widgets.

Since version 2.7, MIC have support for LoRa Networks based on the Semtech network server. Over time, we will discontinue the support for the Semtech network server. Exact time will be announced at a later stage.

Retry and confirmed delivery of webhooks

As a Rule action, webhook is a powerful tool for simple integrations and calls to 3rd party systems. In this release we introduce confirmation of webhook delivery, including up to three retries if not confirmed by the 3rd party system. The retries happen after 1, 10 and 60 minutes. Typical use cases are delivery of alarms and important events to 3rd party systems.

API to manage Resources and their attributes

We have added functionality to the Resource API to support management of Resources and their attributes

  • Resource – create and update Attributes
  • Resource Name – create. Mandatory.
  • Resource Label – create and update. Is by default set to Resource Name. Mandatory.
  • Resource Unit – create, update and delete. Is by default empty. Not mandatory.
  • Allow set Resource – create and update. Is by default set to “Yes”. Mandatory. Allow set is always “Yes” for a Virtual Resource.
  • Virtual Resource – create. Is by default set to “No”. Mandatory.

In the next release, App Board will support the above described management of Resources and their attributes. Details in next Release Notes.

Resources attributes are used in App Board

Resource attributes introduced are now used in visualizations throughout App Board. Examples are

  • Resource Labels are used instead of Resource Names. Exception: When creating formulas in “Custom Widget” and in “Rule edit” we will keep Resource Name
  • Resource Units are displayed next to values

Minor improvements and corrections

Numerous minor enhancements and bug fixes are delivered by the new release, including:

  • Added Set Resource capability to the REST API
  • Improved usability in App Board Resources Management section, including sorting on all columns in the Resources list
  • The filtering behavior of the new selection tools in Rule edit has been improved for increased usability
  • The rendering of the selection tools in Rule edit has been improved in Internet Explorer 11 and Firefox
  • The rendering of the new process widget has been improved in Internet Explorer 11
  • Fixed issue when creating a user: Email is no longer required when SMS is used for verification
  • Fixed issue with Elasticsearch indexing of larger Thing shadows
  • Fixed issue with Elasticsearch where a user in some cases couldn’t see observations for Things belonging to a subdomain