Closed Flumpje closed 4 years ago
@Teeffelen but there is no name and no datatype as you see ;) in this version of node-opcua it is only to fix on browsing for every monitor event to read that information from the key (nodeId) - maybe I missed some, then let me know ...
recipe to enhance:
That could better and easier be done with a browse once for the node-id if it is unknown and organizing them in a context dictionary inside Node-RED.
I'm submitting a ... (check one with "x")
Feature
( ) feature request
What is the motivation or Use Case for your feature request?
Support
Problem
Information
Current behaviour
Pass through from the "name" and "datatypeName" in the listener does not work is: "addressSpaceItems": [{ "name": "", "nodeId": "ns=2;s=Application.GVL_TTM.OpMode", "datatypeName": "" }]
Expected behaviour
Should be: "addressSpaceItems": [{ "name": "MachineStatus", "nodeId": "ns=2;s=Application.GVL_TTM.OpMode", "datatypeName": "Int16" }]
Minimal reproduction of the problem with instructions Inject nod -> Listener -> Debug
Your Environment
Please tell us about your environment:
( ) I am using just the Node-RED package and got node-opcua installed with it
( ) I have installed node-opcua global from source (using git clone)
( X ) I have installed node-opcua as a global package (using npm i -g)
Device :
( ) macOS: v
( ) Linux: v
( X ) Windows: v 1803
( ) Raspbian: v
( ) Other:
Description of the connecting OPC UA system:
Node-RED version:
Node-RED version: v0.20.8
node-red-contrib-iiot-opcua version: ``
Node: (min. 8.x)
node --version
= v10.16.0