deconz-community / node-red-contrib-deconz

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

deCONZ error WebSocket disconnected: 1006 - #225

Closed Mikee1234K closed 1 year ago

Mikee1234K commented 1 year ago

Current Behavior

I had to re-authorize my deconz nodes, which seemed to worked ok initially. The node says connected, but a second later I get a red dot under it with 1006. In the debug window it shows

"WebSocket disconnected: 1006 - In the Node Red cmd window I see this:

16 Jun 11:06:36 - [error] [deconz-server:Phoscon-GW] WebSocket error: Error: connect ECONNREFUSED 192.168.x.x:8080 16 Jun 11:06:36 - [warn] [deconz-server:Phoscon-GW] WebSocket disconnected: 1006 -

Expected Behavior

No response

Steps To Reproduce

No response

Example flow

paste your flow here

Environment

Zehir commented 1 year ago

Can you check if the websocket port is valid ? Try pressing the auto configure magick button

Mikee1234K commented 1 year ago

I pressed the auto config, did not see any errors. It pulls in all the devices so I assumed it was ok

Zehir commented 1 year ago

There is 2 configuration, the rest api for the data and the websocket for the events. The 1006 errors say that the websocket configuration is wrong

Mikee1234K commented 1 year ago

Ok that makes sense. Where and how do I see / change the websocket ?

Zehir commented 1 year ago

You can see the websocket port in the /config endpoint you wan use the api node or phoscon to get it

Mikee1234K commented 1 year ago

Ok I found it. Thanks, seems to be working now. Appreciate your help

Zehir commented 1 year ago

No problem