12-12-2021 07:07
12-12-2021 07:07
Good day all,
I did the initial wear your sense for so many days to get a readiness score and received a score for just over three weeks. Then on the day that my Premium membership renewed I stopped getting a score and the tile just says “Get Started” and no way to get it back.
I wear my sense continuously and only remove it to charge. So I am unsure how to get the Readiness Score started again.
My Sense, iPhone app, and iPhone are all fully updated. I’ve tried restarting both several times even though it syncs normally.
Any help would be appreciated.
12-14-2021 18:25
12-14-2021 18:25
Hi @RobertBN,
When prompted to renew the membership, did you select "Yes"? The "Readiness Score" is exclusive to Premium members.
Kristen | USA Cruising through the Lifestyle Forums
one cruise ship at a time!12-14-2021 22:16
12-14-2021 22:16
Yes I renewed automatically for a year long before my premium account ran out. All the other premium features seem to be working fine but the Readiness Score which reverted to Get Started and there’s no way to get started.
12-18-2021 14:43
12-18-2021 14:43
He is not no runner
03-04-2022 12:43
03-04-2022 12:43
Yes. It was an automatic renew and every other part of the premium offering is working.
03-24-2022 08:51
03-24-2022 08:51
RobertBN’s description of this issue describes the exact same problem on my Charge 5 (on iOS app). My Premium subscription auto-renewed on March 21, 2022, which was the last day that the readiness reading, including the history, was visible.
04-09-2022 17:08
04-09-2022 17:08
Hello,
Has you issue been fixed? I have the exact same problem on my Luxe fitbit. Since it automatically remewed 2 days ago, I have lost my daily readiness score
04-09-2022 19:11
04-09-2022 19:11
Unfortunately after over four months nothing has changed. Hopefully someone at Fitbit will look into it.
04-09-2022 21:24 - edited 04-09-2022 21:25
04-09-2022 21:24 - edited 04-09-2022 21:25
Hello olympe, I just saw your post, and wanted to let you know that the issue has not been resolved, nor to the best of my knowledge, has even been addressed by Fitbit.