Apple Watch pairing error

[JonathanB]

Hi everyone,

We've moved everything relating to Apple Watch pairing issues to this new conversation and will be providing all future updates as edits to this post, so that you won't need to go searching through the comments for these.

I appreciate these pairing errors must be very frustrating, especially for those of you that have been running into issues for several weeks now. Technical specialists are continuing to look into this, however based on what they've seen so far, this does not seem to be one overall fault that we can apply a blanket fix to.

With this in mind, please make sure you have followed the advice on the private message we've sent to each of you, this will ensure that your individual case has been escalated. We've originally sent these messages out a couple of weeks ago, so I'll double check that everyone that has commented has received these. You can find your community messages by clicking on your avatar in the top right of any page, then on "Messages".

Finally, please ensure you are following the Community House Rules when posting on the community, particularly points 8 and 13.

The private message mentioned above will put you in touch with a team that you can raise a complaint with should you wish to do so, any comments that share details of individual Three employees will be removed from the community.

JonathanB

---

**Update 26/10/2022**

Hi everyone,

We really appreciate your patience whilst we've been working on this issue. I can't imagine how frustrating it is to not be able to take full advantage of your Apple watches.

As I mentioned last week above, the errors do not seem to be one overall fault that can be fixed immediately for everyone. We do need a specialist team to do some work in the background on your accounts. With this in mind, I'd advise the following:

• Make sure you've taken any action we've recommended on private messages to your community account. If you're experiencing these issues and we don't already know, please reply on this post so we can reach out.
• Do not repeatedly attempt unpairing and pairing, this may be interfering with the work done in the background. Please wait for a Three representative to contact you and advise before you unpair and pair again.

We've seen some great progress towards getting this sorted in the last few days, I'm hopeful that it won't be too much longer till this issue is fully resolved for everyone.

JonathanB

---

**Update 17/11/2022**

 Hi everyone,

We’re really sorry that there’s been a considerable delay between updates on the errors with Apple watch pairing. As we’ve mentioned previously there is more than one error involved and specialist teams are working hard to address the root causes of these.

I assure you that all comments about this issue are read, and all feedback given is being escalated on a daily basis.

Whilst we’re working on this, we’d be grateful if you can do the following:

• If you’re new to this thread, please either private message me, or add a reply, and I’ll direct you to a team that can help further.
• If I’ve already sent you this information, please ensure you have spoken to that team.
• Please only unpair and re-pair your watch if directed to by one of our support teams as part of the troubleshooting and investigation of your issue.

I’ll provide another update soon.

Thanks,
JonathanB

---

**Update 02/12/2022**

Hi everyone,

Thanks for your continued patience. We’ve seen some great progress towards resolving these issues since the last update. As I’ve mentioned previously there is more than one error involved, and for many of you, your bill cycle will also affect when you can successfully re-pair the service.

Here’s some general steps that should help with common scenarios we’re seeing.

• Ensure that you’ve registered for My3, without a registered online account and password set, the pairing will fail.
• There are some instances where special characters at the start of My3 passwords have resulted in an error. We recommend that you have a strong password that is a combination of upper and lower case letters, numbers, and special characters but avoid beginning the password with characters like /!”£$|\. My3 supports these, but it seems to be causing an issue when this info is passed onto the smartwatch pairing system.
• If you’ve changed your priceplan, upgraded, or are instructed to wait for your bill cycle to complete, you should wait till the day after your new bill cycle starts to attempt pairing. So for example, if your allowances refresh on the 1st, wait till the 2nd.
• Although individual smartwatches can be unpaired from your account, cancelling or removing the add on completely will delay being able to reinstate the service till the following bill cycle.
• As mentioned before, don’t repeatedly unpair and re-pair, the failed requests may cause further issues on your account that delay this being solved.
• I’m continuing to regularly check for anyone new on the thread, just send a reply or private message me, and I’ll link you in with a support team that can help get your specific error looked into and make sure you get the best advice.

Thanks,
JonathanB

---

**Update 11/01/2023**

Hi Everyone,

As well as the steps on the last update, we're finding it helps to clear your temporary data from your iPhone before attempting pairing.

You can do this in Settings, Safari, Clear History & Website Data.

In case anyone is having trouble finding their private messages, click on your avatar image in the top right of any community page, then "Messages". If you've posted on this thread, then you should have a message waiting from me with a link to a support team that will help.

Thanks,
JonathanB

[hamid786uk]

I wouldn’t hold your breathe. They said the same to me, and most of this forum are still experiencing the same issue - Sadly!

[hamid786uk]

Not quite, i have now received the same error again - “E53305 - You already had a paired device.”

[hamid786uk]

I’m getting this error message today

502 Bad Gateway

---

Microsoft-Azure-Application-Gateway/v2

[Ashasg03]

Hopefully it means they finally found the issue and are fixing it 

[joodood]

Same!

[hamid786uk]

only adds to the misery when no one from Three technical support or on this community forum show any signs of concern. 

you would think this would have been escalated with all efforts to resolve this issue for the customers that have been reporting an issue for the past four weeks.

[Hazbean]

I've been having the same issues. I upgraded my Apple Watch when the Series 8 came out almost four weeks ago. I was using an older model of Apple Watch on my account. I removed my old watch, but got the error E53305 "You already had a paired device" when trying to add my new watch. I thought this should be an easy fix to have old watch removed and new one added. It was not easy at all.

Over the last four weeks I have spent hours and hours on either phone calls with people who don't know how to do much more than suggest I restart, reset, or get Apple to tell me it works totally fine. I've had the add-on 'Smartwach Pairing 1m' added and removed to my account half a dozen times to no avail.

The only thing that seemed to "help" matters was having my bill cycle go from one month to the next. This got rid of the E53305 error, and even let me register my watch to my account. Although five days later and a couple of attempts at removing and adding my smartwatch add-on has not helped anything, as it's still stuck at 'Activating'. Now all the webchat team can tell me is there is no issue, and that it must be a fault with my watch. 

[danbrown83]

I've had exactly the same issues other than I didn't previously have an Apple Watch. They need to sort this out. I have a £850 watch and can't use one of it's main features. 

[hamid786uk]

I have myself experienced the same issue as everyone else on this forum.  I have spent endless hours on the call to Three technical support with the usual script of unpair/pair, remove addon/apply addon & reset.  I have been promised 2 callbacks neither have come to fruition.  

Surely, this should be in the papers by now or on Social Media, the customer experience is horrendous.

Such a huge company, making £££’s in profit, surely this should be fixed within days and not weeks and months!

[Boyle]

The reality is, nobody knows what is wrong. I get an error message saying 'there is an error' and that's it. Nobody in the company seems to have any idea what it is or why it's happening, let alone a way to resolve it.