(x ) unexpected behaviour => please visit the Wiki before
Information
Current behaviour
In case of subscribed UA nodes (listening). If the connection to the OPC-UA Server lost the listening node will not subscribe the UA nodes again. You can trigger the inject node two times (sometime one times) to subscribe the UA nodes again.
Expected behaviour
Automatic subscribe after a connection lost.
Minimal reproduction of the problem with instructions
The behavior could reproductied in the all-in-one example.
Just monitor UA noden and de- reactivate the DEMO Server
Your Environment
Please tell us about your environment:
( x) 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)
( ) I have installed node-opcua as a global package (using npm i -g)
Problem
Information
Current behaviour
In case of subscribed UA nodes (listening). If the connection to the OPC-UA Server lost the listening node will not subscribe the UA nodes again. You can trigger the inject node two times (sometime one times) to subscribe the UA nodes again.
Expected behaviour
Automatic subscribe after a connection lost.
Minimal reproduction of the problem with instructions
The behavior could reproductied in the all-in-one example. Just monitor UA noden and de- reactivate the DEMO Server
Your Environment
Please tell us about your environment:
( x) 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)
( ) I have installed node-opcua as a global package (using npm i -g)
Device
Node-RED version: v1.0.2
node-red-contrib-iiot-opcua version: `` node-red-contrib-iiot-opcua 3.12.0
Node: (min. 8.x)
node --version= v10.16.3