If device is turned off, there is not way to attempts to connect top errors (even if modules are disabled)

[antonio1000homens]

Is there a way the code can check if the modules are enabled or not?

Even with modules disabled it tries to connect (and fail to the device)

Error: ERROR (server_error) Server error on 192.168.1.75:60128 - Error: connect EHOSTUNREACH 192.168.1.75:60128
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1128:14) {
errno: 'EHOSTUNREACH',
code: 'EHOSTUNREACH',
syscall: 'connect',
address: '192.168.1.75',
port: 60128
}

[djiwondee]

I would also love to have this error catched since I'm switch the power supply of my entire home entertainment equipment completely off at night for power consumption saving. This error is causing an error message each 8 to 10 sec in the node-red-log then.

According to node-red documentation a catch-node in node-red is not able to handle errors caused by the configuration nodes in a simple way. As far as I know, to allow error handling by a catch node, the call of node.error() must also provide the message that triggered the error. E. g. node.error("Custom Error Message", msg). I haven't looked into the code base here to check whether this would be simple to add.