Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Daylight savings time issue

ANSWERED
Replies are disabled for this topic. Start a new one or visit our Help Center.
We just changed over to daylight savings time and now the android app is running an hour ahead. As if the time went ahead two hours instead of one. I have a fitbit one and it adjusted the time correctly. I turned off sleep mode at 7:30 this morning, synced to the app, and app shows as 8:30 instead of 7:30. Is anyone else having this problem or have any ideas how to fix?
Best Answer
1 BEST ANSWER

Accepted Solutions

Yes, I found it by looking at today's steps. Mine seems to be working fine but some iOS users are reporting the same thing and Fitbit is aware of it.

View best answer in original post

Best Answer
0 Votes
11 REPLIES 11

Where are you seeing the actual time in the app?

Best Answer
0 Votes
When looking at sleep time, for instance, it says that I woke up at 8:30 I
stead of 7:30. There are steps, calories, etc showing for an hour later
than it actually is on all graphs.
Best Answer

Yes, I found it by looking at today's steps. Mine seems to be working fine but some iOS users are reporting the same thing and Fitbit is aware of it.

Best Answer
0 Votes

seems to be that daylight saving still does not work.

 

today it was - one hour. but fitbit dash shows like i wake up 6.57 not 7.57. fitbit time is correct but stats is missing hour.

 

Screen Shot 2016-10-30 at 8.13.00 AM.png

how we can fit it?

 

also when i walk, there is dot collecting in wrong time.

Screenshot_20161030-093929.png

it is in fitbit dashboard correct but app does not understand daylight time.

iphone 13 mini, Oneplus 8, Versa 3 | Retired: Flex (2x), Charge HR, Charge 2, Versa SE
Best Answer

Having the same issue - Dashboard and device showing correct times - but android app is one hour behind. When I check the app time zone for Eastern it shows GMT -4 - should be GMT -5 now with the time change but there is no selection available for that. If I change to Central which displays GMT -5 - everything else changes including the time on my Charge - to show actual Central time. Makes it very confusing especially for the 250 steps per hour as it will not mark complete but two open hours are displaying as the time on my phone is accurate.

 

Can  you please add a selection for EST GMT -5 to the app - I think that will resolve the issue.

Best Answer
How do you fix it
Best Answer
I'm also experiencing the same issue. Has anyone been able to do something to resolve this?
Best Answer

Hey @urmoluts@Gma_Pat@doninhollister@marmar5Hope you're enjoying the forums! Cat Happy

 

Sorry to read the issues you're having with the time in your account and thank you for bring this issue up. My best recommendation is to check if the timezone in your account is the right one. If so, change the timezone (following the steps provided by @AlejandraFitbit) to an incorrect one, sync your tracker and then change the timezone back to the right one.

 

Let me know how it goes!

 

Marlen S. | Community Moderator

What's for breakfast?Check others recipes and share yours!

Best Answer

I reported this to Fitbit Support but apparently they cannot log bugs with their Engineering group.  There are actually three bugs related to DST that I observed:

 

(1) Dashboard (on web and on iPhone) adds an hour to when I woke up.
(2) Log fails to subtract an hour of elapsed time for the skipped hour
(3) Dashboard (only on iPhone, not on web app) mislabels the hours on the active hours.
 
(1) and (2) are shown in the attached picture.  The box on the left is the dashboard view of my sleep: note that it shows I awoke at 8:22AM PDT.  The box on the right is from the sleep log, which correctly shows I got up some time after 7AM.  That is problem (1).  If you calculate the hours from 10:24PM PST to 7:22AM PDT, it should work out to 7:58, yet you do not subtract out the skipped hour, and show 8:58 in the sleep log; that is problem (2).
 
I did not capture a picture of the iPhone for issue (3), but it is correct in the log.  It was correct the following day.
 
In the big scheme of things, they (issues 1&3) were mostly "cosmetic" errors for the day we changed the clocks; the only "true" error (issue 2) was the extra hour of bed-time since the skipped hour was not subtracted out.
 
 
Capture.JPG
Best Answer

Not sure why this would be flagged as "Resolved".  Just because we all know that it was a problem that exists only on the day we mess with the clocks is not the same as "it has been fixed and won't be a problem again next year."

 

Can't wait to see what happens on Nov 5 ...

 

Best Answer

This is as bad as the response I got when I mailed Support.  It is a bug - you just refuse to look at it and understand it.  #Fail.

 

Best Answer