Sense 2 Firmware buggy

[JerryHam]

I see several bugs with the firmware on the Sense 2. One that I hit today was pretty laughable. I had already gotten 447 zone minutes this week (I have the week starting on Sunday). The Sense 2 came up with this message:

Need lots of minutes

So, I need 65,239 more zone minutes in the next 3 days to get to a weekly goal of 150. Now, most people would realize that a full 3 days has only 4,320 minutes - and even if we count "zone minutes" (where you can get double minutes for cardio and peak HR zones) you could only get 8,640 zone minutes in 3 days (and only if you were in cardio or peak HR zones the whole time).

Funny thing was, about one hour later it showed me this:

Pace picked up!

Apparently I did NOT need to pick up the pace as I had been told just one hour before.

There seem to be a lot of crazy bugs like this throughout the firmware.

[t.parker]

Looks like your Sense 2 tried to kill you 🤣

[JerryHam]

Many months later, this has still not been fixed. Today, I got this one:

Notice it says that the incorrect number of Active Zone Minutes needed is to get to my "goal of 150 zone minutes". But, at the same time, I see that I currently have 419 Active Zone Minutes so far this week - well over the goal of 150.

[Guy_]

Hi @JerryHam - thanks for taking the time to post the photo too, sorry had to laugh! Definitely a bug!

[Dopovo]

Yes, it is nice to laugh sometimes but this series of silly bugs is very concerning and raises several question on where Fitbit is going as it is evident there are big problems of quality control in Fitbit.

[honglong1976]

Definitely a bug, but how to raise it as a bug?

[t.parker]

@honglong1976 there is no bug tracking or labelling system so really, reporting bugs here doesn't do probably anything.

@JerryHam this one is tricky. How many times have you managed to reproduce this issue? Are these only these two occurrences several months apart (low reproduction rate)? From the first occurrence, I see it didn't stop you from getting the correct AZM eventually (low severity). Not sure if anyone else experienced that issue which would mean that it is incredibly rare. Also, reproduction steps seem to be unknown (looks occurring randomly). For most companies, that would mean leaving this issue in the backlog waiting for better times as it's not critical (doesn't break data, doesn't cause permanent damage to data, doesn't crash anything etc.) and it's very rare. I don't want to here defend Fitbit on that but, I wouldn't know how to chew it (maybe an hour of time could be spent trying to see if it's something obvious in the most obvious areas, as it looks like an underflow and type error (decrementing unsigned short value, when it drops below 0 it goes back to 65535) but if it isn't so obvious and nobody else can reproduce (so also verify the fix) then the such issue would land in the backlog. Fitbit doesn't even fix critical issues so that pretty much tells the fate of this bug anyway 🙂

[Guy_]

@honglong1976- unfortunately as @t.parker - rightly says there is no bug reporting facility nor any recognition of them nor any reporting when any are fixed.

Fitbit are supposed to exam the forums but there is no means of knowing if they do without a formal register.

And as such the Customer support is often unaware of ongoing issues which can compound the issue of problem solving with the clients.

What would be brilliant is if there was a register of problems that we all could consult and a notification in which firmware release the issue was resolved.

Till now it has been up to members of the forums to do this work voluntarily.

There is so much room for improvement.

[JerryHam]

It is only supposed to show this mid-week on the 4th day of the week. It reproduces about once per month, so 1 out of 4 chances. Obviously low severity. It is so funny because the AZM is so far off because the HR is so far off that it is useless to have an AZM warning anyway. I got 150 AZM the other day on a day that I did not exercise and my HR (real HR) didn't go over 85. Should have been 0 AZM. But, this is still a bug and after fixing high priority ones they should then fix low priority ones like this.