Open danielpeintner opened 2 days ago
During a PlugFest we discovered that the opcua binding did not manage to properly resolve expanded node ids
We tried to use
"opcua:nodeId": "nsu=xxxxxx;s=\"LED\".\"State\""
(Note: xxxx was the actual namespace)
instead of something like this
"opcua:nodeId": "ns=3;s=\"LED\".\"State\""
Anyhow, it did not work, and we were not exactly sure whether it is not properly implemented or we are doing something wrong.
@erossignon maybe you have some idea?
I can take this on board. The feature exists in newer versions of node-opcua and need to be called appropriatly in the binding.
During a PlugFest we discovered that the opcua binding did not manage to properly resolve expanded node ids
We tried to use
"opcua:nodeId": "nsu=xxxxxx;s=\"LED\".\"State\""
(Note: xxxx was the actual namespace)
instead of something like this
"opcua:nodeId": "ns=3;s=\"LED\".\"State\""
Anyhow, it did not work, and we were not exactly sure whether it is not properly implemented or we are doing something wrong.
@erossignon maybe you have some idea?