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: 

Bloody alarm didn’t go off because of the clocks going forward.

‎03-30-2025 05:25

‎03-30-2025 05:25

As title.

Still woke up, fortunately, and only 1 minute later than the alarm was set for.

Just very annoying. My phone and my Fitbit have both gone forward, and are synced.

Will remember this for the next stupid clock shenanigans.

https://19216811.cam/ https://1921681001.id/
Best Answer
1 REPLY 1

‎03-30-2025 07:15

‎03-30-2025 07:15

Hi @kathama2   You can give feedback directly to Fitbit/Google in the Fitbit app.  Tap on your profile picture, then send feedback.  As a long time user, I can confirm that the clock change can mess up hourly activity and sleep tracking.  I think your post is the first alarm failure I've seen.

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