Move reminder set up is bugged

[AggraRhubarb]

After daylight savings I noticed my reminders to move got shifted an hour forward when I would have rathered they stay the same. However if I try to edit the start and end dates manually they start spinning to random values. IE if I set the start to 7 am, it rolls to 9 am, then also causes the end time to roll to another value. If I try to edit the end time the am/pm values swap so it starts at a pm time and ends at an am time. Is anyone else seeing this? It’s frustrating and I can’t get it back to my preferred setting. My app and Versa firmware are up to date and I’m on iOS.

[SarahE1115]

I have the exact same problem. Plus, the hours jump from 8 hours active to 10 hours active to 6 hours active and mess up my hourly activity stats for past days and weeks as well as for my current day. So far, I haven't been able to find any sort of "reset to default settings" for activity goals or at least a cancel button to go back to what one had before one tried to change the hours. Mine is a total mess now. I deleted the app, reinstalled it, and logged back in only to find everything the same mess as it was before. I tried going on the chat help, but nothing came of that. I'm hoping someone in customer service may have some ideas when I call tomorrow. Or maybe we'll luck out and it will straighten out by itself.

[LZeeW · Accepted solution]

@AggraRhubarb  @SarahE1115   All long time Fitbit users know that this is a recurring theme with the switch to DST.  I also happens, for example, when flying and crossing multiple time zones.  It works itself out in a day or two.

[SarahE1115]

Will that also take care of the "spinning numbers" problem that occurs when trying to manually set up the start and end times for 250+ steps every hour? People may wish to change the start and end times for reasons other than DST. I'm afraid to touch anything at this point, but it's discouraging that I can't set the hours to what I want them to be. Thanks for any help you can give for that aspect of the problem.

[SarahE1115]

Looks like the “spinning numbers” issue got resolved as well. Phew! Thanks, LZeeW!