-
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
Reconnect to Miniserver fails sometimes after new Config File is stored to Miniserver #73
Comments
I can confirm this behavior for my setup: Node Red Version V 2.2.2 running in a container from nodered/node-red
Keepalive: 15 seconds |
I have the same issue. Is it a problem of this node or of the Node Red Version: 3.0.2
|
Is there any progress with this issue, please? Or any chance to use keepalive/online node and manually call reconnect? |
@ludekvodicka Sorry, currently not. If someone wants, feel free to do a pull request. |
Any progress please? Unfortunately the issue still occurs time to time leading to complete disconnect of my zigbee lights from loxone server. Is there any way how to manually trigger the reconnection via some REST API for example? |
Sometimes (every 5 to 10 times) Loxone Node does not reconnect to Miniserver after Miniserver restart due to deply of config file to Miniserver.
In the Node Red log File, the following can be found:
`
Websocket Connection closed: 1000 normally closed
11 Jun 15:20:22 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: normally closed (1000)
11 Jun 15:20:22 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:22 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:22 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:22 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:22 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:22 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
...... some 100 messages ....
11 Jun 15:20:40 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:40 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:40 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:40 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:40 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:40 - [info] [loxone-miniserver:bda880d5.2d4e98] connection closed: reconnecting
11 Jun 15:20:40 - [info] [loxone-miniserver:bda880d5.2d4e98] Miniserver connected (192.168.178.230:80) using Token-Enc
11 Jun 15:20:40 - [info] [loxone-miniserver:bda880d5.2d4e98] got structure file 2022-06-11 15:20:19
`
Then nothing more happens. No more log and still no connection.
It locks like reconnect requests happens much too fast, without any delay between the reconnects.
Only restart of Node Red solves the problem (sometimes also a redeploy of the flow helps).
Tested on:
Raspberry 4
Node Red Version V 2.2.2
Loxone Node Version 0.10.12
Miniserver Gen 2
The text was updated successfully, but these errors were encountered: