Closed AHyduchak closed 1 year ago
The output of the debug node showing the msg contents.
hi, same error here, i m trying to find more details on this, the error lies probably on the : parseNamspaceFromItemNodeId function line 503 of the opcua-iiot-core.js , the function receives an item wich is a single value and tries to get the namespace from the nodeitem (wich contains the value) instead of the item.nodeId
i edited https://github.com/BiancoRoyal/node-red-contrib-iiot-opcua/blob/master/src/core/opcua-iiot-core.ts
(in fact locally i edited the equivalent javascript file (i dont know js enough to understand what are ts files ) line 513 nodeNamespace = item.nodeId.substring(3, item.nodeId.indexOf(';'));
This should be fixed with the changes from #157.
(in fact locally i edited the equivalent javascript file (i dont know js enough to understand what are ts files )
.ts
files are TypeScript, a superset of JavaScript that adds types. We compile those into JavaScript for distribution.
E2E tests were disabled in TypeScript migration and is now active again see #177 - works since tag v4.0.7
This issue is stale because it has been open 60 days with no activity. It will be closed in 15 days, but can be saved by removing the stale label or commenting.
Which node-red-contrib-iiot-opcua version are you using?
4.0.1
What happened?
I am unable to write a value to an OPC item.
I have tried structuring the message where the
valuesToWrite
ismsg.valuesToWrite
andmsg.payload.valuesToWrite
as indicated in the General Changes of the description page.The Write node returns:
TypeError: nodeItem.indexOf is not a function
Server
Other/External server
How can this be reproduced?
The problem can be reproduced with my flow as well the provided example flows flows.txt .
What did you expect to happen?
No response
Other Information
No response