-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
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
Expanded Node ID for OPCUA #1334
Labels
binding-opcua
Issues related to opc ua protocol binding
Comments
I can take this on board. The feature exists in newer versions of node-opcua and need to be called appropriatly in the binding. |
erossignon
added a commit
to node-opcua/node-wot
that referenced
this issue
Nov 29, 2024
erossignon
added a commit
to node-opcua/node-wot
that referenced
this issue
Nov 29, 2024
erossignon
added a commit
to node-opcua/node-wot
that referenced
this issue
Nov 29, 2024
erossignon
added a commit
to node-opcua/node-wot
that referenced
this issue
Feb 4, 2025
erossignon
added a commit
to node-opcua/node-wot
that referenced
this issue
Feb 4, 2025
erossignon
added a commit
to node-opcua/node-wot
that referenced
this issue
Feb 4, 2025
erossignon
added a commit
to node-opcua/node-wot
that referenced
this issue
Feb 4, 2025
erossignon
added a commit
to node-opcua/node-wot
that referenced
this issue
Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: