v1.4_beta - Release of Dynamic MQTT Mapper

Changes

This release contains the following enhancements:

1. Feature to parse binary, flat files using a selection in a popup wizard, see documentation for details.
2. Feature to use a self-signed certificate for the connection to the broker. The connection tab was extended.
3. Feature: When the snoop process is stopped the source and target templates are initialised and a hint in th eUI is shown
4. Migration to 1015.0.172

Fixes

1. Several bug fixes when starting & stopping the snoop process
2. When a message was received with a topic name which could not be resolved, an exception was thrown and the connection to the broker was closed. Now only the statistic on the monitoring tab is updated and the exception is logged. But the connection is not closed.

v1.3_beta - Release of Dynamic MQTT Mapper

Fixes

1. Several bug fixes when starting & stopping the snoop process
2. When a message was received with a topic name which could not be resolved, an exception was thrown and the connection to the broker was closed. Now only the statistic on the monitoring tab is updated and the exception is logged. But the connection is not closed.

Changes
This release contains the following enhancements:

1. Feature to parse binary, flat files using a selection in a popup wizard, see documentation for details.
2. Feature to use a self-signed certificate for the connection to the broker. The connection tab was extended.
3. Feature: When the snoop process is stopped the source and target templates are initialised.

v1.2 - Release of Dynamic MQTT Mapper

Fixes
This release contains the following fixes for:

1. Several issues when adding, deleting and updating substitutions in the second wizard step
2. Fix for issue #20

Changes
This release contains the following enhancements:

1. Under Connectionyou can now enable/disable the logging of received payloads, to facilitate easier tracking of mapping behaviour
2. Under Mapping:
   1. You can now create a mapping as well for files in flat file format
   2. Mappings can now extract complete objects from the source payload and map these to the target
   3. The option Defines Device identifierwas removed, since this is now detected automatically
   4. The complete hierarchy of topic levels /plant1/line1/device1_measure1_Type is now added to the source payload as "_TOPIC_LEVEL_": [ "plant1", "line1", "device1_measure1_Type" ]. This allows to use any this information when resolving the external id to the intern Cumulocity [source.id]
   5. Changing rest endpoints for GET/POST of configuration for connection and service
   6. Moving buttons Snooped templates and Samples payload to the upper part of the second wizard step
   7. Adding property ``Expand Array```, see the readme doc
   8. Adding property ``Repair Strategy```, see the readme doc

v1.1 - Release of Dynamic MQTT Mapper

What's Changed

Breaking Change
In the release v1.0 we used to extract only on level of the topic names and assign this to the token _DEVICE_IDENT_.
This concept has been generalised. If you use, e.g. a topic name plant/line/device the following json attribute _TOPIC_LEVELis added to the payload:

  "_TOPIC_LEVEL_": [
    "plant",
    "line",
    "device"
  ]

The items in the array can be used, e.g. to resolve the external id to the internal Cumulocity source id.
This relates to: #13 .

The button Device Identifier is deleted for the above mentioned reasons.

Copy mappings
You can now copy an existing a mapping from the Web UI by selecting a mapping in the table of mappings.

Fixed bug
#15 : Now values for measurements are submitted correctly.

v1.0 - First Release of Dynamic MQTT Mapper

This is the first release of the Dynamic MQTT Mapper.

For the full supported features list and guidance please read the README

Microservice: mqtt-mapping-service.zip
Frontend Plugin: mqtt-mapping.zip