Error codes during pairing of a device

You are here:

Sometimes you experience issues while pairing. Most times they end with an error code. Most people don’t notice these important error codes and just find themselves stuck in pairing their devices. Paying attention to the error codes might help you finding a remedy for the issue you experience.

Information

This article is mainly a copy/paste of the “Crack the codes of pairing failure” article of eWeLink. We have added some community experiences to it.

In general when pairing fails it is best to try pairing with the Quick Pairing mode. The error codes in this mode generally tells the most about the possible cause. Although the codes in other pairing modes can also still be usefull.

Example of error code

Here is an example of an error code. The error code itself is displayed at the upper right corner. In this case the error code is 401 during Compatible Pairing.

Error code
General troubleshooting steps

Error codes

Below follows the known possible error codes categorized by the pairing methods and what you could try to do about the error.

Quick Pairing

Error codes generated during Quick Pairing generally follows the format “61xx”.

6101, 6106 and 6107: Issues related to the WiFi connection or router

In general this means the device couldn’t get a valid IP address from the router.

Troubleshooting steps:

  • Check whether DHCP is enabled on your router.
  • Check whether you have entered the correct WiFi password. If it was automatically filled in: empty it and fill it in manually. Pay attention to uppercase letters, lowercase letters, special characters, numbers and especially automatically added spaces by some virtual keyboards!
  • Temporarily disable 5 GHz Wifi (not to confuse with 5G mobile internet) during pairing on either your phone or router / accesspoint. The latter one is mostly the most easy one. Refer to your router’s / accesspoints manual to see how you can disable 5 GHz on it. You need to be connected to only a 2.4 GHz accesspoint.
  • Temporarily disable mobile data and only enable WiFi. Was this already the case? Then leave mobile data and WiFi enabled both at the same time.
  • Check whether your router has a hardware limitation. Some (mostly cheaper) routers can’t handle enough devices at the same time. E.g. max 32 concurrent connections on WiFi. Or 64 devices in total wired and wireless. Mostly the somebit more expensive ones don’t have this hardware limitation.
  • Test with another accesspoint connected to your router and/or mobile hotspot on a second phone to be more certain whether your router is the issue.

6102, 6103 and 6104: Communication error

In general this means the data didn’t come trough well. On the communities we haven’t seen this error much and thus we have no community driven information on this.

What eWeLink says about these error codes:

Failed to receive the required data or device is not responding in the process of searching for, registering, or connecting the device. The solution to this type of error is to try again. If the pairing fails again, please try again with a personal mobile hotspot to test the WiFi functionality of the device. 

Source: eWeLink “Crack the codes of pairing failure” article

6105: Timeout

A timeout mainly can have the same causes as errors 6101, 6106 and 6107. Otherwise there have been to much time between initiating the pairing on the device itself and initiating the pairing on the ewelink app. A device in pairing mode waits for 3 minutes to receive a signal of your phone to configure its settings.

6108: Unknown error

This error code should rarely show up. If it does show up it should be reported to eWeLink with the in-app feedback feature.

Compatible Pairing

This pairing mode is intended to manually set the WiFi credentials in the device. This pairing mode sets up a local hotspot at the device. The advantage of this is that you don’t have to mess with disabling 5 GHz on router / accesspoint. The disadvantage is that it doesn’t provide you much feedback about a failed connection due incorrect WiFi credentials. So it might appear that you succeeded in pairing but the device remains offline all the time due incorrect WiFi credentials.

Error codes during Compatible Pairing mainly have the format “62xx”.

6201: Device hotspot failure

The app could not find the SSID of the device’s hotspot. Power off the device, put it in Compatible Pairing mode and try again.

6202, 6203 and 6204: Communication error

Somewhere in the connection the data didn’t came through well. It might be a bad connection, but a non-responding device is also possible. Retry the pairing.

6205: Failed to switch to home WiFI

The app couldn’t switch your phone back to your home WiFi. This can be caused by missing app permissions for the eWeLink app. Check the app permission. Especially the one for “location”. Also reboot your phone after configuring the app permissions. If this doesn’t help you can try to connect to your home WiFi in the last stage of the pairing right before the moment of the error.

6206 and 6207: Server error

This error code can not be fixed by yourself. This means the app failed to register your device on the eWeLink server or there was no response from the eWeLink server. Contact eWeLink with the in-app feedback feature and wait for them to confirm the recovery time.

6208: Timeout

A timeout mainly can have the same causes as Quick Pairing errors 6101, 6106 and 6107. Otherwise there have been to much time between initiating the pairing on the device itself and initiating the pairing on the ewelink app. A device in pairing mode waits for 3 minutes to receive a signal of your phone to configure its settings.

