Nov 30th, 2018

  • Grant individual logon privilages (mSb.dam)
  • Lock organization to mSB-core version preventing forced updates
  • Support for locking Flows to script/service version
  • Added CTRL+S/Cmd-S short key for saving scripts
  • FIXED: "Fetch from repo" working kind of funky

mSB-node version 1.0.27

  • Support for Device Access Manager (mSb.dam)
  • Support for custom repos of mSB-core and mSB-node
  • Lock organization to mSB-core version preventing forced
  • Updated snap

mSB-core version 1.2.52

  • Support for Device Access Manager (mSb.dam)
  • Lock organization to mSB-core version preventing forced
  • Support for locking Flows to script/service version

mSB-dam version 1.0.0

  • Support for Device Access Manager
  • Updated snap

Nov 4th, 2018

  • Improve error message for Github permission error
  • Added funtionality to move node between organizations
  • (Yocto) Download firmware metadata
  • Add under general properties in itinerary designer the service organisation location.
  • FIXED: Can't right click on the service in the itinerary designer

mSB.core (1.2.40)

  • (Yocto) nodejs RAUC D-Bus integration
  • FIXED: Message context lost on SubmitResponsemessage
  • FIXED: First msb.core-install, with very slow connection, gets stuck (waited 30 min) #551

Oct 21th, 2018

  • Remove single whitelist entry + add confirmation to Clear list #532

  • API to apply Node template to existing nodes #545

  • Send invites to multiple people #553

  • Enable / Disable node with CTRL+R creates multiple services on node #535

  • FIXED: Changes not saved in script window if you don't close window between saves #531

  • FIXED: Node keys are not renewed when changing IoT Hub provider

  • FIXED: Performance improvements for handling signIn & creation of nodes. #529 Opened in axians/

Oct 10th, 2018

  • Remove single whitlist entry
  • Enable/Disable nodes using CTRL+R
  • Upload Yocto firmware image
  • Download Yocto firmware image API
  • Performance improvements
  • Apply node templates to nodes using API
  • FIXED: Cut long Flow names in list

mSB.core (1.2.31)

  • Fixed issue restarting COM upon State gets updated

Sep 7th, 2018

  • Show diff on Audit log
  • (Node API) Updated (start, stop, enable) to use PUT verb
  • (Node API) Creating a node returns the object
  • VSTS integration to trigger on Pull Requests
  • Show Script window from Services in Flow
  • FIXED: duplicate services started when mltiple tags were used
  • FIXED: Node name textbox should be read-only
  • FIXED: createNodeFromMacAddress should not require authorization
  • FIXED: Ctrl+R does not work in all pages

mSB.core (1.2.18)

  • FIXED: Changed state should trigger all "Receive State" services

mSB.node (1.0.26)

  • Add timeout to ensure installation of core does not hang
  • Updated snap version to 1.26

Aug 11th, 2018

  • Enabled Node templates when Nodes are created using Cisco Jasper integration
  • Impoved Search on Node page
  • Added more trace events from Nodes
  • Added "Copy machine name" to serial no
  • Updated Jasper API not to depend on IMEI
  • Added back audit log to history
  • Added more Cisco Jasper information
  • Added "Go to source script" from Flow
  • Enable annotation for scripts (for Git commits)
  • FIXED: Tags should not be case insensative
  • FIXED: bug when creating nodes thorugh Jasper for the first time (no nodes exists)
  • FIXED: Console not working on Edge

Jul 23rd, 2018

  • Added policys for Nodes.
    • Now you can set policy for nodes, you can change disconnect, reconnect and offline mode actions.
  • Added node templates.
    • When creating new nodes you can choose to create them from a template with specific settings. Managing bulk creation of nodes just became easy.
  • Updated API.
    • New features: Enable, Disable and Restart nodes
  • Format JSON in debug console.
  • Give organization ownership to Co-Admin
    • Now possible to give owner access to a Co-Admin in your organization.
  • Improved node properties page.
  • FIXED: Oranization delete page shows right information


  • Implement policys. (disconnect, reconnect, offline mode)

Jun 30th, 2018

  • New Swagger based API

    • For integration with LOB system for managing your Nodes. This API will be extended for many more options in the future.
  • Format JSON messages in console

    • When ourputting JSON in the Debug output, you can optionally have it formated.
  • FIXED: Resizing Flow designer now works


  • Many more events persisted to History
  • Removed redundant packages that were part of mSB.core
  • Disable IoT Hob connection on disabling the node.

Jun 19th, 2018

  • Saving a flow with a node-attribute set to a non-existing node in a service silently gets created

    • This behavior has now changed, and you can optionally save your Flow without creating the nodes
  • Auto-complete tags when writing '#' in nodes fields

    • When selecting a Node in the Flow designer, you can now select from a list of both Nodes and Tags
  • FIXED: Flow's are disabled by default

    • Flows are nolonger disabled after saving
  • FIXED: Login redirect fires to quickly and doesn't let users edit login

    • Users that once looged in using ADFS were not able to change login
  • FIXED: Tags not working for Inbound State Services


  • Get and instance of another service from code within the same Flow Services normaly interact through the Service connectors in the Flow diagram. But sometimes a service can only exist once, such as for accessing a serial port. In such cases you can get an instance of a specific service using:
var srv = this.GetInstanceOf('mbuService');
srv.Process(msg, context); // or any other method
  • FIXED: Tags not working for Inbound State Services

