From 9ce539554736eea18449fc05bbf3cada7b6e3978 Mon Sep 17 00:00:00 2001 From: Wolfgang Hottgenroth Date: Tue, 22 Feb 2022 17:20:48 +0100 Subject: [PATCH] fix in readme --- readme.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/readme.md b/readme.md index 2685786..2801e79 100644 --- a/readme.md +++ b/readme.md @@ -51,11 +51,11 @@ The section `opcua` contains a list of OPC-UA servers to be queried. Each entry The attribute `nodes` finally contains the list of variables to be queried. It contains the namespace index (`ns`), the node-id (`n`) and an optional descriptive name (`d`). Namespace index and node-id can be determined using for instance UAExpert when browsing the server and navigating to the relevant variables. The descriptive name - if given, otherwise the display name of the variable is used - becomes in `flat` mode part of the topic, in `structured` mode it becomes an attribute name within the message. -In `flat` mode the final topic will be `${mqtt.publicTopicPrefix}/${opcua.name}/${opcua.node.ns}/${opcua.node.d}` - ## Example Output +In `flat` mode the final topic will be `${mqtt.publicTopicPrefix}/${opcua.name}/${opcua.node.ns}/${opcua.node.d}` + An example for the MQTT messages according to the above configuration in `flat` mode is: opcua/apl/0/pv {"serverName": "apl", "nameSpaceIndex": 0, "variableName": "pv", "value": 19.849281311035156} @@ -67,6 +67,7 @@ An example for the MQTT messages according to the above configuration in `flat` opcua/apl/0/tv {"serverName": "apl", "nameSpaceIndex": 0, "variableName": "tv", "value": 22.574615478515625} opcua/apl/0/qv {"serverName": "apl", "nameSpaceIndex": 0, "variableName": "qv", "value": NaN} + In `structured` mode the final topic will be `${mqtt.publicTopicPrefix}/${opcua.name}` An example for the MQTT messages according to the above configuration in `flat` mode is: