Incorrect tracking of HIIT tracking

[Tonio08]

While tracking the HIIT exercise, the phone is correctly saying work and rest. However these actions are in the reverse while reviewing on the app.

Any suggestions on how to correct this?

[t.parker]

@Tonio08 looks like at least 3 years old issue. Earliest report I could find is here (early 2020) and has been left unanswered. I will check if I can reproduce the bug as not many reports of it out there and it's rarely used tracking option or issue is only local to some users.

[t.parker]

The order of intervals is correct for me in the app. Are you able to reproduce this issue every time (more than one workout showing this behaviour). Also, can you see if you use Interval Workout not HIIT the issue still persists? I don't have Sense 2 (HIIT is only available on Sense 2/Versa 4) anymore and issue previously occured for Interval Workout. However, with IW I am unable (so far) to reproduce it.

[Tonio08]

@t.parker yes it occurs everytime. I tried the Interval Workout, that's also doing the same. They are in reverse on the app.

[t.parker]

@Tonio08 I did only a "dry test" today using original Sense (just sitting at my desk I started IW with 30sec Move/Rest intervals) and that came up in my app correctly. However, I went back in my log to December last year and found out the issue occurred for my Sense 2 (it was also just a "dry test" but reproduced the issue):

I'm wondering whether it happens to other Sense 2 users (and probably Versa 4), too. I will try to reproduce it on my original Sense (when the issue was reported long ago, Sense 2 was not in the market yet). If it's device-related it may mean that the bug has been fixed for an older model but before that happened it's been transplanted to the new one with an outdated codebase. Just my guess but I expect that eventually I'll reproduce it also on Sense.

[Tonio08]

Yes, I'm thinking that it's only related to the Sense 2. Thanks for your assistance 

[t.parker]

More digging reveals the issue occurred for Charge 4 using the iOS app almost exactly a year ago (unanswered): link . One thing I noticed was that such an old device didn't have an interface on the watch to set up intervals duration and the only way to do it was through the website.

The issue has appeared also on Inspire devices in 2020 (link) .

Even one report in 2018 for Charge 3 (link) .

And a few more (mostly 2019):

https://community.fitbit.com/t5/Android-App/Interval-Timer-Bug/m-p/3608586

https://community.fitbit.com/t5/Other-Inspire-Trackers/HIIT-intervals-download-backwards-to-the-app/...

Mostly Inspire and Charge trackers. Maybe Sense 2 inherited something from their old codebase when it sends data back into the app? Or inherited from Sense for which issue has been patched?

This thread mentioned an issue in the web API that assigns wrong types to the intervals when setting the durations and that resulted in swapping Move and Rest.

It seems like it's a bug that Fitbit lost any control over and it's been lingering out there for at least 5 years now. Both apps, Android and iOS seem to experience it so the problem most likely is on the server side when data is being transferred with wrong interval types during sync.

Charge and Inspire devices have one thing in common - the interval duration can be set from the app or website (this now is totally redundant I guess). Sense and Sense 2 have only one way of setting durations - on the watch. Many things can go wrong.

On your side, not much you can do and see that a) Sense 2 hasn't received any update for many months, b) the bug existed across multiple devices, apps and mobile OSs - I wouldn't hold my breath waiting for a fix.