Plugin does not connect to HA after reboot

[jncanches]

Describe the bug
On an Hassbian Raspberry Pi 3, Home assistant and Node red configured to launch at startup, just after the raspberry boot, NodeRed can't connect to Home assistant.
Redeploying nodes in NodeRed or restart once Home assistant, solves the issue and NodeRed connects well to Home-Assistant

Expected behavior
NodeRed must connect to Home Assistant after a boot without restarting HA or NR.

Environment (please complete the following information):

• Node Red Version: 0.19
• NR Home Assistant websocket Plugin Version: 0.1.2
• Is Node Red running in Docker: no

Other (please complete the following information):

• Have you searched previous issues for duplicates?: yes
• Did you attempt to reproduce the issue in the dev docker environment, if so what were results (See README.md): no

By the way, very good plugin ! Keep this way !

Thank you

[Swamp-Ig]

I also have this issue, running in a docker container on a QNAP NAS FWIW.

24 Oct 21:28:09 - [error] [server:Home Assistant] Error: connect ECONNREFUSED 172.31.224.65:8123                                                         
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)      

It works fine once HA has booted up properly, but there doesn't seem to be an attempt to retry the connection.

[zachowj]

Yes, it's working as coded but probably not the best way to handle a refused connection. Currently, if it fails the first connection attempt it does spam the server with connection attempts.

In the process of refactoring the connection process.

[jncanches]

Wonderful zachowj.

Does it mean that the next release will try to connect again even after a first refused connection ?

Thank you very much !

[zachowj]

#13

[jncanches]

Thank you!
Do you plan to make a 0.1.3 release soon ?

[zachowj]

it's out