Jun 5th, 2018

  • New beautiful background image Rickard Lundqvist taken this beutiful picture of Nybrokajen in Stockholm.

  • Provide Node shutdown option from portal Nodes can now be shutdown from the portal

  • Enabled remote debug using Chrome Dev Tools Earlier version of remote debugger has been removed and changed to Chrome Dev Tools

  • Audit log Audit log has been made available for Organization, Nodes and Services & Files

  • Show full name of user User name is now shown in the upper right corner rather than the email address

  • Script formating You can now format scripts in the Script Editor

  • Added Privacy information Making sure everyone understands we don't sell or use their data

  • Dell Edge 3001 Temp and humidity service Service for the built-in sensor in Dell Edge 3001

  • Automaicly set the name of script files Setting the name of the Service will automaticly set the name of the file in camel case.

  • Prevent Unauthenticated SignalR calls from nodes All calls from Nodes are authenticated directly on connection rather than only using SignIn method.

  • FIXED: Disable Flow doesn't work

  • FIXED: Change "Reset" to "Wipe" on Node Action menu

  • FIXED: Don't create nodes from typing a name of a node that doesn't exist in a flow

  • FIXED: Unit tests not working All unit tests have been refactored and moved to travis


  • GetInstanceOf method on Services Get an instance of an other service in the same flow using a simple method call.

Apr 22nd, 2018

  • New beautiful background image Håkan Garnefält has been kind enough to share his spring picture of Stockholm by the sea.

  • Audit log for Flows, Nodes, Organization and Scripts
    Users can access the audit log through a number of views in the portal.

  • Full integration with Visual Studio Team Services You can now manage your scripts and services in VSTS and push your changes to

  • Node API External applications such as ServiceNow, can now interact with Nodes using the API

  • Download all scripts You can now download all script files from the Scripts page. This feature can come handy when migrating to VSTS or Github.

  • Mobile console The *Console has been extended to the mobile view

  • FIX: GitHub integration issues ans been resolved

  • FIX: Default organizations is stored in session

  • FIX: Organizations can now change names


  • Set environment parameter at startup node start now accepts --env such as:
node start -c ASDGJ -n myNode -env

Mar 19, 2018

  • History log of all successful and failed transmitted messages along with related events. From the Node page users can now access last weeks event Action drop-down menu. This will provide good insight of everything happening on the node.

  • Highlighting in Console Along with filtering users are now able to highlight events of interest.

  • Enable console for mobile users The console page was earlier hidden for mobile users as it didn't render well for smaller screens.

  • GitHub integration You can now synchronize Scripts in your organization with your gitHub Repo! Just follow this simple guide to Integreate with GitHub.

  • Fixes:

    • Persist selected organization as default.
    • Forgot password page is now aligned with graphical profile.

mSB.core (1.1.40)

  • History log of all successful and failed transmitted messages. Information about every message or event sent from the node is stored in the ./history directory and is saved for a week but limited to 10K. Apart from information about transmitted messages, actions such as connected and disconnected is also stored.

Aggregations of this information can be accessed from the portal.

  • Azure device sdk (azure-iot-device-*) has been updated to 1.4.0. 1.4.0 comes with many updates and improvements for handling re-connect and persistence of messages.

  • Allow 'node restore' with parameter specifying customer's (private) environment uri. When starting up the node for the first time you can now use -env to specify private or self hosted hubs:

node start -c XXXXX -n YYYYYY [-env] [--beta]

mSB.core (1.0.15)

  • Allow 'node restore' with parameter specifying customer's (private) environment uri. When restoring the node you can now use -env to specify private or self hosted hubs:
node restore -env // Requires update of mSB.node

Feb 23, 2018

mSB.core (1.1.3)

  • Always persist messages on Node By setting the retention period on the Node greater than "0", all outgoing event and messages are persisted on the device until the retention period is exceeded or the available storage is less than 25%.

  • Fixes:

    • Fixed: Improved persistence when offline

  • Resend messages from Node

    • On the Node page of the portal you are now able to resend messages persisted on the device.
  • GitHub integration

    • You can now synchronize Scripts in your organization with your gitHub Repo! Just follow this simple guide to Integreate with GitHub.
  • Fixes:

    • Fixed: Reload organizations after accepted invite
    • Fixed: Logging in using GitHub should now work again
    • Fixed: Nodes keep restarting when flows are disabled
    • Fixed: Loading animation for node status never finish
    • Fixed: Nodes keep restarting when flows are disabled
    • Fixed: Prevent none-Administrators from creating organizations for self- and private hosted sites
    • Fixed: Extend session variable timeout from 2h to 24h
    • Fixed: ccp type services won't drag 'n drop

Feb 6, 2018

  • Change org should stay on page

    • When changing organization it's annoying having to navigate back to the same page...
  • FIXED: Move static SignalR list to Redis

    • Major update in relation to Device Management communication to make it more stable.
  • FIXED: Empty itineraries causes flow list to fail

Jan 27, 2018

  • New design on homepage

    • Winter is comming...
  • Toggle enable and disable on flow

    • You can now enalble or disable all services running in the flow from the Flow page.
  • Filter in console

  • Scroll to end in console

  • WIKI pages

    • Help pages are replaced with markdown WIKI pages. All help will be updated.
  • FIXED: Confirmation email page is links to missing image

  • FIXED: Copy script from Script page

mSB.core (1.0.70)

  • Implement retry policy "NoRetry" for Azure IoT.

  • Migrated to 1.3.0 of for Azure device SDK.


  • Build service script for UBLOX_EVK_ODIN_W2

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


  • 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.
  • Notifications
    • 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

  • Tags
    • 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.
  • Whitelist
    • 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.