Page History

...

Note: Subscriptions such as site# or site+ are invalid as there is no topic level for the wildcard to denote. 

For the examples below we will subscribe on test/# 

No Tag Name configured  

Let say we have a publish received on the topic "test/data/point" with value "12345".  If no Tag Name is configured, and a message is received, MQTT Engine will create a two folders "test" and "data" and a tag "point" with the value of "12345".

Image RemovedImage Added

Image RemovedImage Added

Tag Name Configured

If a Tag Name is configured, lets call it "payload", then MQTT Engine will convert each token in the topic to a folder and create a tag called "payload" with the value "12345"

Image RemovedImage Added

Image RemovedImage Added

In most cases it is useful to specify a Tag Name in order to prevent cases when a publish on a topic can overwrite a previously created tag, changing it into a folder.  Consider the case where you have the following two publishes:

...

Let say we have a publish received on the topic "test/data/json" with value '{ "stringTag" : "12345", "folderTag" : { "intTag" : 1, "boolTag" : true } }'. MQTT Engine will create a two folders "test", "data" and "json" followed by a tag/folder structure representing the JSON value of the payload. 

Image RemovedImage Added

Image RemovedImage Added

Additional Resources

...