Issue with Setting Sleep Goal in Fitbit App

[baraksheleg]

I’m unable to set a sleep goal in the Fitbit app. Each time I try to set a specific sleep time, the app shifts it to a different time (for example, I set the sleep time to 11:15 PM, but it appears as 8:15 PM). I have no idea why this is happening, and I’m unable to resolve it. What should I do?

Thank you for your assistance!

P.S. I am using a Fitbit Charge 6 device.

[RudieS]

Im having the same issue. Ive tried reinstalling the app, restarting the device, restarting my phone etc. but nothing is working. Other posts refer you to the basic steps but these dont solve the problem.

[Jollies]

I have the same problem and cannot find an answer the device is only 4 months old but it appears to have a bug

[Carolinne]

I have the same problem. Just got my device exchanged from 5 to 6 and now my sleeping goal has changed and I can’t fix it. 😣

[acousticlmo]

Same issue here! Just tried to change it today and everytime I save it, it changes it to something bizarre that is not at all what I entered. Would be nice if someone at Fitbit would address this. 

[Amysrecord]

Having the same issue. Seems to have started last night. Using inspire 3. 

[Dlbergthold]

I’m having the same issue.

[RudieS]

Evening everyone,

Mine seemed to sort itself out. Not sure if it had something to do with
Daylight Savings here in Ireland. The only suggestion I could give is to
make sure your mobile and wearable are both updated.

[kmorgand]

I’m having the same issue! I tried updating and restarting the app and syncing my device, but no change. Very frustrating.

[RiekoC · Accepted solution]

Hello @kmorgand , @Dlbergthold , @acousticlmo , @Amysrecord 

Sorry to see that you've been having issues with setting/editing your sleep goals/logs.

Unfortunately, this is something that typically happens due to the biannual time change and usually fixes itself in a day as @RudieS noted. Let us know if you are still having the issue.

Also, please make sure you've updated your Fitbit app to the latest version.

[Amysrecord]

Thank you. This seems to have corrected itself as you indicated. 

[kmorgand]

Yup, mine fixed itself! Thank you! 

[RiekoC]

Hello @Amysrecord & @kmorgand 

Thank you for confirming that you no longer have the issue. Hopefully, it will be the same for the other users on this thread.

[Dlbergthold]

Mine also fixed itself too!  

[baraksheleg]

Thank you very much!

Indeed, as you noted, it fixed itself!

[RiekoC]

Hi @Dlbergthold & @baraksheleg 

Thank you for confirming the issue fixed itself.