Mars 24th, 2024

microservicebus.com

  • Suspicious user activity
    • In an effort to raise the security bar, a series of controlls has been implemented to detect suspicious user activity. Global administrators will get notified in cases where users are locked out

microservicebus-py version 1.0.8

  • Minor fix for downloading files
  • Added colors to logging
January 30th, 2024

microservicebus.com

  • Global Administrator
    • Private instances can now provide Global Administrators which will automatically be added as Co-administrator
  • Next available IP for VPN peers
    • When adding Node- or user peers, you’ll get a proposed with the next IP address
  • Minor UI fixes

microservicebus-py version 1.0.6

  • Improved sign-in process
    • Sign-in process now respects disabled Flows and Services along with Bind-to-version for improved version controll
  • Much improved re-connect handling
    • The Python Node has previously relyed on restaring after missing heartbeats after unexpected disconnect. This experiance has now improved with better event handling
  • Preparation for auto update
    • The util class now have a check_version function which can be called from a custom service.
  • Improved logging
January 15th, 2024

microservicebus.com

Although there has been several small fixes in this release, this update is to align microServiceBus.com with underlying platforms and dependancies.

IMPORTANT! Due to changes in .Net 8, API keys needs to be regenerated. Our support team will contact you and assist you if needed.

  • Underlying platform update
    • microServiceBus.com has undergone a major update from .Net 6 to .Net 8, which in turn has provided a much improved performance
  • GUI update
    • Aligned with the platform update, we have also updated from bootstrap 3 to bootstrap 5, for better alignment with our other products
November 29th, 2023

microservicebus.com

  • New Invoicing API
  • Improved VPN Validation
    • More intuitive experiance when managing VPN settings
  • Improved monitoring of cloud services

microservicebus-py version 1.0.5

  • Improved handing of MAC addresses
  • Added support for PIP start
  • Added support for Meter configuration
October 10th, 2023

microservicebus.com

microServiceBus.com will be undergoing a migration to .net 8 in November, whilst this update primarly focus on simplyfying the deployment in November/December. This includes refactoring of configuration settings, security updates and bringing all dependancies to latest version.

  • New DEV tools
    • We’ve had some dev tools we’ve been using internally to simplyfying our day-to-day work which we have now made available to all users; JSON editor, CRON Editor and REST test console

microservicebus-py version 1.0.1

  • Improved error handling
  • Tracking is now available for our Python agent
  • Watchdog service has been added

microservicebus-core version 4.6.0

  • Improved VPN information
  • Minor bug fixes
  • Improved terminal (sizing, coloring etc)

microservicebus-node version 4.1.0

  • Fixed bug for removing npm packages

meta-microservicebus-intel(YOCTO firmware for Intel)

  • Updated to Kirkstone 4.0.13
  • Updated node.js => 16.20.2
  • Updated npn => 8.19.4
  • microservicebus-node => 4.1.0

meta-microservicebus-imx8(YOCTO firmware for Compulab iMX8)

  • Updated to Kirkstone 4.0.13
  • Updated node.js => 16.20.2
  • Updated npn => 8.19.4
  • microservicebus-node => 4.1.0
August 2nd, 2023

microservicebus.com

  • Improved partner offering
    • Partners can now offer custom operational support
  • Added support for “ignore” npm/pip version
  • Added Python snippets for code enditor
  • Organization API
    • Organizations can now be added using the API
    • User invites can now be sent using OrganizationsAPI
  • VPN API
    • You can now manage VPN node- and user peers using API
  • Regenerate VPN token
    • VPN tokens can now be re-generated through the API
  • VPN general improvements
    • Many improvments have been done to make VPN connections more stable
  • Password is no longer needed for generating API key
  • Fixed Meter Config
    • Fixed minor issues with Meter Config
  • Fixed enable/disable VPN API
  • Fixed VPN Net mask

