Skip to content

Version 3 breaks error handling in live connect

Summary

writing to a opcua server that is not available used do cause this log message: [eta_utility.connectors.live: ERROR] Host timeout: opc.tcp://192.168.116.43:4840 but didnt raise

since version 3 this action raises with a asyncua timeout error

also these error messages arise:

close_session but connection wasn't established close_secure_channel was called but connection is closed

that are not desirable

Explain your context

(Explain what you did.)

What is the expected correct behavior? What was your goal?

(What you should see instead.)

What is the current bug behavior?

(What actually happens.)

Was there an error message?

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Steps to reproduce

(How one can reproduce the issue - this is very important)

Edited by A.Clement