TheeeEnding

Thanks a lot @mikakaraila ! Just fyi, I've done a few tests in the meantime and was able to nail down the problem to the code line that I mentioned...

I tested the new version overnight in order to see the reconnect/keepAlive after a longer downtime and unfortunately the problem is not fixed! The client did not reconnect successfully after...

Thanks a lot!!

@regrog Hi, how would that help? It seems that the solution from https://github.com/mikakaraila/node-red-contrib-opcua/issues/638 only works if the node throws an BadConnection Error. In this example the node does not show...

I've tested with the 0.2.327 and it still doesnt throw an error. The change from v0.2.327 to 0.2.328 only affects the opcua server node - so I didnt test it

Hey, can we expect any update on this? It is still an ongoing problem.... Thank you!

Thanks for the fast answer! That is a good point, unfortunately it doesn't seem to matter what I set the interval to... I even set it to 1000ms and increased...

Hi Mika, I tested the connection with the modified settings as in node-red (MaxKeepAliveCount / MaxLifetimeCount / MaxNotificiationsPerPublish / Priority) and it seems that the problem cannot be traced back...

I can try that however I'm unsure how this could reduce the cpu load on the opcua server of the machine? It would be great if you could explain that...

Alright thanks, I will test it asap and give feedback