10-19-2020
20:31
- last edited on
11-12-2020
13:24
by
MatthewFitbit
10-19-2020
20:31
- last edited on
11-12-2020
13:24
by
MatthewFitbit
I’ve updated the app (and my phone-an iPhone) multiple times over the past few months and CANNOT find where to set vibrate alarms through the app itself—I can suddenly (as of a few months ago) only do it through the watch itself (Fitbit charge 3).
it USED to be that I would open the app, click the top left icon (my photo) and then select my device (charge 3) an the option to set an alarm was there. Well, it hasn’t been for months, I’ve searched the app countless times and have consulted google AND this forum on multiple occasions and there have been NO answers.
I don’t WANT to be forced to set an alarm through my smart watch itself, I set all other alarms via my iPhone (11) and don’t want the inconvenience of having to use my actual Fitbit to set one.
10-19-2020 20:44
10-19-2020 20:44
As you have discovered, alarms for Charge 3 must now be set on the watch, not in the app.
10-20-2020 07:57
10-20-2020 07:57
Oof, I was really hoping I just couldn’t find it. It just seems goofy to make setting alarms harder/less accessible than easier/more accessible.
10-20-2020 10:10
10-20-2020 10:10
@Brookeeellis Welcome to the Fitbit Community!
Thank you for your feedback regarding the new alarms . As @JohnnyRow mentioned this option was changed from the app to the tracker itself but you can share your idea in our Feature Suggestions board. Search for the idea first to see if one already exists so you can add your vote. The more votes an idea gets the more likely the developers will try to implement it.
Let me know how it goes.
If a post helped you try voting and selecting it as a solution so other members benefit from it. Select it as Best Solution!
10-22-2020 14:01 - edited 10-22-2020 14:07
10-22-2020 14:01 - edited 10-22-2020 14:07
"You can share your idea in our Feature Suggestions board. ... The more votes an idea gets the more likely the developers will try to implement it."
Well, except for the fact that this topic, with 466 upvotes, has been set to "Status: Not currently planned" and the thread locked.