An unused connection still tries to connect

tzapu / node-red-contrib-blynk

Blynk app integration with Node Red

MIT License

17 stars 5 forks source link

An unused connection still tries to connect #14

Closed tvillingett closed 8 years ago

tvillingett commented 8 years ago

If I have defined a Blynk connection to a server that is not used, it still tries to connect: Connecting to TCP: 127.0.0.1 8441 Error ECONNREFUSED

And it gives messages in the log ( http://thethingbox.local/console.txt )

tvillingett commented 8 years ago

I dissapered when i erased the definition, I only used the cloud server at this moment.

tzapu commented 8 years ago

the server node gets initialised if it is added so that would be the expected behaviour as it is.

i am not sure if i can obtain the information that the server is used or not at the time of intialisation so i skip it ...

tvillingett commented 8 years ago

Ok, I guess that is the best behaviour, also since the server could be temporary out of reach because of network or other issues, it is good to continue to try to access it. As long as the error doesn't make any excessive cpu load or other bad things.