search

codmpm / node-red-contrib-loxone

Connect the Loxone Miniserver to node-red via the Websocket API
MIT License
74 stars 24 forks source link

Connection Closed after reboot of miniserver... #10

Closed SteeveK closed 4 years ago

SteeveK commented 6 years ago

Hello (i'm french...),

Great job !!!!! I've a problem with CONTROL IN : when i rebooted my miniser, the CONTROLS IN are no reconnected, they are in yellow with CONNECTION CLOSED. I've to update the miniserver in node-red to get again CONNECTED... Could you please help me and excuse me for my horrible english :-)

Thanks.

alladdin commented 6 years ago

This is issue in new backend class node-lox-ws-api. I was fixed it in new version (0.4.2) of that library.

SteeveK commented 6 years ago

Ok and thanks, i will waiting new version 0.4.2...

codmpm commented 6 years ago

I will include the new node-lox-ws-api 0.4.2 into node-red-contrib-loxone in the next days. Did not had any time and have to build a better testing environment.

SteeveK commented 6 years ago

Ok thanks a lot

codmpm commented 6 years ago

Updated in node-red-contrib-loxone 0.6.0

mapchen commented 4 years ago

hello,

can it be possible that this error came back? After power outages I assume my raspberry comes back faster then the miniserver. That means Loxone Nodes do not have the miniserver structure and are now working. After a restart of the flows everything works fine again

codmpm commented 4 years ago

I will have a look into this when I finally manage to work on the other issues.

gbrehmer commented 4 years ago

I have similar problems. During FW-Updates of miniserver the miniserver is several minutes not available. node-red tries to reconnect but it seems that reconnect attempts have some limits set?! Is it possible to add some configuration to increase such limits or try counts?

codmpm commented 4 years ago

Please check with 0.10.6, should be fixed.