search

mikakaraila / node-red-contrib-opcua

A Node-RED node to communicate OPC UA. Uses node-opcua library.
Other
208 stars 191 forks source link

BrowseName property not Included in messages when using READ MULTIPLE #691

Closed arjendeetman closed 2 months ago

arjendeetman commented 2 months ago

First of all, thank you for making this nice Node-RED package available.

When creating an OPC UA item, users have the ability to assign it a name. Subsequently, when reading the node using a client with a single READ operation, the browseName is appended to the message. This facilitates easy identification and distinction of different nodes by filtering messages based on the browseName property.

However, when attempting to read multiple nodes using a READ MULTIPLE operation, the browseName property is not included in the messages. Consequently, users are unable to distinguish between different messages based on the assigned names. While it's possible to differentiate messages based on the node ID, leveraging the browseName is a more intuitive and convenient approach.

Is it possible to add the browseName property to messages generated when using READ MULTIPLE operations? This enhancement would significantly improve usability and streamline the process of identifying and distinguishing between multiple nodes.

Best regards,

Arjen

arjendeetman commented 2 months ago

I managed to change the source and add this functionality. Please see the pull request https://github.com/mikakaraila/node-red-contrib-opcua/pull/692

The set item name can be accessed via msg.topic.browseName

arjendeetman commented 2 months ago

Thank you for merging my pull request. We can close this issue.