Incorrect data for Zone Minutes/Target Heart Rate Zones near midnight

[jonseymour]

I have noticed that the FitBit Zone Minutes/Target Heart Rate Zones page on the iOS Fitbit App is showing incorrect data in the hours just after midnight.

Furthermore, this range of data becomes increasingly incorrect as the day progresses.

Here are 5 screenshots. The first four screen shots, show the Target Heart Rate Zones screen at various times on the same day,. As the day progresses, there are HR spikes corresponding to activity on the right hand side of the graph but, surprisingly, spikes also appear at the left hand side of the graph for times that had previously been reported and during which no activity occurred (I was in bed asleep at that time).

When I went for a run at 10pm, there is a large spike on the right corresponding to that run, but apparently this caused a spike at 2am - 20 hours previously when I was very definitely in bed, asleep.

The final screen shot shows the main heart rate graph which comports exactly with reality - no posthoc phantom spike at 2am and a completely explicable spike at 10pm (only).

I have reported these symptoms to FitBit support, but I leave these here for the information of others that might be trying to explain spurious spikes in the Zone Minutes - Target Heart Rate Zones graphs.

Moderator edit: subject for clarity 

[LiliyaFitbit]

Welcome to the Fitbit Community, @jonseymour.

I appreciate your participation in the Forums and sharing that the Zone Minutes/Target Heart Rate Zones page on the iOS Fitbit App is showing incorrect data in the hours near midnight. Thank you for providing the additional details and screenshots, I am glad to assist you. I appreciate the information that you've reporting this to our Support team. I've confirmed that you already have a case with them. I know they will be glad to help you out and provide a solution. I recommend to continue working with them since they have already all the details and special tools to continue assisting you. 

Let me know if you have any questions.

[jonseymour]

Thanks.

My support case is not going well.

Having being asked to factory reset the device for what is clearly a iOS app issue, I am now being pushed down a warranty/product return path despite the fact that there is no evidence that the hardware (or firmware) of the device is faulty and every evidence to suggest that the flaw lies entirely within the implementation of the NEWLY RELEASED software feature for heart rate display within the Zone Minutes section of the iOS app.

To be clear. I am not reporting a problem with Fit Bit Versa 2 hardware or firmware. I am reporting a problem with the iOS app. In no conceivable universe will the problem I have noted in the iIOS app be rectified by the replacement of my FitBit Versa 2 hardware. I have explained this to FitBit support but they continue to seek to replace my hardware despite the fact that I have pointed out that such a replacement would be pointless.

[Rach89]

Hi, did you ever get a solution to this problem? My Fitbit app is also affected like this, I don’t think it my Fitbit sense that is the issue I think it’s the app, it changes on the left side after activity, but I don’t understand why. Following a walk this afternoon it has changed my recording from this morning, I’ve attached pics to help show the issue. 

 

 

[Bones19]

I am also experiencing the same disconnect between the 2 graphs (high heart rate when sleeping in Zone minutes/Target Heart Rate graph and normal below heart rate showing in main heart rate graph). I have a Charge 4. It is getting increasingly frustrating when key metrics like this are so disconnected and makes trusting the data more difficult. I have seen additional issues being reported on the Fitbit app. The battery level indicator is stuck on a fixed % and this issue has been like this for a while. It seems that there is limited attention from Fitbit to fix these issues.  

[gwalker3]

Thank you so much for this. I was getting so concerned - now I can relax knowing it’s just the tech and not my heart. 

[FennC]

Thank you for sharing. Has anyone got this resolved with Fitbit?

[Pegatha]

I’m wondering the same - has anyone gotten a satisfactory answer to this problem? I gave up on support after I tried everything they suggested. They wouldn’t escalate the problem to their engineers.

[Richard773653]

I’ve just had the fright of my life - thought I was going to have to visit a&e

woke up to this….

 Thankfully my wife then checked my heart rate data …..

 The two are completely different - my heart rate data graph is represent an accurate overview of my heart (from what I can gather!) whilst the zone minutes graph would suggest I was either doing cardio all night or am about to have a heart attack.

This is really upsetting

first time ive noticed this but will check past data now - someone has to provide an explanation 

[Richard773653]

 

[Richard773653]

 Apologies - the forum wouldn’t allow me to post thise pics in my original post - another big !!

[jonseymour]

No, I did not get a resolution to this. 

I have a feeling that the problem can't be reproduced by developers who don't live in the UTC+10/+11 timezone as I do. They can't fix what they can't see, they can't see because they can't be bothered testing in non-US timezones.

[Pegatha]

I’m in UTC -5. Customer support had me try at least a dozen things and nothing fixed the problem. They would not escalate the issue. I gave up.

Sent from my iPad

[Richard773653]

It seems clear it’s a fault that can’t be dealt with - which in my case
frightened the life out of me and it should be clearly printed in the
instructions that erroneous zone reporting can occur.


--
Sent from Gmail Mobile

[Pegatha]

Yeah, I was checking out some features I hadn’t before while on vacation. When I saw that graph I almost panicked and was going to go to the ER until I looked at the graph first thing the next morning and then later in the day and discovered it was an error in their graphing.

Sent from my iPad