Version 2.11 (2017-03-02)

Features

Node-RED Integration

Node-RED is a powerful and flexible third party “tool for wiring together hardware devices, APIs and online services in new and interesting ways”. For further information, please visit https://nodered.org/.

To facilitate integration between Cloud Connect and Node-RED, Telenor Connexion is releasing Cloud Connect specific “nodes” that makes it easy to connect to, and interact with the Cloud API from within the Node-RED user interface.

Using Node-RED, flows that connect different API endpoints can be designed by drag and drop and then executed, to i.e. combine data from different sources with business logic functions and trigger activities in relevant systems.

Documentation for the Cloud Connect nodes can be found at https://docs.telenorconnexion.com/cc2/node-red/ once version 2.11 is in production and the “nodes” are provided by Telenor Connexion on request.

Geofencing

Geofencing is a powerful addition to the rule engine enabling quick and intuitive setup of location based rules to track your Things movements and get notifications/alarms.

To add a geofence-based rule, select the “latlng” resource in the Set rule section of rule editing. A map is shown in which you draw an area (polygon) by marking its corners, just as for geo-filtering. You are able to scroll in the map (move the covered map area) and also zoom in/zoom out in the map. This makes it easy to zoom in to mark a specific street or point as border for the geofence, yet at the same time enabling you to incorporate large areas in the fence.

4 geofence comparisons are available; Inside area, Outside area, Leaving area and Entering area.

The rule engine triggers events based on the incoming observation (latlng position) of the Thing. For the Leaving and Entering comparators, the incoming observation is compared with the last know state of the thing.

Per domain customizable user management notification emails

Emails sent for the signup, email verification, and administrator approval is now customizable per domain, enabling a tailored text message and web address depending on the user’s domain. This enables e.g. use of welcome message being relevant to the specific domain of the user and possible even different web addresses if the users are to be directed to different sites depending on domain.

Text and links have to be configured by Telenor.

Full support for multiple stacks in one AWS account

Apart from the production stack, customers and partners can now deploy multiple other stacks for use in the same AWS account set up for Cloud Connect. These can e.g. be used for testing, verification and demo without interfering with the live production stack.

Support for MQTT using Cognito credentials

Version 2.10 introduced the MQTT PUB/SUB API, which gave initial support for using Cognito credentials to subscribe and publish to MQTT.

In this version 2.11 we include support for the accepted, rejected, delta and documents sub topics and instead of using separate pub and sub topics, the same topic is used to replicate the structure of the $aws/things/<thingname>/shadow/update topics. A logged in Cognito user can subscribe and publish to thing-update/<domainpath>/<thingname> and subscribe to thing-update-accepted/<domainpath>/<thingname>, thing-update-rejected/<domainpath>/<thingname>, thing-update-delta/<domainpath>/<thingname> and thing-update-documents/<domainpath>/<thingname>. The payload is the same as for $aws/things/<thingname>/shadow/update.

App Board uses the MQTT PUB/SUB API

App Board is now migrated and uses the new MQTT PUB/SUB API.

Minor improvements and corrections

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

  • Improved validation message handling
  • Fixed issue with negative minimum values in gauge widget
  • Fixed issue with Thing files browser pagination
  • Fixed issue with LoRa
    • Thing creation intermittent
    • File widget not working as expected o Downlink not working as expected