Node Red freezes because of failed attempts to connect to miniserver about node-red-contrib-loxone HOT 3 CLOSED

Thank you for this issue!

Delays between attempts to reconnect (for example 10 seconds?) in order to prevent Node Red becoming unresponsive.

I think this is handled by the underlying node-lox-ws-api and is not exposed, so I can't change that.

Disable connection if login credentials (in loxone-miniserver node) are missing.

I think this is the way to go... as far as I know it is not possible to connect to the miniserver without credentials anyway, or is it?

Exporting the credentials with a flow export ist not valid, as these are sensitive informations and could then be - without knowing - made public by exporting a flow. Node-red itself advises to store them separately: https://nodered.org/docs/creating-nodes/credentials

I will disable the connection when no credentials are given in a future release.

from node-red-contrib-loxone.

Thanks a lot!

Yes, as far as I know, it is not possible to connect to miniserver without credentials. So it is safe to make credentials obligatory and disable connection and throw an error ("red triangle" in Node Red) if credentials are missing.

from node-red-contrib-loxone.

Btw, the red triangle is provided by the node-red editor. It appears after an editor reload if the node-config is not complete.

from node-red-contrib-loxone.