uncatchable errors

[AndyGR42]

At first, the flow works fine for me, thank you for your development.

But I cannot find a way to supress the error messages when the device is not reachable. The node spams the debug log every few seconds. I think these error messages are usefull for debugging, but unnecessary when you expect them. The connection can easily be taken from the node state.

Can you please give us the option to supress the connection errors at all or make them at least catchable?

Thank you

[Lanjelin]

Having the same issue.
Deleting all the nodes (from flows and config), and uninstalling eiscp through the palette menu doesn't remove the errors either..

24/03/2020, 16:30:13 Onkyo
msg : string[286]

"Error: ERROR (server_error) Server error on 192.168.1.18:60128 - Error: connect ETIMEDOUT 192.168.1.18:60128↵ 
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1137:16) {↵
 errno: 'ETIMEDOUT',↵
 code: 'ETIMEDOUT',↵ 
syscall: 'connect',↵ 
address: '192.168.1.18',↵
 port: 60128↵}"

Edit: Deleting/Uninstalling then rebooting the server seems to have done the trick.

[lukesav1]

I would like to bump this issue, it's causing my node red to crash now...