01-08-2022 02:16
01-08-2022 02:16
Having bought a blood glucose monitor, I thought I would track the levels using my Charge 5.
I entered my first value this morning, which at 4.7 mmol/L is within the ‘normal’ range of 4-7.
When I click on this mornings value it confirms that it is well within the range yet on my summary screen it says it is out of range above 40?? I have got mmol/L unit set which is what should be displayed in the home screen??
has anyone noticed this when using?
thank you
pete
01-08-2022 02:32
01-08-2022 02:32
Hello @Porridge51
I don't use it myself but looked at the information on the site:
I couldn't see anything and then looked at your message again. Did you forget to put the decimal point in? If you did, 4.7 would end up being 47, which would be out of your range.
If it was just a typo in your post here, please ignore this one.
Good luck!
01-08-2022 04:18
01-08-2022 04:18
@Porridge51 Do you use an Android or iPhone? You are describing an app bug, not a Charge 5 issue. I want to move this post to the correct app forum. If other users are having the same problem, then it is easier to get Fitbit's attention.
Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS
Take a look at the Fitbit help site for further assistance and information.
01-08-2022 08:02
01-08-2022 08:02
The blood glucose device also suggests logging an entry after a meal as well as first thing having fasted overnight.
I did another test and entered it on the app and again a reading, this time 5.5 mmol/L shows up correctly in my daily stats(both of them for today do) but on the summary home screen it shows now as out of range and over 99?
01-11-2022 06:50
01-11-2022 06:50
I sent fitbit a direct message to their twitter support facility.
In summary they know about the problem I have posted about but are not intending to fix it.
So if you log your blood glucose levels in your fitbit app please be aware that the value reported on your home screen is wrong.
02-01-2022 19:20
02-01-2022 19:20
I have the same issue and posted to the app section of these forums - am yet to have anyone make any response whatsoever. Per the commenters below, the issue is not with forgetting to put a decimal point in, and he issue persists even when changing measurement units, reinstalling the app or restarting the phone, so something is screwed up with the app. I'm using an iPhone, for what that's worth.
02-01-2022 23:37
02-01-2022 23:37
Maybe send fitbit support a direct message?
I only got my response from doing so, with no response (from them) to my post on this forum.
I guess with so few reporting the problem they don’t see it as a priority and are not prepared to put any resource into fixing it?