Custom Topic Configuration for Litmus Edge OPC UA Server

see the steps below to update a tag in the litmus edge opc ua server that originates from a source other than devicehub solution the litmus edge opc ua server allows you to enter any topic as the data source when configuring a new tag the server still expects a custom topic to have the same fields in the message as a devicehub message at a minimum, the fields success and value are required in the payload of the message for the opc ua server to update the tag this guide assumes that you have already configured and enabled the opc ua server and that a tag is already configured the following instructions show how to update a tag on the opc ua server with the current timestamp note it is important to match the data type of the value you are sending with the data type of the configured tag in the opc ua server if the data types do not match, the value may not be updated on the opc ua server to update a custom topic in le opa ua server in litmus edge, navigate to flows manager and open the flow canvas see create a flow docid 7x0n7c4dxswtd61vpibza to learn more on the flows canvas, add an inject node, a function node, and a devicehub publish node double click the inject node configure it to inject the timestamp on an interval, every 1 second double click the function node insert the following code the payload will generate the following output double click the datahub publish node in the topic field, enter the topic name configured in your opc ua tag below is the configuration of the opc ua tag used in this example the structure of the json string you are sending to the custom topic must have the and value keys at minimum for the opc ua server to update the value from that topic if success is set to true, the value is updated and the status of the tag is good if success is set to false , the value is updated and the status of the tag is badresourceunavailable