Reading ExtenstionObject Timesout Node Red

[0rion447]

Prior to release 0.2.339 reading extension object passed to the client node from an item node of format: Item : ns=4;s=|var|PLC.Application.PROGRAM.myExtObj type : ExtensionObject Gave no errors.

Now it times out node red and forces a restart. I believe the issue lies with the [email protected] package. Reverting node-opcua to version 2.131.0 and node-red-contrib-opcua to 0.2.332 may solve this for me but I'm not sure just yet. Will update if i am able to get it to work.

[0rion447]

version 2.131.0 does not work but version 2.130.0 does

[Strunck]

Facing the similar problem, when reading an "ExtensionObjectArray". After the OpcUA-Client-node activates, node-red is not responding anymore. I tried to do npm install [email protected]. So far no luck.

It is running in a podman container with Alpine Linux v3.21, Node.js v22.13.1, [email protected]

[0rion447]

@Strunck heres my package.json Im running [email protected] and Node.js v18.19.0 `{

"name": "node-red-project", 
"description": "A Node-RED Project", 
"version": "0.0.1", 
"private": true, 
"dependencies": { 
    "node-red-contrib-opcua": "0.2.332", 
   “flowfuse/node-red-dashboard":”1.22.0” 
}, 
"overrides": { 
    "node-red-contrib-opcua": { 
        "node-opcua": "2.121.0" 
    } 
} 

} `

and i install with npm i --omit=optional --maxsockets 1 --loglevel verbose --noproxy registry.npmjs.org after editng my package.json, now I edit my package.json in the /data/ directory of my docker container. since thats where my node-red pulls its modules from. at first i struggled with versioning since i was installing modules into the wrong npm dir and not the one that node-red was using. Good luck.