Common Errors

Here are some of the common errors you may experience with the plugin and how to resolve.

HTTP Login Error

Entries in the log may be displayed as:

• ***** Disabling plugin. *****

  ***** user does not exists [10003]. *****

This error can appear when entering a username for a eWeLink account that does not exist. This error is specific to the username being incorrect - an incorrect password will show a different error.

In a small number of circumstances, users based in Australia and New Zealand may receive this error even when the username is correct.

To resolve:

• Verify that you are using the correct username (email or phone number) that is associated with your eWeLink account
• If you are receiving this error and you are based in Australia or New Zealand, use the optional settings part of the plugin settings to set 'HTTP Host' to us-apia.coolkit.cc the 'Country Code' to e.g. +61 or +64

WS Timeout/Slow Error

Entries in the log may be displayed as:

• [Device] device update failed as WebSocket request was rejected by timeout (5000 ms)
• The write handler for the characteristic '%' on the accessory '%' was slow to respond!
• The write handler for the characteristic '%' on the accessory '%' didn't respond at all!

This error can appear when controlling an accessory through HomeKit and the plugin doesn't receive a 'reply' from eWeLink confirming neither success nor error. In many cases this is due to using a 'shared' eWeLink account.

To resolve:

• Confirm that you are using your main eWeLink account for both the eWeLink app and this plugin

WS 504 Error

Entries in the log may be displayed as:

• [Device] device update failed as request timeout [504] at connectionWS.sendUpdate...

This error can appear when controlling an accessory but the device is unreachable by eWeLink.

To resolve:

• Confirm that the device is powered on and connected to your local network
• Confirm that the device doesn't appear as offline in the eWeLink app

WS 406 Error

Entries in the log may be displayed as:

• WS login failed [406] see http://bit.ly/hb-ewelink-errors
• WS login failed as Unknown WS parameters received { "error": 406... }
• WS unknown command received { "error": 406... }

This is an authentication issue which can happen in a number of circumstances, for example:

• Running multiple instances of Homebridge with the same eWeLink credentials
• Logging into the eWeLink app on another phone with your credentials

To resolve:

• Often simply restarting the plugin can help
• Make sure you only have one instance of Homebridge running with the eWeLink plugin configured
• Try logging out of the eWeLink app on all mobile devices, then logging into the app on your main phone and restarting Homebridge