-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection Closed after reboot of miniserver... #10
Comments
This is issue in new backend class node-lox-ws-api. |
Ok and thanks, i will waiting new version 0.4.2... |
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. |
Ok thanks a lot |
Updated in node-red-contrib-loxone 0.6.0 |
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 |
I will have a look into this when I finally manage to work on the other issues. |
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? |
Please check with 0.10.6, should be fixed. |
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.
The text was updated successfully, but these errors were encountered: