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_LEVEL
is 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.