QR-code Pairing

The technique of this pairing mode is very like Compatible Pairing, but offers you the ability to automatically connect to the correct hotspot without searching for it. This is why it has the same format of error codes: “62xx”.

Again the advantage of this hotspot pairing mode is that you don’t have to mess with disabling 5 GHz on router / accesspoint. And again the disadvantage is that it doesn’t provide you much feedback about a failed connection due incorrect WiFi credentials. So it might appear that you succeeded in pairing but the device remains offline all the time due incorrect WiFi credentials.

6210, 6211 and 6212: Communication error

Somewhere in the connection the data didn’t came through well. It might be a bad connection, but a non-responding device is also possible. Retry the pairing.

6213: Failed to switch to home WiFI

The app couldn’t switch your phone back to your home WiFi. This can be caused by missing app permissions for the eWeLink app. Check the app permission. Especially the one for “location”. Also reboot your phone after configuring the app permissions. If this doesn’t help you can try to connect to your home WiFi in the last stage of the pairing right before the moment of the error.

6214 and 6215: Server error

This error code can not be fixed by yourself. This means the app failed to register your device on the eWeLink server or there was no response from the eWeLink server. Contact eWeLink with the in-app feedback feature and wait for them to confirm the recovery time.

6217: Device hotspot failure

The app could not find the SSID of the device’s hotspot. Power off the device, put it in Compatible Pairing mode and try again.

Bluetooth pairing

Some devices are paired by a bluetooth connection. A great advantage of this is that the WiFI credentials are directly placed at the device without requiring a WiFi connection in advance.

Error codes during this pairing method have the “63xx” format.

eWeLink didn’t share to much details on their “Crack the codes of pairing failure” article. But the main advise is to try the bluetooth pairing again.

6301: Scanning failed

Could not scan for nearby bluetooth devices. Did you enable bluetooth on your phone?

6302: Failed to connect to bluetooth

The eWeLink app failed to connect to the Bluetooth part of the device. Try to place your phone more near the device.

6303: Failed to send WiFI credentials

The eWeLink app failed to send the WiFi credentials to the device over the bleutooth connection. Maybe an unstable bleutooth connection. You might want to move your phone more near the device.

6304: Device failed to connect to WiFi

Refer to Quick Pairing errors 6101, 6106 and 6107.

6305: Could not retrieve device information

The eWeLink was unable to retrieve device information.

6306: Failed to register the device

Could be an eWeLink server issue. Best is to wait. Otherwise create an in-app feedback to eWeLink and wait for them to confirm the recovery time.

6307: Failed to send network information to device

The eWeLink app was unable to send your WiFi credentials to the device.

6308: Timeout

There was no communication with the device for to long. Can have many possible causes. Most common will be a slow working router / accesspoint or non-responding device.

6310 and 6311: Invalid device. Authorization failed. 

Unknown error to us.

6309, 6312, 6313 and 6314: Cannot connect the Bluetooth device

Quite unknown error to us. Probably unstable bluetooth connection. Try moving your phone closer to the device.

6315, 6316, 6317, 6318, 6319 and 6320: Device can’t connect to home WiFi

Refer to Quick Pairing errors 6101, 6106 and 6107. The device was unable to obtain an IP address. Mostly due incorrect WiFi credentials.

General errors

General errors can occur in any pairing mode and contain 3 digits. Mostly in the “4xx” or “5xx” format.

400 and 403: App error

This is an error with the eWeLink app itself. Please contact eWeLink with the in-app feedback feature.

401 and 402: Login expired

Somehow your login has expired. Maybe the server registered a double login by accident and logged you out automatically. Please login again. If the app says you are already logged in then try loggin out from the eWeLink and log back in.

406 and 407: Account error

This can have 2 causes:

  • The device is not allowed to be handled by this account.
  • The device belongs to another account.

In both cases you will need to contact eWeLink with the in-app feedback. Provide them the Device ID (if you can find it, mostly at the back of the device or on the box it came in) and your eWeLink account (if you are the owner of the device).

500: Server error

Mostly a temporary error. Can be an eWeLink server outage. Try again in a few hours. If the problem remains then contact eWeLink by the in-app feedback feature or if that fails email them at .

Next > How do I reset my device?

In case you think there is an error in a Knowledge Base article, there is something missing or when you have an idea for a new Knowledge Base article please contact us on our Contact form!

If you refer to an existing Knowledge Base article please include the link to the article involved!

Table of Contents