TSB display bug

[Steven Limmer]

This post is deleted!

[Steven Limmer]

replied too early and can’t delete comment

[isazi]

@Steven-Limmer I can delete your previous post if you want

[Steven Limmer]

This post is deleted!

[Steven Limmer]

@Steven-Limmer Have gone for a lunch run, and now the Active/Inactive values are in sync…

[Tieutieu]

@Steven-Limmer Just checked. For me too.
So I guess it’s because we past noon.
I bet tomorrow morning we will have the difference again.

[herlas]

TSB by TrainingPeaks definition is always the difference between yesterday 's fitness (CTL) - yesterday’s fatigue (ATL).

[Tieutieu]

@herlas Yes, of course.
The question is not about TSB calculation which is OK.
The question is about the value displayed on the widget in the watch that shows TSB values of previous days instead of value of the day.

[herlas]

@Tieutieu you mean from 2 days back? Either that or TBS from today’s numbers are not correct.

On my SV I’m seeing the right TBS, I get TBS of - 5 in TP, SA and SV widget and watch face that came from SR.

I know your issue is on S9PP, BTW , to summarize it, any TBS value not equal to yesterday’s CTL-ATL is wrong.

[Tieutieu]

@herlas
If you don’t seem to have the problem, a large amount of users have a difference between TSB value in SA, which is OK, and TSB value in the watches, which shows TSB of past day.

What we just noticed with @Steven-Limmer is that this difference (in the morning only) is one day when watchface is “locked”, and two days when unlocked. When noon has been passed the difference is 1 day.
I’m on SV.

[Steven Limmer]

@herlas this isn’t the point though. There are 2 values showing depending on whether the watch is inactive or active

[herlas]

@Steven-Limmer got it, yeah, just wanted to be sure we don’t call yesterday’s values (1 day) a issue for TBS.

Thanks

[Tieutieu]

@herlas No TSB calculation Issue. It’s a watch widget display issue.
(Are you sure you don’t have it ? After a soft reset or a restart the values are ok, but next day the difference occur).

[Steven Limmer]

I think the summary of this bug is:

• TSB on the inactive screen is correct
• TSB on the active screen is incorrect until 12pm OR an exercise is performed before 12pm

Seems like a relatively simple timecode error