question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[eWeLink] WebSocket was closed. Reason [1006]

See original GitHub issue

Hey guys,

This seems to have just started happening recently.

Whenever Homebridge is sending a command to eWeLink devices, the request seems to always timeout. Below is what the log reads and it keeps repeating on and on without resolve:

[2018-4-18 08:19:52] [eWeLink] Setting power state to [on] for device [Hall and Porch CH 1]

WebSocketClient: error { '0':

   { Error: getaddrinfo ENOTFOUND us-long.coolkit.cc us-long.coolkit.cc:8080

    at errnoException (dns.js:50:10)

    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26)

     code: 'ENOTFOUND',

     errno: 'ENOTFOUND',

     syscall: 'getaddrinfo',

     hostname: 'us-long.coolkit.cc',

     host: 'us-long.coolkit.cc',

     port: '8080' } }

[2018-4-18 08:20:10] [eWeLink] WebSocket was closed. Reason [1006]

WebSocketClient: reconnecting...

My suspicion is that the individual Sonoff devices aren’t connected to the internet (perhaps a Wi-Fi issue?) which is leading to this message.

If anyone has any insights on how to fix this, that would be greatly appreciated!

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:20 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
MrTomAshcommented, Apr 22, 2018

Please try to update your config.json file as follow: "webSocketApi" : "eu-pconnect3.coolkit.cc"

1reaction
deng-sancommented, Nov 8, 2020

Hi,Ben

thank you for your mail.

I have settled the issue.

best regards

Z. S. Deng

8/11/2020 午後4:38、Ben notifications@github.comのメール:

@deng-san your config is for homebridge-ewelink-max, this plugin is homebridge-ewelink that’s why it isn’t working

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Getting the reason why websockets closed with close code 1006
Close Code 1006 is a special code that means the connection was closed abnormally (locally) by the browser implementation.
Read more >
Error 1006 abnormal close websocket? - Arduino Forum
Error 1006 means there's a low-level issue with websocket itself, or rather the code used to create the websocket. Without posting your code, ......
Read more >
Ewelink / Sonoff Binding - New binding without flashing
Websocket] - Websocket Closed, Status Code: 1006, Reason:Disconnected 2021-03-21 14:18:21.936 [ERROR] [onoff.internal.connections.
Read more >
Пользователь (freeman2014) - Sprut.AI
<br /><br />[eWeLink] WebSocket was closed. Reason [1006] <br />[eWeLink] WebSocketClient: reconnecting... <br />[eWeLink] Setting power state to [on] for ...
Read more >
[SOLVED] code server WebSocket close with status code 1006
The main reason is that the connection was closed abnormally (locally) by the browser implementation. It means that your browser cannot reach ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found