Version 2.17 (2017-10-05)
Changes to the Observation API due to upgrade of Elasticsearch
A future release (2.18, tentatively planned 26/10) will deliver an upgrade of Elasticsearch from version 2.3 to 5.5. This will impact the Observation API, Thing API and Event API since these APIs allow developers to query Elasticsearch directly, and there are differences in the Elasticsearch query syntax between the two versions. Depending on how the above APIs are used for a specific application, updated queries might be required.
To facilitate migration activities, the two versions of Elastisearch will be available in production in parallel during an interim period. During this period, the active version can be selected for each stack individually.
If you are using the Elasticsearch query capability in the any of the APIs, you are kindly requested to contact Telenorconnexion for joint establishment of a migration plan.
Technical documentation available online
All technical documentation for Managed IoT Cloud, including API specifications, are available at https://docs.telenorconnexion.com/mic/
New gauge aggregation widget in Thing Type dashboard
A new widget type is available in the Thing Type dashboard. The new widget is called Gauge Aggregation, and is used to visualize the sum/count/average of a specific resource for the collection of things of a specific type that match the current filter.
As a basis for the calculation, the latest reported data for each thing that matches the current filter is used. The aggregation widget is only available for resources that have the data type number.
Send SMS rule action
A new rule action that allow rules to send SMS’s has been added. The SMS rule action is configured by adding the SMS action to a rule, enter the telephone number(s) of the recipient(s) and define the text that should be sent as an SMS. The same syntax that is used for events and emails can be used for the SMS text, to include system data such as the thing and resource value for which the rule was triggered. The text can be maximum 160 characters. If the text is longer, it will be truncated at 148 characters and an ending text “…truncated” will be added to the SMS.
Please note that the SMS action is visible only if the Telenor Connexion SMSC service has been configured for your account. Please contact your Telenor Connexion representative if you would like SMS to be enabled for your MIC account.
Track historical position of thing in the Thing dashboards map widget
A new configuration parameter “Show historical trace” has been added to the map widget available in the thing dashboard.
If “no” is selected for this parameter, the latest reported position of the thing will be visualized in the map – corresponding to the functionality for this widget before this release.
If “yes” is selected, the widget will display the historical positions reported by the thing, interconnected by a line, on the map. With this setting, the data for the widget will not be updated in real time.
Please note that the number of data points simultaneously displayed in a map is limited to 100. If the current filter returns more observations, a label indicating that only the 100 latest values are displayed will be shown in the map.
Review of the status field in Thing filter
The status field in the Thing filter contains a number of predefined status flags. In this release, new status flags has been added and some of the old statuses has been renamed for clarity.
The new set of status flags and their definitions are covered in the following list.
- Offline - The thing have reported state and tcxn.connection_status = 0
- Offline (connectivity available) - The thing have reported state and tcxn.connection_status = 1. This status is used when the modem is connected but the thing/sensor itself is not connected. Previously this status was called “Cloud Online”.
- Online - The thing have reported state and tcxn.connection_status = 2
- Not yet connected - This means that the thing have never sent any data to MIC, its state is undefined.
- Unknown connection status - This means that the thing have reported state but the resource tcxn.connection_status has not been reported.
- All – includes all statuses above.
Thing markers in geographical filter map
The map that is used to define a geographical filter in the thing filter and in rules will now display thing markers to indicate the current position for relevant things. This gives the user context that is often helpful when defining a geographical filter.
Improved navigation in App Board
The App Board’s usage of the browser history has been reworked, and navigation using the browser’s back-button is now more user friendly.
Added API to create virtual resources
Virtual resources have existed since version 2.1, but they have only been possible to add through App Board.
Now we have added API support for creating virtual resources as part of the Resource API.
Added Events API to manage Events
In this release we add the Event API that is used to find and manage Events, both Rule Engine Events and Lifecycle Events.
We have also added type of Event. Type is Rule for Rule Engine Events and for Lifecycle Events the name of the Lifecycle Event is used (e.g. THING.CREATE).
Combining the Event API with Rule Engine and virtual resources brings a lot of powers to customers and partners. E.g .it can be used to create support for a trip in a fleet management solution. The start and stop of a trip are 2 events set by a rule and including data and timestamps to be able to fetch all reported positions (lat,lng) between start and stop and then visualizing the trip on a map, calculating the distance, average speed, duration, etc.
API support for specifying pre-defined Device IDs at thing creation
The Thing Management API has been extended to include the attribute “externalId”, which is optional and intended to be used for a unique ID of the device.
An example use case is to specify the pre-defined Device EUI for a LoRa device at Thing creating.
Added possibility to automatically create a user-specific domain at signup
This feature makes it possible to automatically create a sandbox domain for the user at signup and place the user in that domain.
Every user domain will be created as a subdomain to a main domain specified.
Added provisioning and protocol support for non-MQTT devices
We have created an adapter architecture to support non-MQTT devices. The architecture support plug-in adapters for almost any device protocol.
In this release we have added support for TCP-based protocols in general and implemented a specific TCP-based device protocol.
This is an additional feature, available on request.
Minor improvements and corrections
Numerous minor enhancements and bug fixes are delivered by the new release, including:
- Reduced size of App Board web page, giving faster loading of the application
- Review of permission model for Thing Update API
- Improved documentation of user sign up and authentication