Ewelink Error: getaddrinfo ENOTFOUND as-pconnect4.coolkit.cc

What issue do you have? Please be as thorough and explicit as possible.

My homebridge server will be stopped and when I check the log, it says Error: getaddrinfo ENOTFOUND as-pconnect4.coolkit.cc at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)

Details of your setup.

• Do you use (1) Homebridge (+ config-ui), (2) Homebridge (CLI) or (3) HOOBS? I use HOOBS

• Which version of Homebridge/HOOBS do you have? HOOBS 3.3.5

• Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known. Raspberry Pi

• Which version of this plugin (homebridge-ewelink) do you have? Has the issue started since upgrading from a previous version? 5.5.1. Yes I also had the same issue on pervious version so I updated it to 5.5.1 hoping it will solve the issue.

• Which eWeLink devices do you have that are causing issues? Please include product models if applicable. I don’t believe it is specific to one model…

Please paste any relevant logs below.

Error: getaddrinfo ENOTFOUND as-pconnect4.coolkit.cc
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)

[bwp91]

I have just released v5.6.0 (same as beta -7) hopefully (and it looks like) this will sort everything!

[bwp91]

@estilles are you able to try the beta I have just pushed, v5.5.2-6. Make sure it’s the -6 version.

Some background information:

Once the plugin has logged into eWeLink, they provide a web address for the web socket connection. There are a range of addresses they provide for the Asia server, as-pconnect1.coolkit.cc, as-pconnect2.coolkit.cc, as-pconnect3.coolkit.cc, as-pconnect4.coolkit.cc, etc… The address provided at random and can change each hour that the plugin refreshes the connection.

It seems that the address ‘as-pconnect4.coolkit.cc’, although provided by eWeLink themselves, is causing these ENOTFOUND errors.

There is no way for the plugin to decide which address is provided by eWeLink, so the fix needs to be a ‘workaround’. It seems I need to ‘verify’ the address provided by ewelink, something I assumed would never need doing…

So in this beta, the plugin will now try and connect to the provided address, and if after 10 seconds it has failed, the plugin will try and request a different address to use. If this ‘as-pconnect4.coolkit.cc’ is provided again, the same will happen after 10 seconds, the plugin will request a new address. This will loop until a valid address has been given.

I hope this makes sense and the beta should

1. stop homebridge from crashing in this particular ‘as-pconnect4.coolkit.cc’ case
2. keep requesting a new address until the one provided works correctly

If you can get the beta installed and running for a while, let me know if you continue to get any errors!