microservicebus-py version 0.9.9

  • Added Tracking
    • *Python services can now track messagesa using await self.Track(message)
  • Transfer files to Nodes
    • Users can now transfer files to Python nodes from the Device option
  • Restart if node has not successfully signed in before first heartbeat
  • Improved logging and exception handling
  • Fetch base uri from env MSB_HOST
    • Base uri (E.g. https://yourorg.microservicebus.com) can now be set in environment variables (MSB_HOST)
  • Improved package versioning
April 28th, 2023

microservicebus.com

  • Fixed VPN issues
    • There has been issues where VPN user peers has been registerd as Node peers causing Nodes to appear twice in on the Node list page

microservicebus-py version 0.9.1

  • Added IP addresses to signin request
Mar 16th, 2023

microservicebus.com

  • New service to receive connection change events
    • See mSB-core updates

microservicebus-core version 4.4.4

  • The Node agent will now raise events on changes of the connection state, both for connection to mSB portal and IoT Hub
    • These events can be captured using either a Connected state inbound service (using flows) or a Background service. This allows for custom scripts or services to try to resolve the connection issue.
Mar 16th, 2023

microservicebus.com

  • NEW CODE EDITOR!
    • The old Ace code editor has served us well, but has now been replaced with the new Monaco editor (same as VS Code)
  • Firmware list
    • The list of firmwares on the /Nodes page now includes images published at the Root organization
  • Added external IP to Log in info
  • FIXED: Adding VPN User peer does not present WireGuard configuration.

microservicebus-core version 4.4.1

  • Node receives GPS location info on Sign-in
    • The location info is available using settings.location
  • Removed dependancies to request npm package
  • Updated signalr, network and dbus dependancies
  • FIXED: Console data not transmitted to portal

microservicebus-py version 0.9

  • Added reconnect event and changed automatic_reconnect option
    • The reconnect event makes the Node more stable
  • Improved handling of updated SAS tokens
    • Removed restart on update node
  • Improved versioning
  • Implemented support for state changes
  • Fixed enable / disable service
Feb 21st, 2023

microservicebus.com

  • Update/renew tokens
    • A new API has been provided to updated individual Node tokens. The API is available under /Organizations
  • FIXED: Remote terminal issue with VI/VIM
    • There has been an issue where opening files with more than 30 rows has ended up “outside” the console frame. This issue has now been fixed

microservicebus-py version 0.1.6

  • Support for remote terminal
    • Our Python based agent is now accessable from the remote terminal in the mSB.com portal
  • VPN Support
    • Same capabilities as with the Node.js agent allowing to host or participate in VPN networks
Aug 30th, 2022

microservicebus.com

  • UNMANAGED SLA
    • Along with 24/7 and Office hours, we now support Un-managed SLA. This might come useful for Organizations reporting only custom errors. Please be aware that Off-line nodes and other managed alerts are not supported
  • Meter Configuration
  • New IoT Provider supported: Proptech OS
    • ProptechOS is an innovation platform which collects and harmonizes real-time data from building management systems, BIM, business and IoT devices
  • API update:
    • Manage GPS locations through API
  • FIXED: Validation errors are not shown when saving node with IMIE issues
Aug 30th, 2022

microservicebus.com

  • Improved support for AAD federation
    • There were issues with certain claim configurations.
  • Search whitelist
    • The whitelist is now searchable for Name or MAC address
  • FIXED: Whitelist pagination not working
  • FIXED: Update firmware using UI not working

microservicebus-node version 4.0.0

  • Improved Node.js support
    • microservicebus-node now supports Node.js v18

microservicebus-core version 4.0.0

IMPORTANT!

Changes in microservicebus-core mentioned below has been available for testing since May 2022. All Nodes using “latest” will automaticly be updated once restarted. If you have not yet tested the BETA version and don’t want this update at this moment, navigate to the Organization page, click EDIT on the NPM feature and set the “Default version” to 3.16.1.

THIS CHANGE WILL BE APPLIED 31 st of Aug (tomorrow)

  • Improved Node.js support
    • microservicebus-core now supports Node.js v18
  • Removed dependancies to npm
    • To support lastet version of Node.js
  • Set IP for VPN host
    • Useful for Nodes hosted behind private ip’s
  • Update firmware on Offline
    • See above
Aug 10th, 2022

microservicebus.com

  • API for calling device methods
    • Our API has been extended to include calling Device methods (Azure only)
  • Update firmware on Offline nodes
    • Until now, offline Nodes has been ignored for remote firmware updates. Our API has now been extended for both Nodes and Tags. Using the tag option will let you update many Nodes with a single call

microservicebus-core version 3.9.94 (BETA)

  • Update firmware on Offline nodes
    • See above
Aug 8th, 2022

microservicebus.com

  • Remove API throttle restrictions on managed instances
    • Managed instances are no longer subject to API IP rate limits
  • Fixed: Error on /updatefirmware API call
    • The exception were caused by one or more nodes were not online. The problem is now fixed and returns a object with information about which nodes has and has not been updated.
June 11nd, 2022

Time for re-factoring

As summer and vacations are coming to Sweden we’re planning on doing some re-factoring and aligning our products with the latest platforms and frameworks. microServiceBus.com (portal) will be migrated to .net6, microservicebus-node to Node.js 16+ and our Yocto images to Kirkstone.

We expect all of this to be ready by Jul-Aug and we will freaze the backlog until then.

microservicebus.com

  • Migration to .net 6
    • microServiceBus.com has been undergoing a series of steps in prefaration for migrating to .net 6.
  • Fixed: Unable to remove nodes that has VPN configured. #1744
  • Fixed: Audit log Diff is not showing the latest settings. #1745
  • Fixed: Bug when sending Email notifications

microservicebus-node version 4.0.0 (BETA)

  • Removing references to NPM package
    • As of Node.js version > 15, the NPM package is no longer supported
  • Support for Node.js version 16+

microservicebus-core version 3.9.9 (BETA)

  • Removing references to NPM package
    • As of Node.js version > 15, the NPM package is no longer supported
  • Support for Node.js version 16+

meta-microservicebus (YOCTO)

  • Updated to support microservicebus-node@4.0.0

meta-microservicebus-intel (YOCTO)

  • Migrated to Yocto release Krikstone
  • Updated Node.js vresion to 16.14.2
  • Many security updates
May 10th, 2022

microservicebus.com

  • SmartEdge integration
    • SmartEdge is a generic visualization platform which if integrated with microServiceBus.com will receive data from your IoT Hub. You can then continue to create and building reports and dashboards to visualize your data.
  • Improved invoicing

microservicebus-py version 0.0.20

  • Firmware updates
    • Improved RAUC support
April 19nd, 2022

microservicebus.com

  • Added SLA and CostCenter to Node Templates
    • Node Templates now includes Cost Centre and SLA
  • Improved performace
    • Overall improved performace for loading pages
  • Added Get IoT Hub Connection string to Organization API
    • The Organization API now provides a way to retrieve the IoT Hub connection string (Azure IoT hub only)
  • Improved invoice documentation
  • Resolved issue with VPN forwarding
  • Resolved issue with deleting VPN peers

microservicebus-core version 3.15.2 (BETA)

  • Updated dependancies
    • “async” => “3.2.3”
    • “moment” => “2.29.2”

microservicebus-py version beta

  • Set settings on initial signin
  • Replaced all print calls with self.printf to resolve issue when running as service
  • Updated meta-microservicebus-py Yocto layer
Mar 22nd, 2022

microservicebus.com

  • Allow tags as destination for Python Nodes
    • As with JavaScript services, users can now configure their Python services to use tags as destination
  • Background Services
    • Background services can now be set on the Node property page under Policies
  • Updated Node templates
    • Background services can now be set on the Node template

microservicebus-core version 3.15.0

  • VPN support
    • Through the integration with WireGuard®, Nodes can now establish VPN networks.
  • Docker compose support
    • Added support for Docker Compose build, up and down command.
  • Background tasks
    • Services can now be configured to run the background independantly of Flows and other Services.
  • FIXED: Nodes now report storage

microservicebus-py version beta

  • Update Firmware support
    • Through integration with DBus and RAUC, the Python Node can now manage firmware.
  • VPN support
    • Through the integration with WireGuard®, Nodes can now establish VPN networks.
  • MQTT support
    • Added support for transmitting messages to the IoT Hub through mSB-py.
  • Azure IoT Hub support
    • Similar to the JavaScript based node, the Python Node can now transmit messages to the Azure ioT Hub.
  • Hosting custom services
    • Similar to the JavaScript based node, the Python Node can now download and run services defined in mSB.com.
Feb 8th, 2022

microservicebus.com

  • Azure Devops integration - File pattern
    • Users can now optionally set file pattern to match files imported through Azure Devops
  • Background tasks
    • Services can now be configured to run the background independantly of Flows and other Services. This feature can be very useful for health monitoring for instance.
  • Improved VPN support
    • Node can now be configured to forward all traffic

microservicebus-core version 3.14.4 (BETA)

  • Background tasks
    • Services can now be configured to run the background independantly of Flows and other Services.
  • FIXED: Nodes now report storage
Jan 4th, 2022

microservicebus.com

  • Docker compose support
    • We have now extended the Docker support with Docker Compose. You can now create docker compose yaml files along with attached docker files, and later build, install and run it at the Node.
  • Improved firmware management
    • We’ve added some UI improvments such as image and platform intellisense.

microservicebus-core version 3.13.19 (BETA)

  • Docker compose support
    • Added support for Docker Compose build, up and down command.
Dec 25th, 2021

microservicebus.com

  • VPN support
    • You can now set up VPN networks through mSB.com by delegating VPN interfaces and peers through your Nodes. This feature also includes key rotations and forwarding. For more information

microservicebus-core version 3.13.17 (BETA)

  • VPN support
    • Through the integration with WireGuard®, Nodes can now establish VPN networks.

microservicebus-node version 3.4.5

  • Updated dependancies
    • tar => 6.1.11
Nov 8th, 2021

microservicebus.com

  • Support for on-premise installation of microServiceBus.com
    • Our on-premise offering complements our cloud hosting options to support high security scenarios where the entire solution is installed in secure zones with no internet access.
  • Docker support
    • Aligned with our on-premise offering, microServiceBus.com, with all its dependencies can now be hosted as Docker containers.
  • Support for Eclipse Mosquitto™ as IoT provider
    • Eclipse Mosquitto™ has been added as an alternative to other IoT providers and will serve as the on-premise solution for a local IoT Hub. As with our support for other IoT Hub providers, -Mosquitto MQTT is fully managed from the portal.
  • Manage proxy settings on Nodes
    • With the 3.13.10 release of microservicebus-core (see below) Nodes can act as proxies. Proxy settings such as ports, keys and destination address can be managed from the Node page.
  • Package manager
    • microServiceBus.com package manager allows you to import packages from NPM and PIP (or manual upload) and make these available for Nodes. This option is to support Nodes installed in secure zones without access to other package managers.
  • FIXED: ADFS/AAD Users can’t get access to profile settings

microservicebus-core version 3.13.10 (BETA)

  • Node proxy
    • Nodes can now act as proxies for other Nodes. This feature can come useful in scenarios where Nodes are installed in secure zones without access to internet.
  • Support for Eclipse Mosquitto™ as IoT provider
  • Improved error notification
    • Added error notification when trying to transfer a file from a Node which doesn’t exist.
  • Dependancy update: AZURE Device SDK update
    • azure-iot-common@1.12.13
    • azure-iot-device@1.17.8
    • azure-iot-device-mqtt@1.15.8
    • azure-iot-device-amqp@1.13.8
  • Dependancy update: chai
    • chai@4.3.4
  • Dependancy update: mocha
    • mocha@9.1.3
  • Dependancy update: network
    • network@0.6.0
  • Dependancy update: retry-request
    • retry-request@4.2.2
  • Dependancy update: uuid
    • retry-request@8.3.2
Sep 1st, 2021

microservicebus-core version 3.13.0

  • Transmit log files on startup
    • A new Log Policy has been added to the Nodes causing the Node to transmit log files with first start after boot. Log files get automatically accessible from the Node properties page
  • Improved error notification
    • Added error notification when trying to transfer a file from a Node which doesn’t exist.
  • Dependancy update: AZURE Device SDK update
    • azure-iot-common@1.12.10,azure-iot-device@1.17.5,azure-iot-device-amqp@1.13.5
  • Dependancy update: underscore
    • underscore@1.13.1
Sep 1st, 2021

microservicebus.com

  • Transmit log files on startup
    • A new Log Policy has been added to the Nodes causing the Node to transmit log files with first start after boot. Log files get automatically accessible from the Node properties page

microservicebus-core version 3.12.8 (BETA)

  • Transmit log files on startup (see microServiceBus.com above).
Aug 25th, 2021

microservicebus.com

  • FIXED: Empty description field when creating a new node
  • FIXED: Issue with invites not being sent
  • FIXED: Issue with retreiving syslogs

microservicebus-core version 3.12.5 (BETA)

  • Added error notification when trying to transfer a file from a Node which doesn’t exist.
June 2nd, 2021

microservicebus.com

  • Node prefix
    • Nodes are generally named using the “node” prefix, E.g. node-00064. This prefix can now be set on the Organization level, which also makes it possible to share IoT Hubs across many Organizations.
  • SLA Report
    • Organizations can now download an SLA report from the Organization page with details about number of nodes, SAL levels and alerts
April 12th, 2021

microservicebus.com

  • Python support!
    • In alignment with the new Python based Node, users can now create and manage Python scripts. The Python Node is a Tier II Node, meaning it’s intended for smaller devices where Node.js might not work. It does not come with all bells and whistles, but is still a fully managed Node.
  • Support for industrial energy protocols!
    • Through partnership with SystemCORP, microServiceBus.com can now offer support for protocols like IEC 61850, IEC 60870-5-101, IEC 60870-5-103 and IEC 60870-5-104.
  • View user public SSH key
    • *Users can now view their public SSH key used for signing in to the Node on the Account page *
  • Added JSON script type
  • Meter Configuration API
    • *Node configuration can also be managed through the API (GET POST)api/organizations/{id}/nodes/{name}/configuration*
  • Improved management of Meter Configuration
    • Improved user experience
  • Integration with Axians Maestro
    • MAESTRO is a SaaS application that makes it possible to manage your assets smartly, remote monitor all your machines and carry out updates at the touch of a button. It can also access data from machines quickly, safe and easily and connect to a platform with dashboard.

microservicebus-core version 0.9.0

The new Python based Node is intended for smaller devices or where Node.js is not working. It comes with some limitation in comparison to mSB-node (Node.js), but is still a very manageable alternative.

microservicebus-core version 3.12.0

  • No updates for this release

microservicebus-snap

  • No updates for this release

meta-microservicebus (YOCTO)

  • No updates for this release

meta-microservicebus-imx7 (YOCTO)

  • No updates for this release

meta-microservicebus-imx8 (YOCTO)

  • No updates for this release

meta-microservicebus-intel (YOCTO)

  • New firmware for intel based boards
March 10th, 2021

microservicebus.com

  • Save MAC address on Node sign-in
    • *MAC address is now saved when Nodes signs in and is accessible from the Node property page (Identifiers tab) *
  • Limit provisioning using MAC address to only once
    • The option of limiting Node provisioning using MAC address has been moved from site setting to Organization settings
  • Allow Co-administrators to claim Nodes
    • Organization owners can now allow Co-admins to claim Nodes from the Organization page
  • Allow Co-administrators to use terminal
    • Organization owners can now allow Co-admins to use the terminal through settings on the Organization page
  • Restrict access for Organization settings
    • All Organization settings has been restricted to Organization owners
  • MFA support
    • None Active Directory users can now enable multi-factor authentication to their account
  • Wipe Node using API
    • Similar to the UI, wiping Nodes resets all settings to default and forces the Node to be claimed.
  • Meter configuration schemas
    • Schemas defining the structure of meter configuration can now be managed from Organizations. Four schemas comes oob for Modbus RTU/TCP and MBus RTU/TCP. For more information see Working with meter configuration
  • Meter configuration
    • A Meter Configuration option is now available on the Node Action menu which can be used to defining Node specific configuration for accessing meters
  • FIXED: Unable to submit bugs & features from some pages

microservicebus-core version 3.12.0

microservicebus-snap

  • No updates for this release

meta-microservicebus (YOCTO)

  • No updates for this release

meta-microservicebus-imx7 (YOCTO)

  • No updates for this release

meta-microservicebus-imx8 (YOCTO)

  • No updates for this release

meta-microservicebus-intel (YOCTO)

  • New firmware for intel based boards
January 21th, 2021

microservicebus.com

  • Add node to whitelist direct from mSB.com
    • Add node to whitelist without importing file. Only input field for MAC, name and append to list.
  • Added support for google IoT state
    • It is now possible to get the state of each device connected to Google IoT
  • Hides element correctly
    • Tabs are hidden when containing information which is not supposed to be displayed

microservicebus-core version 3.11.1

  • Added support for google IoT state
  • Updated dependencies

microservicebus-snap

  • No updates for this release

meta-microservicebus (YOCTO)

  • No updates for this release

meta-microservicebus-imx7 (YOCTO)

  • No updates for this release

meta-microservicebus-imx8 (YOCTO)

  • No updates for this release
December 30th, 2020

HAPPY NEW YEAR!

microservicebus.com

  • New Getting started process
    • New users are now presented an easy to use wizard where they in a few simple steps can create account, organization and provision a device.
  • Support for Google IoT Core
    • Along with Microsoft, AWS and IBM, microServiceBus.com is now supporting Google IoT Core
  • Submit bugs, feature- and change requests
    • Users can now submit bugs, feature- and change requests directly through the portal
  • Enable- and disable nodes through API
    • Organization API has been updated to include enable- & disable Nodes.
  • Patch Node through API
    • Users can now update almost all properties of a Node through the Node API
  • Hide tabs of Services with no properties
    • Tabs in the Service property dialog (in Flows) are now hidden if there are no properties

microservicebus-core version 3.11.0

  • Support for Google IoT Core
    • Along with Microsoft, AWS and IBM, microServiceBus.com is now supporting Google IoT Core

microservicebus-snap

  • No updates for this release

meta-microservicebus (YOCTO)

  • No updates for this release

meta-microservicebus-imx7 (YOCTO)

  • No updates for this release

meta-microservicebus-imx8 (YOCTO)

  • No updates for this release
December 8th, 2020

microservicebus.com

  • Service - Properties (hide tabs without fields)
    • Property tabs such as security- and static properties will now be hidden if there is no content
  • Add new endpoint to update node properties
    • The user now has the option to change a nodes properties through API calls using the node id or the organization id and node name
  • Notify issuer when issue is closed
    • If a user has sent in a bug or feature request, they will now recieve a notification on email when the issue has been dealt with.
  • Un-subscribe to news letter
    • Users can now unsubsribe from recieving mails about latest news in their profile
  • FIXED: Issue where nodes w/ imei could not be updated
  • FIXED: Organization feature dialogs looks bad
  • FIXED: Invalid login attemt throws a general exception
  • FIXED: One line install script -env is not correct depending on organization
  • FIXED: Name validation for services
  • FIXED: Add more description to options on feature/bug dialog

microservicebus-core version 3.10.0

  • Updated dependencies

microservicebus-snap version 3.4.3

  • Updated snap version to 3.4.3

meta-microservicebus (YOCTO)

meta-microservicebus-imx7 (YOCTO)

meta-microservicebus-imx8 (YOCTO)

  • Updated Azure IoT Edge SDK to 1.0.10
December 1st, 2020

microservicebus.com

  • Report bugs and features directly in microServiceBus.com
    • Users will now be able to report bugs and features easily in microServiceBus.com menu using a dialog
  • Updated content for validation email
    • Improved user interface such as register link
  • Better suitable description for NPM feature
    • Organization page has been update to provide improved NPM information such as available versions
  • Confirm Reboot modal added
    • Users will now get a confirmation modal when clicking on reboot node
  • Updated 500 error message
    • Displays a more helpful message when something has gone wrong on the web site’s server
  • FIXED: Create new script stops working when importing service/script
  • FIXED: Import Script Service dialog
  • FIXED: Make IMEI unique for whole environment
  • FIXED: Enable flow#1 also enables flow#2 on same node
  • FIXED: Display clone button depending on itinerary
  • FIXED: Action buttons on Audit page not working #1334
  • FIXED: Resolved issue with cultureinfo and timezone
  • FIXED: Verify Azure IoT connection string

microservicebus-core version 3.10.0

  • Updated dependencies
  • FIXED: Enable flow#1 also enables flow#2 on same node

microservicebus-node version 3.4.3

  • Improved offline check on start up

microservicebus-snap version 3.4.3

  • Updated snap version to 3.4.3

meta-microservicebus (YOCTO)

  • Updated recipe microservicebus-node to 3.4.3 for zeus

meta-microservicebus-imx7 (YOCTO)

  • Added support for RS485
  • Updated meta-microservicebus

meta-microservicebus-imx8 (YOCTO)

  • Added support for Azure IoT Edge zeus
  • Moved Azure IoT Edge home directory to data partition
  • Updated meta-microservicebus
November 15th, 2020

microservicebus.com

  • Notify all users when updates comes available.
    • As new updates are made public, all users will now get notified through an email.
  • Transfer files to Nodes
    • Users can now transfer local files to Nodes using the Device dialog on the Node page
  • Download Node files
    • Users can download files from Nodes using the Device dialog on the Node page
  • Keep state when changing iot hub (Azure IoT Only)
    • Device state (twin/shadow) is now migrated to new IoT Hub upon switching
  • Improved handing of invites and changing accounts
    • Accepting invites will now update the Orgaization list and clear cached session information.
  • Wipe Node
    • Organization Owners are now able to wipe nodes
  • FIXED: Issue with paging on Node page is now resolved
  • FIXED: Issue with snap list in Node details is resolved
  • FIXED: Search button for calendar doesn’t work on auditLog
  • FIXED: Help button on edit Service Script page dosen´t work
  • FIXED: Make IMEI unique for whole environment
  • FIXED Github Login does not work (in any environments)
  • FIXED: Search bar on Vulnerabilities page doesn’t work
  • FIXED: Navigating back from Change IoT hub provider takes user back to the old org details page.

microservicebus-core version 3.9.0

  • Transfer files to Nodes
    • Users can now transfer local files to Nodes using the Device dialog on the Node page
  • Download Node files
    • Users can download files from Nodes using the Device dialog on the Node page
  • FIXED: Loosing connection to Azure IoT Hub is now resolved
  • FIXED: Issues with uploading syslogs is now resolved

microservicebus-node version 3.4.0

  • Reboot on DNS issue
    • If nodes starts up online but but not able to resolve DNS, it will reboot every 5 minutes

microservicebus-snap version 3.4.0

  • 3.4.0 is now available as Stable in snap store
October 14th, 2020

microservicebus.com

  • Handle invites
    • Improved experience for accepting and joining Organizations from the Organization page
  • View Node login information
    • From the Node properties page, users can now review last know mac, ip, firmware version and more
  • Many shortcuts added to the Script & Service editor
    • Read more about all the shortcuts here.
  • FIXED: ServiceNow Integration is now adding company and Organization CI

microservicebus-core version 3.3.0

  • Updated dependencies

microservicebus-core version 3.7.9 (BETA)

  • Vulnerabilities update
  • Added access to Utils and RaucHandler to services
  • Added this.Converter to all services
    • this.Converter can be used to convert from and to different units
  • Added contentType to Azure Send Event
  • Added support for no IoT Hub
  • Updated dependencies
  • Changed node-pty to an optional dependancy
    • node-pty is used as the back-end of the remote Node terminal and was previously installed as needed, but is now included by default.
  • FIXED: There has been a issue where requiring packages like “request” and “async” has failed which is now mitigated
October 08th, 2020

microservicebus.com

  • New Organization page
    • Organization page is now segmented into features where each feature is visible as a widget.
  • IoT Hub instance is now available on the Organization page
  • Added support for Organizations with no IoT Hub
  • FIXED: Organization API GetByTag is now working again

microservicebus-core version 3.7.5 (BETA)

  • Vulnerabilities update
  • Added access to Utils and RaucHandler to services
  • Added this.Converter to all services
    • this.Converter can be used to convert from and to different units
  • Added contentType to Azure Send Event
  • Added support for no IoT Hub
  • Changed node-pty to an optional dependancy
    • node-pty is used as the back-end of the remote Node terminal and was previously installed as needed, but is now included by default.
September 10th, 2020

microservicebus.com

  • Added IoT Hub instance to the Organization detail page
  • FIXED: Autocomplete menu on script editor (Scripts & Services) not visible
  • FIXED: Oneway outbound services showing outbound connection
  • BREAKING CHANGE: API POST whitelist
    • POST /api/organizations/{id}/whitelist will no longer clear the whitelist. To clear the whitelist use the /api/organizations/{id}/whitelist.

microservicebus-core version 3.5.3 (BETA)

  • Added node-pty dependancy
    • node-pty is used as the back-end of the remote Node terminal and was previously installed as needed, but is now included by default.
September 1st, 2020

microservicebus.com

  • Limit Node terminal to Organization owners
  • Added API to update state with object
  • GitHub integration - File pattern
    • Users can now optionally set file pattern to match files imported through GitHub
  • FIXED: Issue with uploading Yocto images has been fixed
  • FIXED: Session IdleTimeout has been increased from 20 => 8 hours

microservicebus-core version 3.5.0

  • Updated Azure SDK’s
    • All azure-iot-* packages has been updated to latest version
  • Added meta data on sign-in
    • IP- and MAC address together with firmware information is added to the sign-in request
August 26th, 2020

microservicebus.com

  • Copy and paste in Terminal
    • Users can now enjoy copy & paste functionality in the Node terminal
  • Warning users when using the remote Node terminal
    • First time users are using the Node terminal they are made aware not to use commmands like halt, shutdown and kill.
  • Receive more data from Node upon sign-in
    • Nodes (core version > 3.4.3) signing in will now include, IP- and MAC address together with firmware info if available. Although the portal is persisting this data, we have yet to figure out where to make it accessible
  • Ui improvements
    • Script & Service page has got some long overdue refresh.
  • mSB API update
    • Create Node API no longer require Node name. If no name is provided, the node will get assigned a new name.
  • More Node sign-in changes
    • If the Node is registerd in the whitelist, the “claim” sign-in request will be bypassed and the Node will automaticly be registered
  • FIXED: json files are no longer being imported from GitHub

microservicebus-core version 3.4.3 (BETA)

  • Updated Azure SDK’s
    • All azure-iot-* packages has been updated to latest version
  • Added meta data on sign-in
    • IP- and MAC address together with firmware information is added to the sign-in request

meta-microservicebus 2.0.45 (BETA) (Yocto layer)

  • FIXED RAUC issue
    • Fixed issue with RAUC service triggering to and causing parsision info to be incomplete
August 20th, 2020

microservicebus.com

  • Filter by tag
    • Users can now filter their search by Tag by selecting one or more tags in the new drop-down list on the Node page
  • Toggle grid view on Flow canvas
    • In the upper-right corner of the Flow designer, users now find a grid toggle button. Toggling grid view will enable services to snap to grid,
  • Ui improvements
    • Some overall improvements on the Flow design dialog
  • FIXED: Fixed issue where user sometimes got redirected to msb.com:44390

meta-microservicebus 2.0.42 (Yocto layer)

  • New terminal screen
    • Terminal users are welcomed with a new shiny screen complemented with commonly used shortcuts
  • Added NTP service
    • The Network Time Protocol (NTP) is used to synchronize the time of a computer client or server to another server or reference time source, such as a radio or satellite receiver or modem. http://support.ntp.org
August 18th, 2020

microservicebus.com

  • Remote Terminal
    • Users can now enjoy a remote ssh terminal from mSB.com with full access to the Node.
  • Claim node to existing node
    • Nodes signing in using claims can now be assigned to existing Nodes
  • More info for Claim Node
    • Nodes that are visible using claims now presents all IP-and MAC addresses
  • Added commands to 3rd party devices
    • A new Action menu appears on the Node property page for 3rd party devices
  • Route to url on login
    • If users navigate to a page before login they will now get redirected to this page after login
  • Added API to execute scripts on a Node
    • Previously the runScript API was only available with tag filter.
  • Passing parameters when running scripts on Node
    • Users can now pass parameters to the runScript API (Organization and Node API)
  • Missing readings GA
    • Alerts on Missing readings is now available
  • UI Update: Updated styles for campaign and price calculator
  • FIXED: Fixed issue with not being able to remove prod itineraries w/o unbinding version
  • FIXED: Fixed issue where it was not possible to remove items from Node Whitelist
  • FIXED: Fixed issue when moving Node to other organization

microservicebus-core version 3.4.0

  • Remote Terminal
    • Users can now enjoy a remote ssh terminal from mSB.com with full access to the Node.
  • Passing parameters when running scripts on Node
    • Users can now pass parameters to the runScript API (Organization and Node API)
  • MSB_NODE_HOST => MSB_HOST
    • Previous environment variable MSB_NODE_HOST is now called MSB_HOST
  • Improved Docker support
    • The Node can now control and manage containers running in Snap/Docker
  • Immediate version update on restart
    • Nodes are now updated after first restart
  • Logging mSB-core version
    • Added msb-core version to logs when starting
  • Login using MAC address is now using all MAC addresses for identification
  • FIXED: Removed legacy signalR and added restart method to AzureIoT
  • FIXED: Fixed issue with installing docker images
April 23th, 2020

microservicebus.com

  • Added support for managing docker containers
    • You are now able to manage docker containers on your Node. Through the Device interface on the Node, you can now install images and containers while also stop start and update them
  • Improved support for Yocto images
    • Better versioning and support for switching partitions
  • Preparations for May release
    • The May release of 2020 will require users to reset passwords

microservicebus-core version 3.0.0

  • Preparations for May release
    • The V2 version of micriServiceBus.com will come with an updated protocol for device management communication.
  • Added support for StopAsync and StartAsync
    • While Start and Stop functions still works as before, the StartAsync and StopAsync provides a more controlled process
  • Added support for managing docker containers
    • You are now able to manage docker containers on your Node. Through the Device interface on the Node, you can now install images and containers while also stop start and update them

meta-microservicebus

  • Added new meta layer for Compulab IMX7
  • Improved support for microServiceBus-dam
Mars 27th, 2020

microservicebus.com

  • Added DeviceManagement API
    • You can now manage devices which are not running the microServiceBus Node agent though the manufacturers provided API.
  • Support for Elvaco CMe2100G3
    • The CMe2100G3 is an MBus metering gateway from Elvaco, compatible with most standard MBus meters and can be configured and managed through miroServiceBus.com
  • Generic installation scripts for Linux and Windows
    • After created a Node, you are guided to the installation and setup page providing you with all possible ways to install the Node. The generic scripts will not only install the Node but all necessary dependencies
  • Updated privileges for claiming nodes
    • Co-administrators are now allowed to claim nodes
  • Copy emails
    • You can now copy email addresses from all your team members on the Organization page

microservicebus-core version 2.9.0

  • Added support for setting the mSB instance as environment variable (MSB_NODE_HOST)
  • FIXED: Formatting errors when showing flows
  • FIXED: Nodes should not try to recover from disconnected state while disabled
Mars 13th, 2020

microservicebus.com

  • Support for agent-less devices
    • You can now manage devices which are not running the microServiceBus Node agent though the manufacturers provided API.
  • Support for Elvaco CMe2100G3
    • The CMe2100G3 is an MBus metering gateway from Elvaco, compatible with most standard MBus meters and can be configured and managed through miroServiceBus.com
  • Generic installation scripts for Linux and Windows
    • After created a Node, you are guided to the installation and setup page providing you with all possible ways to install the Node. The generic scripts will not only install the Node but all necessary dependencies
  • Updated privileges for claiming nodes
    • Co-administrators are now allowed to claim nodes
  • Copy emails
    • You can now copy email addresses from all your team members on the Organization page

microservicebus-core version 2.9.0

  • Added support for setting the mSB instance as environment variable (MSB_NODE_HOST)
  • FIXED: Formatting errors when showing flows
  • FIXED: Nodes should not try to recover from disconnected state while disabled
February 21th, 2020

microservicebus.com

  • Share Flows accross Organizations
    • Flows created in the Root Organization will automaticly be accessable to all Organizations, but only editable in the Root Organization. Services in such FLows are therefor only addressable using Tags and not Node name
  • Notify team members
    • If you need to quickly notifying team members, you can do so using CTRL+R and type “info “ + your message. Eg.
      info I'm restarting node-00002
  • Improved Delete Node page
    • Users are now provided more details on deleting Nodes.
  • Co-administrators can now delete Nodes
    • This was previously only allow for Owners
  • Provision using serial number
    • This was previously only done using IMEI
  • API Update
    • Added API to force Nodes to report Vulnerabilities
  • Azure DevOps integration
    • Improved error handling for setting up Azure DevOps
  • FIXED: Issues with NPM Vulnerability list.
  • FIXED: Organization and Node SLA was not shown properly
  • FIXED: Changing policies on Nodes which had never signed in failed.
  • FIXED: Broken help link from Create Node page

microservicebus-core version 2.8.0

  • Script/Service version shown on start up
  • Flow environment shown on start up
  • Vulnerabilities report update
  • FIXED: Updated mSB-dam error handling
  • FIXED: SNAP list version where wrong

microservicebus-dam version 1.2.3 (Snap stable)

  • Get grants using serial number
  • mSB-dam now calls directly to designated instance of mSB.com
  • Improved stability
  • Improved error handling
February 7th, 2020

microservicebus.com

  • Creating nodes
    • There is now a guide of dialog boxes/forms (wizard) that lead the user through a series of well-defined steps when creating a node. The purpose of this is to simplify the way of creating nodes and the onboarding nodes.
  • Improvments to Console
    • Resolved issue where Console got overflow by moving the content to a sized buffer. The new Console allows a more flexiable search and highlighting.
  • More data-plan details on Node
    • IP-address, session start time and end time has been added to Node details page
  • FIXED: Tracking issues resolved where tracking data was not shown in the history.
  • FIXED: Deleting Organizations was not working

microservicebus-core version 2.7.0

  • Updated dependancies
    • Updated nyc => 15.0.0 & azure-iot-device => 1.12.2
  • Snap refresh
    • Preserve devmode for snaps installed as devmode
  • Console overflow
    • Truncating log messages > 1000 chars
  • FIXED: Vulnerability scan had some issues that has been resolved
January 17th, 2020

microservicebus.com

  • Show snap list in vulnerabilities view
    • The Vulnerabilities page is now showing an aggregated view of all Snaps used, along with information about latest versions
  • Improved visualization of tags
    • Tags on Nodes are now shown as “tags” rather than a comma separated list.
  • Organizations are created as CI’s in ServiceNow
    • For the purpose of aggregated incidens (such as “One or more nodes has outdated Snaps…”, Organizations are now registered as CI’s in ServiceNow.
  • Added new System error codes:
    • 90006 - Organization has npm vulnerabliteies
    • 90007 - Organization has Snaps to be updated
    • 90010 - Failed login
    • 90011 - Invalid user login
    • 90020 - Data plan limit approaching
    • 90021 - Data plan reached

microservicebus-core version 2.6.0

  • Improved support for cloud to device messaging
  • Improved handling of octet-stream
  • Daily reporting of installed Snaps
December 12th, 2019

microservicebus.com

  • Service usage
    • You can now find out wich Flows are using a service directly from the Service/Script page
  • Flow usage
    • Ever wanted to know which FLows are used by a Node. You can now find out using the Action button on the Nodes page.
December 1st, 2019

microservicebus.com

  • Improved Node vulnerabilities view
  • Improved ServiceNow integration
    • Better syncronization with CI’s
  • Performance update
    • Performance imrovements done to Node, Flow and MAnagement page

microservicebus-core version 2.4.0

  • Improved support for Node vulnerabilities
    • Nodes now provide informatoin about snaps
  • Updated Azure IoT SDK
    • azure-iot-device => 1.12.0
    • azure-iot-device-mqtt => 1.11.0
    • azure-iot-device-amqp => 1.11.0
  • Avoiding loading dependancy files multiple time
    • Depenancy files will now only get downloaded once although referenced from many services.
  • Better support for cloud messaging
  • Added support for octet stream
  • Added support for rauc and azure iot-edge
  • Improved integration with snap

microservicebus-yocto

  • Added support for Azure IoT Edge
November 7th, 2019

microservicebus.com

  • Un-suck IoT campaign
    • https://microservicebus.com/iotsucks and home page carousel.
  • Added suport for Azure IoT Edge.
    • IoT Edge nodes are based on docker and can run cloud modules such as machine learning side-by-side with the microServiceBus node. By moving certain workloads to the edge of the network, your devices spend less time communicating with the cloud, react more quickly to local changes and operate reliably even in extended offline periods.
  • Claim Node
    • Nodes started without parameters can now be claimed in portal
  • microServiceBus.API
    • Restart Node by id
  • Updated price calculator
    • https://microservicebus.com/pricecalculator
  • Minor UI updates
    • Some minor graphical updates and fixes has been applied on the Node page.
  • FIXED: Bug with invites not deleted
  • FIXED: Pricecalculator 24/7 prices fixed
  • FIXED: Tag are not saved when cloning stage flow

microservicebus-core version 2.4.0

  • Added suport for Azure IoT Edge.
    • IoT Edge nodes are based on docker and can run cloud modules such as machine learning side-by-side with the microServiceBus node. By moving certain workloads to the edge of the network, your devices spend less time communicating with the cloud, react more quickly to local changes and operate reliably even in extended offline periods.
  • Disable debug after 30 minutes.
    • Debug console will automaticly be disabled after 30 min.
  • FIXED: Fixed History (TTLCollection)

microservicebus-node version 2.0.10

  • Updated node.js version
    • Node.js version 12.11
  • Updated snap version to 2.0.10
    • Logic for logging in with IMEI is moved to mSB-core

meta-microservicebus-raspberrypi (Yocto) version 1.2.0

  • Update bundle version as msb-node version now is 2.0.8
  • Minor fixes
September 29th, 2019

microservicebus.com

  • Added suport for signing in Nodes anonymous.
    • Signing in Nodes anonymous, and later claiming the Node in the portal provides an easy provitioning process. visit microServiceBus.docs for more information
  • Integration with Fiware
    • microServiceBus.com can now be integrated with Fiware Orion Context Broker to store and update entities from meters and sensors in the field. For more information about Fiware, visit https://www.fiware.org
  • microServiceBus.API
    • More Flow API’s for browsing Flows and Services
  • Move Nodes to other Organizations
    • This feature no longer require the node to be online
  • Minor UI updates
    • Some minor graphical updates and fixes has been applied on the Node page.

microservicebus-core version 2.2.0

  • Added suport for signing in Nodes anonymous.
    • Signing in Nodes anonymous, and later claiming the Node in the portal provides an easy provitioning process.
  • FIXED: dependencies marked with vulnerabilities
  • FIXED: Vulnerabilities scan for Snap Nodes

microservicebus-node version 2.0.10

  • Updated node.js version
    • Node.js version 12.11
  • Updated snap version to 2.0.10
    • Logic for logging in with IMEI is moved to mSB-core

meta-microservicebus-raspberrypi (Yocto) version 1.2.0

  • Update bundle version as msb-node version now is 2.0.8
  • Minor fixes
August 13th, 2019

microservicebus.com

  • Updated Audit log
    • Added Node description and fixed audit logs for snap
  • FIXED: Log file list
    • List of log files at the Nodes page is now sorted correctly

microservicebus-core version 2.1.0

  • Add aggregated exception interval
    • Users can now set how often exceptions of same type get sent to tracking
  • Added refreshSnap
    • Refresh Snap is called from the portal or API
  • FIXED: dependencies marked with vulnerabilities
  • FIXED: Vulnerabilities scan for Snap Nodes
August 8th, 2019

microservicebus.com

  • Manage Incident policies
    • Incident policies is part of Device Management and allow you to take actions on exceptions and alerts, such as when Nodes comes of line or custom alerts. For more info visit docs.microservicebus.com
  • ‘SLA’ (Service Level Agreement) information and ‘Cost Center’ now available at ‘/api/organizations’ API.
  • Update Snaps
    • Snaps (Ubuntu) can now be updated using the Manage device environment dialog. For more info visit docs.microservicebus.com
  • Run scripts
    • Patch scripts can be remotely executed on Nodes using the Manage device environment dialog. For more info visit docs.microservicebus.com
July 19st, 2019

microservicebus.com

  • Manage firmware
    • Firmware can now be managed through a special dialog on the Nodes page.
  • Mark partition
    • You are now able to mark which partition to be active

microservicebus-core version 2.0.90

  • Updated Azure device SDK
    • Updated azure-iot-sdk-node => 1.10.0
  • Update yocto firmware image
    • Improved error handling
  • Enabled Mark partition
July 7th, 2019

microservicebus.com

  • Vulnerabilities viewer
    • Vulnerabilities from all nodes are presented in one view, grouped by severity
  • Added CostCenter and SLA
    • CostCenter and SLA has been added to Organization and Nodes
  • Usage API
    • Added /api/organizations/usage to give insight to billing.
  • Price calculator
    • To provide a better cost estimate including portal, device management and sim-cards
  • FIXED: Avoid sending empty grants grants to mSB-dam
  • FIXED: Japser provisioning
  • FIXED: Github integration

microservicebus-core version 2.0.80

  • Updated snapcraft version
    • Added tpm plug
  • Updated dependancies
  • FIXED: vulnerabilities for Security Alerts on tar package

microservicebus-node version 2.0.7

  • Vulnerabilities Scan
    • A Vulnerability scan is performed daily and submitted to the portal
  • FIXED: Changes to Node policies should be applied immediately
  • Minor bug fixes
June 1st, 2019

microservicebus.com

  • Clone Flow - handle target environment
    • Optionally bind version of services
  • Add validation of HMAC signature in JasperNotification API.
    • Incoming requests from Cisco Jasper are now validated using HMAC signature.
  • Preparation for support for new IoT Providers
    • Plan is to support Oracle Cloud and FiWare
  • User documentation

microservicebus-core version 2.0.70

  • Do retries when downloading service files
    • To prevent failures while downloading scripts and services
  • Increased the retry interval when signing in using imei
    • Preventing unnecessary restart of service
  • Updated AWS SDK => 2.2.1
  • Azure IoT SDK stability improvements.
  • FIXED: Unable to download new firmware due to full disk
    • Clean firmware directory before downloading new image
  • FIXED: Unable to download syslogs
    • Improved error handling for uploading syslogs + updated dbus interface
  • Support for compression
    • Built-in support for compression of messages
  • Minor bug fixes
May 13th, 2019

microservicebus.com

  • Integrate external ticketing system (ServiceNow)
    • Users can now throw their own custom exceptions to ServiceNow
  • Updated all help links
    • Linked all help pages to docs.microservicebus.com
  • Manage state from Node page
    • *Users can now set Nodes in Normal-, Maintenance- and Test mode *
  • Only accept accepted pull requests
    • When using git integration, PR’s are only completed when accepted
  • Updated microServiceBus.API
    • Update API to include FindById (ICCID, IMEI or hostname)
  • Improved error handling in Node Sign-in
    • Making it easier to find issues related to Sign-in
  • Use Shared Secret to validate inbound calls from Jasper
    • Shared secrets can now be used to validate inbound calls from Cisco Jasper
  • Clone Flow itinerary
    • Users are now able to clone Flows while mapping Node names and tags
  • Download Syslog from portal
    • Users can now download syslogs from the Nodes page
April 21th, 2019

microservicebus.com

  • Maintenance and Test mode on Nodes
    • Nodes can now be set in Maintenance to prevent alarms
  • Simplified authentication for Site Verification
    • Nodes now has to be set to TEST MODE before accepting tests to run
  • Toggle Comment and file name in script window
    • Mark text in script editor and toggle commenting the text using CTRL+/
  • Only accept accepted pull requests
    • When using git integration, PR’s are only completed when accepted
  • Stay on scripts page when switching organization
    • Same behavior as for Nodes and Flows
  • Improved error handling in Node Sign-in
    • Making it easier to find issues related to Sign-in
  • Use Shared Secret to validate inbound calls from Jasper
    • Shared secrets can now be used to validate inbound calls from Cisco Jasper
  • Added QR code to test scripts
    • Upon saving a Test Script, a QR code is presented for easier exposing the test

microservicebus-core version 2.0.50

  • Maintenance and Test mode on Nodes
    • Nodes can now be set in Maintenance to prevent alarms
  • Added dbus IsActive endpoint
    • Enabling external applications and services to check on status for mSB-core
  • More portal notifications
    • Nodes are now notifying on firmware updates
  • Support for compression
    • Built-in support for compression of messages
  • Minor bug fixes
March 26th, 2019

microservicebus.com

  • Improved tracking and monitoring
    • Better and faster tracking and integration with ServiceNow
  • Manage Incident Policies allowing organizations to add custom incidents
    • Users are now able to set up custom incidents which will be escalated to ServiceNow
  • Site verification app
    • The site verification app can be used to run custom unit tests on Nodes at runtime
  • Added QR code to test scripts
    • QR-code for faster access to the site verification app
  • Download and view syslogs from portal
    • Users are now able to initiate, download and view syslogs from Nodes
  • Trigger firmware update from action menu
    • Before this release, firmware updates could only be initiated from the API
  • Delete firmware image
    • Users can now remove firmware images from the Node page
  • “Remove me” from organization and email tooltip of users
    • Users can now remove themselfs from organizations

microservicebus-core version 2.0.27

  • Update Yocto firmware works with version and platform
    • This prevents images to be downloaded installed if the device is already using the latest version
  • Site verification scripts
    • Allowing the execution of unit tests to be executed on the Node. These scripts can be used to verify installation setup.
  • Updated Azure device SDK to 1.9.4
    • Nodes are now being notified on disconnect
  • Support for compression
    • Built-in support for compression of messages
  • Minor bug fixes
February 26th, 2019

microServiceBus.com

  • Serverside performance improvements
    • Mainly focusing on Node sign in
  • On-site test scripts
    • Providing capabilities to let site technitians running unit test on-site to verify installation

microservicebus-core version 2.0.14

  • Enable remote unit testing
    • *To support On-site test scripts (see microServiceBus.com)
  • Improved support for Yocto
    • Extract platform and version from Yocto bundle
  • Updated Azure SDK => 1.9.3

microservicebus-dam version 2.0.1

  • Extended to support Yocto
    • Corrected bug where DAM only worked in snap env.
February 1st, 2019

microServiceBus.com

  • UI performance improvements
    • Improvments of how scripts and styles are loaded
  • Managing ssh user account and keys
    • Improve UX
  • Visualization of environment status
    • Improved visualization of environment with all networks and serialport
  • Show device state (Azure- & AWS IoT hub) on Node property
    • Users can now view and edit device twin/shadow directly in the portal
  • Updating code snippet colleciton to include new features
    • Added snippets for GetCurrentState, GetLocalTime and GetInstanceOf
  • FIXED: Closing flow window by clicking on the upper right corner botton doesn’t work

microservicebus-core version 2.0.1

  • TTLCollection available from services
    • TTLCollection to support adding unique items
  • Add all networks and serialports to requested Environment
    • see microServiceBus.com
December 27th, 2018

microServiceBus.com

  • Lock microservicebus-core version on Organization
  • Lock microservicebus-core version on Node
  • Lock script/service version in Flow
  • CTRL+S/Cmd-S short key for saving scripts
  • Updated support for binary messages
  • AZUREDEBUG option
  • Save last latest command using CTRL+R
  • Added functionality to move node between organizations
  • API to apply Node template to existing nodes
  • Send invites to multiple people
  • Azure SDK 1.8
  • TTLCollection built in to microservice.js
  • FIXED: Resize “View source” window
  • FIXED: Remove services from flow

microservicebus-node version 2.0.0

  • Lock microservicebus-core version

microservicebus-core version 2.0.1

  • microservicebus-core is now running the latest version of Azure Device SDK, fixing issues where messages did not get delivered properly
  • Updated support for binary messages

microservicebus-dam version 1.0.0

  • Manage SSH keys in portal
  • microservicebus-dam snap/daemon
  • Grant access to Node

mSB-yocto version 1.0.0

  • microservicebus-node Yocto layer
  • Upload firmware
  • Firmware updates using RAUC (bootloader interface)
  • Trigger “Update firmware” from mSB.API
November 30th, 2018

microServiceBus.com

  • Grant individual logon privilages (mSb.dam)
  • Lock organization to microservicebus-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

microservicebus-node version 1.0.27

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

microservicebus-core version 1.2.52

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

microservicebus-dam version 1.0.0

  • Support for Device Access Manager
  • Updated snap
November 4th, 2018

microServiceBus.com

  • 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

microservicebus-core (1.2.40)

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

microServiceBus.com

  • 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/microServiceBus.com
October 10th, 2018

microServiceBus.com

  • 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

microservicebus-core (1.2.31)

  • Fixed issue restarting COM upon State gets updated
September 7th, 2018

microServiceBus.com

  • 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

microservicebus-core (1.2.18)

  • FIXED: Changed state should trigger all “Receive State” services

microservicebus-node (1.0.26)

  • Add timeout to ensure installation of core does not hang
  • Updated snap version to 1.26
August 11th, 2018

microServiceBus.com

  • 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
July 23rd, 2018

microServiceBus.com

  • 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

microservicebus-core

  • Implement policys. (disconnect, reconnect, offline mode)
June 30th, 2018

microServiceBus.com

  • 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

microservicebus-core

  • Many more events persisted to History
  • Removed redundant packages that were part of microservicebus-core
  • Disable IoT Hob connection on disabling the node.
June 19th, 2018

microServiceBus.com

  • 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

microservicebus-core

  • 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
June 5th, 2018

microServiceBus.com

  • 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 microServiceBus.com 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

microservicebus-core

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

    Apr 22nd, 2018

    microServiceBus.com

  • 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 microServiceBus.com
  • 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 has been resolved
  • FIX: Default organizations is stored in session
  • FIX: Organizations can now change names

    microservicebus-core

  • Set environment parameter at startup node start now accepts –env such as: 
    node start -c ASDGJ -n myNode -env myorg.microservicebus.com
March 19th, 2018

microServiceBus.com

  • 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 microServiceBus.com 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.

microservicebus-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 xxx.microservicebus.com] [--beta]

microservicebus-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 xxx.microservicebus.com // Requires update of microservicebus-node
February 23rd, 2018

microservicebus-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

microServiceBus.com

  • Resend messages from Node
    • On the Node page of the microServiceBus.com portal you are now able to resend messages persisted on the device.
  • GitHub integration
    • You can now synchronize Scripts in your microServiceBus.com 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
February 6th, 2018

microServiceBus.com

  • 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
January 27th, 2018

microServiceBus.com

  • 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

microservicebus-core (1.0.70)

  • Implement retry policy “NoRetry” for Azure IoT.

  • Migrated to 1.3.0 of for Azure device SDK.

mSB.mbed

  • Build service script for UBLOX_EVK_ODIN_W2
December 7th, 2017

microServiceBus.com

  • 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
November 12th, 2017

microServiceBus.com

  • 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
October 28th, 2017

microServiceBus.com

  • 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
    • microservicebus-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
October 28th, 2017

microservicebus-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
March 29th, 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
February 22th, 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.
February 6th, 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
    • microServiceBus.com 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 microServiceBus.com. 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.