help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Clocks going back problem

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎10-31-2021 00:20

‎10-31-2021 00:20

Last night's sleep log says I woke up at 5.58am. (6.38hrs). It should have read 6.58am. If the clocks hadn't gone back last night it would have been 7.58. I've added up the different components of my sleep and it comes to 7.38 hrs. It's as if we went back two hours not one.

Best Answer
Labels:
1 REPLY 1

‎11-02-2021 05:40

‎11-02-2021 05:40

@Kazar12   This happens every time there is a clock change, whether it's BST to GMT or the US switch from daylight savings time to standard time.  It happens twice a year, every year.  It takes a day to sort it out.  Reminders to move hours tend to get messed up, too.  It is a limitation in Fitbit's programming.

Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS

Take a look at the Fitbit help site for further assistance and information.

Best Answer
0 Votes