Dec 7, 2017 -

Updated Jasper API

Updated API allows for Jasper to notify when devices comes offline

Added Map

Nodes with location settings get visible on map (node page)

Added OAuth token authentication to all API's

Tokens can get generated from account page

Exceptions API - Created

The Exception api allows for registing external exceptions

Enabled location updates

Nodes can now register location

Added Agreement & ServiceTypes

Axians only

Add funcionality to export script and properties

Export scriptss and services from one organization to another

API for checking if node is online (ServiceNow)

Allowing ServiceNow to call to check if node is offline

Add description mandatory dialog when creating a new script from scratch


Nov 12, 2017 -

New design

We hope you enjoy our new darker theme. In the future we'll add support for selecting your favorite theme

Device IoT Hub protocol

You are now able to change the device protocol. This only affects Azure IoT hubs as they support AMQP, AMQP-WS, MQTT, MQTT-WS and REST

FIXED: Minor UI fixes

Oct 28, 2017 -

Scheduled updates

Enterprise customers will be able to schedule updates, patching and other actions through the portal

Node state

State of node (network. os, env npm list etc) is now available from Node page

Resetting nodes

mSB-core is now removed upon resetting the node

Jasper consumption data

SIM card consumption and status is now provided through the Node page

FIXED: Services must now have unique names

FIXED: Track exceptions

Oct 28, 2017 - mSB.core

New version of microServiceBus.core (1.0.20)

Persisting limit

Only 1000 msg will be persisted to prevent filling disk space

Sys logs (linux only)

Sys logs can be requested from the node page

FIXED: Messages are no longer routed to disabled services

Mar 29, 2017

Scheduled updates (Beta)

Enterprise customers will be able to schedule updates, patching and other actions through the portal

New version of microServiceBus.node (2.0.19)

Updates to support scheduled updates

Fixed stability issues

Updated tests

New version of microServiceBus.core (1.0.25)

Changed default Azure IoT protocol to MQTT-WS

Fixed signin issues for AWS IoT

ixed issue with debug = true, not reconnecting

Feb 22, 2017

Support for Amazon AWS IoT

Alongside Azure IoT we now support Amazon AWS IoT Hub. All features available for Azure are available for AWS as well.

Check out Choose IoT provider for more information.

Desired state

Desired state is a useful feature which has been available for AWS from the early beginning (Shadows). This has now also been implemented in Azure IoT, and is referred to as Device-Twin.

we’ve added several Services to the Flow toolbox to support Desired State features, both to set state, and to read state.


Users will now be notified of updates and news using Notifications popups.

Restart all nodes

On the Node page, users can choose to update/restart all online nodes.

Paging list of nodes

With many nodes, it’s easier to use paging to quicker select and manage your nodes.

Feb 6, 2017


On the details page for each node, there is now a Tags field. This is a field where you can provide a comma-separated list of tags. These Tags can later be used in the Node setting of Inbound Services of Flows. This way you can configure many nodes through one single Service. To use Tags in Services, simply use #[TAG], Eg. #building3.

ServiceNow integration is now fully integrated with ServiceNow, and can escalate issues and abnormalities to ServiceNow. This is an enterprise feature, and is not available for the trial edition.


By uploading a whitelist (Node page) containing MAC addresses and node settings, nodes can sign in using simply a “-w” flag. Eg. node start -w

If the “-w” flag is used, the node will provide its MAC address when making its initial call to If the MAC address is registered, the node will be provided all other settings and continue.

Remote debugging

This feature enables you to set breakpoints and remotely control the scripts and services running on the node. Check out Debug your nodes for more information

Remote Restart and Reboot

From the Node page your are now given a set of Actions to control your node. The Reboot option will re-start your node, but requires the process to run with enough privileges. The Restart option restarts the Core process and will download any updated packages.