Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Readiness stopped after premium renewal

Replies are disabled for this topic. Start a new one or visit our Help Center.

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. 

Best Answer
8 REPLIES 8

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!
Best Answer
0 Votes

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. 

Best Answer
0 Votes

He is not no runner

Best Answer
0 Votes

Yes. It was an automatic renew and every other part of the premium offering is working. 

Best Answer
0 Votes

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.

Best Answer

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 

Best Answer

Unfortunately after over four months nothing has changed. Hopefully someone at Fitbit will look into it. 

Best Answer

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.

Best Answer