search

deconz-community / node-red-contrib-deconz

Node-Red Nodes for deCONZ connectivity.
GNU General Public License v3.0
81 stars 16 forks source link

WebSocket disconnected: 1000 #165

Closed arozhankov closed 2 years ago

arozhankov commented 2 years ago

Current Behavior

After last update at Deploy I have this error: WebSocket disconnected: 1000 but all works fine .....

Previously it was: https://github.com/deconz-community/node-red-contrib-deconz/issues/146

Environment

TheNON75 commented 2 years ago

Hi @arozhankov Does this happen with full deploy only or in other cases too?

arozhankov commented 2 years ago

Hi @arozhankov Does this happen with full deploy only or in other cases too?

with full deploy

Zehir commented 2 years ago

This mean that at some point the connexion between node-red plugin and deconz websocket was lost. The connexion came back in second so that why it's working fine. The last error is displayed on the node until a new event is passing throught the node. I need to change this beavior but I don't know how yet. Maybe I will remove server error of the nodes and put them in a new node a in a mode of the event node.

TheNON75 commented 2 years ago

I believe it is perfectly fine in case of a "full deploy" or "restart nodes"

;)

Zehir commented 2 years ago

I believe it is perfectly fine in case of a "full deploy" or "restart nodes"

;)

Yes when you deploy the websocket is shutdown so it's trigger the error event but this should be ignored and not sent to the user

TheNON75 commented 2 years ago

I believe it is perfectly fine in case of a "full deploy" or "restart nodes"

;)

Yes when you deploy the websocket is shutdown so it's trigger the error event but this should be ignored and not sent to the user

You are a perfectionist, I like it 😉