Sleep metrics mismatch after editing sleep log

[DannyFB]

When I edit a sleep log to remove the hours where I was simply reading a book or watching a movie it results in nonsensical and mismatched sleep metrics. Example of mismatch being the main interface will show, for example, perhaps 30 minutes of deep sleep while the secondary (drilling down) will show an hour and some minutes.

The bug, in my opinion, is in the recalculation of sleep metrics after edit of sleep log. Should be easy to figure out if someone with access to the code could read the code.

Anyone else notice this?

Update 3:37 PM 9/9/2022 -- From my PC now. I will try to post the screen shots showing what I am reporting. NOTE: This failed from my Android phone (3.66) with a nonsensical cannot post because it contained a string of digits that cannot be mentioned for an unknown reason. I will post the screen shots first, to see if that is accepted. Then, if it is, I'll offer explanation.

On that one (Sleep metrics when you drill in to see them) NOTE that it shows 31 minutes deep sleep and 12% REM (don't get me started on why somebody decided to show deep sleep in minutes but REM in a percentage of total).

That worked. I was able to post from PC. Here is 2nd screen shot to look at for illustration of the issue reported here. NOTE this is screen shot including the error I got telling me I was not allowed to post. Check out the metrics for Deep sleep and REM. They are NOT THE SAME. THIS happens darned near every time I edit the sleep log to eliminate where FITBIT decided I was sleeping during the movies, etc.. 

[DannyFB]

Charge 5

3.66

[DannyFB]

• What zero-nine-dash-zero-seven-three-two-zero-two means.

[DannyFB]

INSANE!!!!

FITBIT doesn't allow the actual digits to be posted. Which prevents me from asking what those digits mean in the error messages I get back when I try to post something....which doesn't have those digits included.

Basically there is another bug in fitbit app where the solution appears to be to simply prevent me from posting about it.

[DannyFB]

AND this post automatically selected itself as the Best Answer?

[SunsetRunner]

Hello @DannyFB 

You can unselect your best answer. To revoke a Best Answer, click Options > Not the Best Answer. You can then choose another answer or leave the question unanswered.

Can you describe what happened instead. What are you trying to do? I see your in the Android forum, is it a Fitbit App issue your dealing with? Or is it a Fitbit in particular that is giving you an issue? Which Fitbit model do you have? 

[Guy_]

Hi @DannyFB - could you explain where you see this information, could it be a case number from support?

[DannyFB]

Well.....hard to explain since I am not able to actually use the numbers themselves....when I try to post it I get back rejection (within the body of the post, when using PC as I am now). The rejection is telling my I am not allowed to have a posting with that number in it and therefore I must remove that number before I can post. This is the craziest bug yet and we know there have been a LOT of them over the course of the past few months. So take the "subject" which is written phonetically and transcribe it to be the actual number in the form of "dd-dddddd". THAT number is not allowed in a post. Make sense of that, if you will.

[DannyFB]

And since that post worked (because I did not have the dreaded "dd-dddddd" in the body) allow me to expound a bit more: I originally got the error when I tried to attach phone screen shots of what the FITBT app was showing me for sleep metrics, to go along with that posting in regards to a problem where editing the sleep log results in crazy wrong and non-matching sleep metrics. THAT posting had no "dd-dddddd" in it anywhere yet it kept getting rejected because "dd-dddddd" is not allowed to be posted to the community board. I am SO very interested in knowing what "dd-dddddd" actually is. It must be something deadly like the nuclear missile launch code or something?

[Guy_]

@DannyFB - suppose the question is why are you trying to put that number in a post in the first place?

As mentioned it may be considered a case number (which are private) or just meaningless.

There are many sequences that aren't allowed.

[DannyFB]

And, finally (until more) -- NO, I have not contacted technical support because we all know the answer is going to be:

1) Shut everything down and then start up again, see if the problem goes away.

2) If problem doesn't go away then delete all FITBIT applications and devices from everywhere they can possibly exist, then re-install everything and see if the problem goes away.

3) If the problem doesn't go away then go back to step 1 and circle back around

Update: As has been pointed out I missed the final step of "Then just don't try to do that anymore"

[DannyFB]

Why am I putting that number in the post?

Circle back, take a deep breath, and actually read what I type.

I did NOT enter that number when the problem itself surfaced. I simply tried to attach a screen shot to a problem report. That problem report did NOT have those digits in it anywhere. Yet I get the error telling me I'm not allowed to have those digits in a posting and I must remove them before posting. But, obviously, since the numbers don't exist anywhere I can't remove them.

So I did some troubleshooting by simply creating an entirely new post within nothing in it but those digits (in the Subject line). I got the same error. That time it did at least make sense in that the posting actually had those numbers in it.

And I guess, clearly, I missed one of the standard tech support answers -- If reboot of everything doesn't solve the problem and deleting everything and starting over doesn't solve the problem and it is the nth time through that process then, finally: 4) Just don't try to do that anymore.

Me "Doctor, it hurts when I do this"

Doctor "Then don't do that".

[DannyFB]

Interesting that this entire post has been silently deleted.

Actually, it appears to have been merged into this one?

Talking/chatting with Support in regards to the number that cannot be mentioned: Answer is that they'll escalate to somebody else. Right...

Also talking/chatting about sleep metrics: Answer- see above. Reboot everything. If that doesn't work remove everything and start over.

[LizzyFitbit]

Hi there, @DannyFB. @SunsetRunner and @Guy_ Thanks for stopping by to help our member.

@DannyFB Thanks for the detailed information, and the screenshots provided. I understand where you're coming from as the sleep details should match correctly on the Fitbit app. Because this isn't the case, may I know since when this started to happen? What is the model of your phone? Also, does the same happen when editing different data such as an exercise?

I believe you've already done so, but please confirm if you've tried the following steps:

1. Log out from the Fitbit app.
2. On your phone's settings tap Apps > Fitbit > Storage > Clear Cache.
3. Go back one screen, tap Force Stop and reboot your phone.
4. Open the Fitbit app and log back into your account.
5. Pull down on the screen to force a manual sync.

About your other question, I noticed you started this other thread and I've provided a response in there. In the meantime, let's try keeping the conversation of each topic in their respective threads. This will help us to keep the forums organized, and prevent any confusion.

[DannyFB]

LizzyFitbit -- understood.

But please do keep in mind that many of us "out here" actually want solutions rather than "try this and see if the problem goes away...for a while...and then do that again....for a while...". 

I already know how to get over the problem. Just wait a few hours and it then synchs up. Sometimes many hours. Sometimes only a few. But I'm tired of it happening. It has been happening since I got the device back in December of 2021. It happens more and more often with each application update update. Android phone. Currently version 3.66.

Another of those simple ones to replicate, I predict. 1) edit a sleep log, 2) check out the sleep metrics (after you have Saved the edit, obviously). 

No offense. It is a common issue. Hard to tell if somebody simply wants to recover and move on versus somebody actually want to NOT experience the problem anymore.

-danny

[LizzyFitbit]

Hi there, @DannyFB.

Thanks for getting back and sharing more details about this situation. Let me clarify that the steps shared in my post were suggested just to make sure that we've exhausted all the possible steps. However, I understand where you're coming from and appreciate your feedback.

That being said, because the issue still persists, I'd recommend contacting our Support team so they can investigate and provide you with further assistance. They're available via chat and phone, please click here to get connected with them and make sure to let them know every step tried so far.

[adolfwerner]

Hi, did you manage to get in touch with the team about this? Thank you.

[DannyFB]

The usual:

Never heard such a problem.

Try restarting phone.

Try restarting the device.

Uninstall and reinstall.