3.12.1 (Vienna Siberian Tigers) - May 2022

New Features 3.12.1

• Support for MindSphere Integrated Data Lake in China
• Docker images based on node-red 2.2.2
• Bumped all dependencies

3.12.0 (Vienna Siberian Tigers) - May 2021

New Features 3.12.0

• Support for "bidirectional" communication with MindSphere [#129]
• new message type to read asset information [#129]
• new message type to execute a custom javascript script using MindSphere javascript/typescript SDK [#129]
• Bumped all dependencies

3.11.0 (Vienna Jaguarundi) - March 2021

New Features 3.11.0

• Important Bugfix for Unitless Mapping (see below)
• Implemented Support for EU2 Data Lake
• New setting: Data Lake Only - the node will not try to retrieve configuration if it is only used for data lake
• New setting: Emit control message - the node will emit a message which can be used to control the data ingest
• New setting: Hide request statatus information - reduces the node verbosity
• New example flows on https://playground.mindconnect.rocks - queueing the messages, handling ingest pressure
• Documented how to manage the node configuration from the flow on playground.
• Bumped all dependencies
• Restructured files for better readability
• Upgraded json schema definitions for ajv v7 reqirements

Bugfix 3.11.0

• Important - There is now a new type of mapping in MindSphere (unitless mapping) which versions before 3.11.0 are not aware of and which was causing the node to create mappings with the "null" unit. (that is "null" as a string). This is fixed in version 3.11.0. It is strongly recommended to upgrade to 3.11.0 if you are using automatic mapping feature.

3.10.0 (Vienna European Shorthair) - November 2020

New Features 3.10.0

• Support for Generation of Signed Upload URLs
• Data Lake File Upload Support
• Better error messages when the node input is misconfigured
• Bumped all dependencies

Bugfix 3.10.0

• The node now handles long asset names correctly

3.9.2 (Vienna Bobcats) - October 2020

Bugfix 3.9.2

• Node not working properly on IOT 2040 with Node-RED 0.20.7 (#107)

3.9.1 (Vienna Bobcats) - September 2020

Bugfix 3.9.1

• Node not loading on raspberry pi with chromium 79.0 (#103)
• Copy to clipboard not working on raspberry pi with chromium 79.0 (#104)

3.9.0 (Vienna Bobcats) - September 2020

New Features 3.9.0

• Automatical Data Source Configuration and Mapping to a selected asset. (#89)
• Configuration Information Dialog about current agent state.
• Buttons to copy timeseries-, bulk timeseries-, event- and file- templates to the clipboard.
• New examples on https://playground.mindconnect.rocks for flows
• MindSphere Start for Free suited example on https://playground.mindconnect.rocks
• Bumped all dependencies

3.8.1 (Vienna Tigers) - July 2020

Bugfix 3.8.1

• Removed Ajv from global scope

3.8.0 (Vienna Tigers) - July 2020

New Features 3.8.0

• Custom Event Support via _customEvent switch on the message.
• Added msg._includeMindSphereToken and msg._ignorePayload switch which propagates the MindSphere Authentication Token in msg.headers
• The msg._includeMindSphereToken switch can be used in conjuction with the http request node to call custom southbound mindsphere APIs (#83)
• New examples on https://playground.mindconnect.rocks for flows
• Bumped all dependencies
• New Logo <3

BugFix 3.8.0

• Node is now Node-RED 1.10 compatible.

3.7.0 (Vienna Ocelots) - April 2020

3.7.0 (Vienna Ocelots) - April 2020

New Features 3.7.0

• new docker images with version 1.0.* for multiple architectures
• the old 0.20.* based docker images are now deprecated
• the node has now a link to agent diagnostic application in the mindsphere
• new configuration button to delete all local data of the agent (including the .mc/agentconfig.json)
• the node will await parallel asynchronous requests automatically after configured number of seconds
• the node will regularly display information about asynchronous requests

Important docker image user change - for users upgrading from versions before 3.7.0

If you are using host directories for docker persistence and you are upgrading from previous version of docker images (which were based on 0.20.* version of node red) you will have to ensure that any existing data and .mc directory has the correct ownership.
As of 1.0 this needs to be 1000:1000. This can be forced by running the command

sudo chown -R 1000:1000 path/to/your/node-red/data
sudo chown -R 1000:1000 path/to/your/node-red/data/.mc

on the host system.

Consider using docker named volumes instead.

This is necessary because of the change in the base docker image of node-red. See also https://nodered.org/docs/getting-started/docker

Bugfixes 3.7.0

• the node now removes previous keep alive and async logging interval on redeployement (#39)
• fixed CSS for node-red > 1.0.0 (the node title is white again)
• updated to mindconnect-nodejs 3.7.0
• bumped all dependencies

Stay strong, safe and healthy! <3 :hearth: