- last edited on by
DavidFitbit
- last edited on by
DavidFitbit
I had to continue my topic with a new one because replies were disabled on my original. Fitbit reps, please report these problems and get the bugs fixed.
https://community.fitbit.com/t5/Sense/Sense-Sleep-errors/m-p/5748355#M75664
May report
I've been taking weekly updates from google play for bug fixes but nothing ever gets fixed with this sleep bug. All I ever see happening is more very useful features being deleted and doubtless, more useless features being added. One of the most annoying losses occurred with the bug fix update last week when the ability to force a sync in the usual way disappeared. Has that been moved to some oddball place?
In May, this app worked properly to show a sleep score and proper sleep stages 18 days out of the month. How can this be considered useful for any practical purpose? It would be so nice if this app allowed the fitbit to be used as a tool to learn how to improve sleep quality and get more deep sleep. I've been using fitbits since 2015 and they're still nothing but a toy.
Funny thing is, even when it works right for score and stages, it still trashes the records in an often irreparable way. For instance, on June 10 I went to sleep very early. Asleep on the sofa by 7:30 after a very hard day of work. At 8:06 I was awakened by network alarms when our power went out. I was awake long enough to turn on more emergency lights, silence the alarms and start the electrical co-op app to view the outage information. It didn't seem like anything outstanding so I chose not to start the generator and went right back to sleep. I woke up again at midnight when the power came back on thanks to the TV. coming back on. After going to the bathroom, I immediately went back to sleep. This is how the fitbit app recorded my night of sleep. It was another irreparable situation because it wouldn't allow an edit.
As happens quite often when the app goes brain dead, it will come up with the flimsy excuse of "Can't save sleep session A sleep has already been logged in this time period." Well duh, of course it was. I was asleep. I knew it, my Fitbit knew it and obviously this broken app knew it. Why can't the app work with the data it admits it knows about and simply create the proper records ? As a farmer, I get up early and I go to bed early. Many times I wake up around midnight for a few minutes and go right back to sleep. Why does this simple act cause the app to fail at properly recording sleep so often?
Moderator edit: Clarified subject
Best AnswerAs a means of trying to narrow down these silly fitbit errors, a few days ago I updated the app on my android 11 phone that's connected to another account and fired up my in reserve new Sense to wear on my right hand. v 4.44.2
I continued wearing my 4¼ year old Sense on the left hand, connected to the latest and greatest badly broken version of Fitbit on my android 14 phone.v 4.45.
How my usual android 14 version of Fitbit read my sleep last night. I was up late and didn't go to sleep until around 10:30. At least this idiot app gave me a sleep score and stages.
This is how the android 11 version reading the new fitbit saw things. Very cute. 10 hours 2 minutes of sleep during an elapsed time of 6 hours 48 minutes.
Best AnswerHere's the first two days of this experiment. The only thing that's consistent is the Thursday sleep data for both watches. One minute of difference in awake time. No sleep scores or stages. Friday sleep data also without scores or stages.
There is no consistency and who knows what is closest to accuracy. Typical Fitbit nonsense. Fitbit really is just a toy that's only useful for entertainment value.
Thursday old Sense on android 14 main screen and sleep screen
Thursday new Sense on Android 11 main screen and sleep screen
Friday old Sense on android 14 main screen and sleep screen
Friday new Sense on Android 11 main screen and sleep screen
Next part of this experiment will be changing the handedness of the watches and swapping hands.
Best Answer