Skip to content
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

Open
danielpeintner opened this issue Nov 28, 2024 · 1 comment
Open

Expanded Node ID for OPCUA #1334

danielpeintner opened this issue Nov 28, 2024 · 1 comment
Labels
binding-opcua Issues related to opc ua protocol binding

Comments

@danielpeintner
Copy link
Member

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?

@danielpeintner danielpeintner added the binding-opcua Issues related to opc ua protocol binding label Nov 28, 2024
@erossignon
Copy link
Contributor

erossignon commented Nov 29, 2024

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
binding-opcua Issues related to opc ua protocol binding
Projects
None yet
Development

No branches or pull requests

2 participants