Locked out of my Versa

[LucianAdrian]

I am unable to use my Versa and I did not find a solution so far.

What happened?

Having my Versa paired with FitbitPay, with lock code enabled I unpaired it from the phone (due to phone factory reset) and left it unpaired. At the same time, my child (3 years old) started playing on the screen, entered the PIN code wrong and locked the Versa. The Versa is now asking for phone unlock, that is not possible as it is not paired. I'm using Android phone, currently running Android 10. 

Steps to reproduce:

1. Enable PIN lock on Versa while paired with phone

2. Unpair from phone 

3. Enter PIN on Versa enough times to make it locked and ask for phone unlock

4. Attempt to pair with phone and see that the pair code is not shown on device

What I tried?

- Pair device with phone but pair code is not shown on device to enter on phone 

- Hard reset by holding three buttons on Versa and then releasing one ...

Are there any solutions? 

[JuanJoFitbit]

@LucianAdrian, welcome to our Fitbit Community. I'm sorry to hear that your Fitbit Versa is locked. By the way, thank you for troubleshooting this issue before contacting our forums.

I'd like you to try the steps that shared my friend Alvaro in this post. These are the steps to unlock your Versa by using your phone. This should resolve the issue.

Keep me posted on the outcome! 😀

[phabfish]

This simply does not work. If the OP's experience is anything like mine, the Fitbit will be locked with no option to unlock. I have tried everything I can find to try but all to no avail. I have contacted this community, twitter and your email but all approaches have been ignored. I think that repeatedly directing locked out customers to a post that offers nothing to alleviate a very frustrating situation is terrible for the reputation of Fitbit.

[LucianAdrian]

Hello,

I have been to that post before posting here. 

As specified, the Versa is not paired with the phone, so the device is not listed in the App.

The indicated solution does not fit my problem.

Have you been able to reproduce the issue I describe on your side and can someone please come up with a decent workaround? 

Lucian

[LucianAdrian]

I subscribe to this comment.

Before posting to this community, I did look for solutions on forums, contacted support via Twitter DM and tried a couple of possible solutions. 

The options provided by support did not work, and I believe they did not even try to replicate my exact scenario, as all solutions point to a scenario where the device is paired with the phone (and that is not my case).