MAX! Binding improved discovery of the Cube

fix for error on first message when no config is provided.

Signed-off-by: Marcel Verpaalen <marcel@verpaalen.com>
I agree, for the catch blocks in the finally block the logging handling looks fine. If an exception occurs while the connection is being closed, should be ok to log it on debug as a normal usage of the binding is probably possible.
I was rather referencing to lines 72 - 75 as well as 114-117 in my comment above. If an error occurs during the communication with the MAX!Cube Gateway, I'd like to see it in a noticable way (e.g. WARN or ERROR) in the log as a user.