We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
The text was updated successfully, but these errors were encountered:
I can take this on board. The feature exists in newer versions of node-opcua and need to be called appropriatly in the binding.
Sorry, something went wrong.
opcua: handle nsu in nodeId (fixing eclipse-thingweb#1334)
71765c5
5982c62
32cbe50
No branches or pull requests
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?
The text was updated successfully, but these errors were encountered: