@simplepinoi177 wrote:
Sorry I'm coming from a Pixel Watch 2 rather than the Charge 6, but I've been getting fed up with my watch's (and now I'm learning it's Fitbit's fault) sleep analysis and it claiming I am awake on average now 45%-over 50%!!!! I began googl'ing my issue and there wasn't any real widespread reporting on it, and this was the first instance (now that I know it's not specific to the Pixel Watch 2's but Fitbit app as a whole, I'll broaden my search).
At first I thought it was my sensitivity (which I lowered from sensitive back to normal), then I changed the arm I wear my watch, to then making sure I wasn't wearing it too tight (put the peg one level/hole next to my usual to make it looser)! Absolutely nothing is making it less outrageous! I am not restless for half the night! I even employed some phone apps snoring & sleep analysis, just for a rough comparison, just to see if there was any even slight similarities, and the apps' analysis is completely different and doesn't match it at all.
It all clearly started when I updated my watch at the end of June (that was when my watch's latest semi-annual update) -- I had to go back every single day manually deleting sleep thinking to correct my average times and simply removing the buggy sleep (after hoping it had been corrected); and it goes back directly & only to that update.
What's weird is my wife's Pixel Watch 2 seems to be unaffected (or at the very least, that greatly).
As I planned on resetting my watch completely, I think I will also do as OP suggests and call Fitbit customer support and complain.
So an update to this....I was able to fix things a bit where it's gotten back to being more or less back to normal; or at the very least not outrageous (giving me 39's and 40's).
So, the main thing I noticed was I was only getting decent scores (and it was even only in the 70's!) when sleeping like 8-and-a-half hours, and if I was to sleep for 7 hours and 45 minutes, it'll mark me at like 50's or 60's still! Then it made me realize that, even if I was being honest at trying/attempting to get the standard 8 hours of sleep, and inputting that in the settings, because of Fitbit's stupid messed algorithm and marking me as a whole lot more "Awake" than I know that I am, unless I'm getting more than those 8 hours and offsetting that messed up algorithm, I could sleep a really long time and still get a bad score; because it's counting more as "Awake" and so unless I put in more sleep time to add more non-Awake time, it didn't matter. Once I lowered the "sleep goal" -- and I mean rather unrealistic and severely (like 5 hours and 30 minutes) -- a good sleep that actually felt good was marked in the 80s; like it was in the past! No more of me getting where I could sleep for 7 hours and 30 minutes and feel really rested and get like 2%-4% more than my average deep sleep and REM, but only get like a 58 or 64.
Another thing that helped a lot was lowering my Awake average (because at this point it's close to 40%) -- I couldn't do much about being Awake a lot in the middle of the sleep cycle, but I was noticing that the terrible stupid algorithm was having me "Awake" for like 30 minutes before "Light Sleep" and fifteen-to-thirty minutes of "Awake" before ending my sleep cycle; so I would edit my sleep where I noted the times right before I actually went into Light/Deep/REM Sleep and to the minute of me waking up out of those, and edited the times to 1 minute before and 1 minute after. So, for example, I was Awake from 10:00PM-10:29PM, 10:30PM-11:45PM Light Sleep, etc....then Deep Sleep from 6:30AM-7:15AM, 7:16AM-7:30AM Awake -- I would edit the sleep to from 10:29PM to 7:16AM. Thus removing like 45 minutes of extraneous "Awake"; and thus lowering my average (if done for enough days). I mean, the "Awake" is important and vital in the middle of the sleep cycle, but unless it's "Light" going in and out of the sleep cycle, what's the point of notating you're "Awake" during the sleep cycle when, technically, you're not even sleeping! And honestly I'd be alright leaving this be, if Fitbit's stupid algorithm worked properly.
And of course any "Awake" that's above 40% throughout the night -- where there are like 2 hour blocks of Awake where I know I wasn't "Awake" or restless -- and since I can't just edit it out at the ends, I just delete the whole night's sleep cycle. And for the last like 8 months, I have whole gaps of "no data" -- but better that than weeks and weeks of 50's and 60's average that I stopped even monitoring and checking my sleep scores for months there. Thanks for nothing Fitbit. Fix your algorithm!
I even waited for October's update (for the Pixel Watches) hoping Fitbit would fix what they broke back in April, and they didn't...
Gold Fitbit Product Experts share support knowledge on the forums and advocate for the betterment of Fitbit products and services. Learn more
Best Answer
