11-13-2024
10:20
- last edited on
11-22-2024
07:39
by
MarreFitbit
11-13-2024
10:20
- last edited on
11-22-2024
07:39
by
MarreFitbit
I purchased fitbit charge 5 which was activated in October 2022 and was having battery issues in October 2023 and I was unable to use it and hence a replacement was provided in November 2023.
I had forgotten to discard my above original charge 5.
Since my replacement charge 5 is dead now (died as usual in October 2024 exactly in 1 year) ; I was trying to charge both my Original and Replacement Charge 5 one last time today before discarding them both.
I could see that my original charge 5 was able to connect via the fitbit app to some extent but couldn't pair it as it was giving an error stating that 'it cannot be paired and is blocked; as replacement was provided'. Refer attached image.
Now when I asked the fitbit/Google support to unblock my original charge 5 they are saying they can't unblock it as replacement was provided.
I don't understand why it cant be unblocked as I had paid my hard earned money to buy the product and I should have the ability to use them until they are alive and are able to work for even few mins, irrespective of their condition or battery life.
Atleast unblock my original charge 5 and allow me to try to connect it or offer a refund or replacement or repair it or offer some discount (I don't understand why no discounts are provided for affected Indian users). 😡😡😡😡
Badly need help on this as I am feeling cheated by Fitbit/Google.
Moderator Edit: Clarified subject
11-16-2024 13:37
11-16-2024 13:37
Have you tried pairing it again? I'm just looking at your time stamp from your message and noticed it was the same time I was having issues pairing my newly factory reset Pixel Watch 3 today (reset due to a different issue). I looked at downdetector.com around that time and realized there was an outage.
I tried again an hour later and was able to pair my device
Kristen | USA Cruising through the Lifestyle Forums
one cruise ship at a time!11-16-2024 20:00
11-16-2024 20:00
Thanks for replying. I tried it multiple times but it's confirmed by Fitbit that it's blocked by them which is not correct.