03-19-2025
09:53
- last edited on
03-20-2025
07:32
by
DavidFitbit
03-19-2025
09:53
- last edited on
03-20-2025
07:32
by
DavidFitbit
So I updated my Charge 6 this morning (on Android) now the repeating alarms are showing grey with a cross and the only way I can have them on is to have a 1 time alarm any ideas?
I've restarted the watch uninstalled the app on my phone and check DND and sleep mode and neither are on.
Moderator edit: updated subject for clarity
04-17-2025 19:41
04-17-2025 19:41
Any news ? Can we just go back to the old software. that situation is pretty ridiculous for a simple alarm clock function...
04-19-2025 09:29
04-19-2025 09:29
Just a thought to the Fitbit folks. Take down the current update as it is worse than the original version. Stop getting people to update their watches with an update that doesn’t work!
04-20-2025 17:42
04-20-2025 17:42
For anyone looking for an update as of 04/20/25, this is still an issue. It seems as if you are not able to set recurring alarms that will go off in the next 24 hours. My suggestion is adding a one-time alarm for the next morning and regularly scheduling your other repeat alarms.
For example, it is Sunday night so I had to set a one-time alarm for tomorrow morning. However, I was still able to set my regular repeat alarms for Tues/Wed and Thu/Fri.
I did test different number and combo of days, different times, etc. so this is the most likely answer. Hopefully will be patched soon.
04-20-2025 19:31
04-20-2025 19:31
How do I even do a new post on this?
Anyway I'm having the same problem. Any updates on when this can be fixed? It's my morning alarm daily for work, this is incredibly inconvenient.
04-20-2025 22:04
04-20-2025 22:04
are you guys attempting to fix this bug? i get alerts every single day of someone commenting on this thread asking what happened? is this even on the fitbit radar?
Monday
Monday
Do we know why this hasn’t been fixed yet? Does Fitbit not care?
yesterday
yesterday
Any update on this? It's been over a month since the original post and this is still an issue. Thanks!
3 hours ago - last edited 2 hours ago
3 hours ago - last edited 2 hours ago
Hi everybody, thank you four your feedback.
We have escalated this issue to a higher level department. As it has previously mentioned, any updates about this will be shared throught this channel. I appreciate your patience.
I really appreciate the contribution of those who have suggested some alternative solutions in the meantime.