Node-RED: OpcUa Client node

[tad]

Dear Armin,

Thank you very much for your information.
Finally, I execute the following commands from the Node-RED console, and then the OpcUc client node was able to communicate with a server in S7-1500 without any error.

===========
root@NTB827EBB5D102:~/.node-red/node_modules/node-opcua-client# mkdir certificates
root@NTB827EBB5D102:~/.config/node-opcua-default-nodejs/PKI/own/private# cp private_key.pem /root/.node-red/node_modules/node-opcua-client/certificates/client_selfsigned_cert_2048.pem.csr
root@NTB827EBB5D102:~/.node-red/node_modules/node-opcua-client/certificates# mkdir PKI && cd PKI
root@NTB827EBB5D102:~/.node-red/node_modules/node-opcua-client/certificates/PKI# mkdir own && cd own
root@NTB827EBB5D102:~/.node-red/node_modules/node-opcua-client/certificates/PKI/own# mkdir private && cd private
root@NTB827EBB5D102:~/.node-red/node_modules/node-opcua-client/certificates/PKI/own/private# cp /root/.config/node-opcua-default-nodejs/PKI/own/private/private_key.pem .
===========

And, I couldn't update the OpcUa Client node to the newest version 0.2.222 or delete the node.
After the restart of netPI, version 0.2.64 is always active.

I hope 'hilschernetpi/netpi-nodered' always includes nodes which are working properly.
Best regards,