02-25-2019 01:41
02-25-2019 01:41
I have no activity goals and all features are disabled on the watch and app EXCEPT heart rate tracking, and sleep tracking, and also "core stats" in the watch menu.
If stand up or walk a few steps for the first the first time after midnight my versa vibrates and lights up displaying fireworks and colors to congratulate me of 0!I This is annoying and breaks my concentration.
The programming for the Fitbit OS and the Fitbit app reminds me of Ubisoft. Obvious oversights and issues caused by a seemingly complete inability to pay attention to detail or conduct thorough Q/A for software and features.
Answered! Go to the Best Answer.
02-26-2019 03:16
02-26-2019 03:16
How about changing the goal from 0 steps to 0 active minutes. You're less likely to get active minutes in your sleep than you are to get a step from random movement.
02-25-2019 02:58
02-25-2019 02:58
If you would rather not use the daily goal and its celebration, could you not change it to something very high, rather than zero, so that you never reach the goal and therefore don't get the celebration?
02-25-2019 14:21 - edited 02-25-2019 14:23
02-25-2019 14:21 - edited 02-25-2019 14:23
No, I don't want a goal.
There is no "disable goal" switch. I could turn off activity tracking completely but I want to track it. I just don't have any goal. I'm not trying to lose weight or be more active, I'm just tracking sleep because I have chronic severe insomnia.
A "disable goal" setting or setting it to 0 should have the same effect.
It's a bug, a bug report needs to be filed. That's why I'm posting. I want fitbit to be better.
02-26-2019 00:13
02-26-2019 00:13
But if you wait for fitbit to change things then you'll have a long wait (that's presuming they agree to make the change). Or, you can spend 30 seconds setting a high goal and your problem goes away.
I don't think it is a bug as such, it just doesn't work the way you would like it to. However, it is working as designed.
Your best bet might be to raise a feature suggestion for this change and the more people that vote for it the greater the chance that fitbit will make the change.
https://community.fitbit.com/t5/Feature-Suggestions/idb-p/features
02-26-2019 03:10
02-26-2019 03:10
What it comes down to is you can apply valid settings that cause unexpected and unusual behavior of the device.
Most days but not all it buzzes randomly some time after 12. Sometimes from standing up, sometimes from stretching, or maybe with a huge delay after I've already been walking around my house. The latest I remember it going off was 12:47am!
The worst however is it's even done it after I laid down to sleep and woken me up! (After <1 hour of sleep, but the startle awake can take quite a while for someone with insomnia like me to fall back asleep)!
It's obviously unintended operation. They didn't even think about what the possible side effects of issues of someone setting the goal to 0 could be.
02-26-2019 03:16
02-26-2019 03:16
How about changing the goal from 0 steps to 0 active minutes. You're less likely to get active minutes in your sleep than you are to get a step from random movement.
02-26-2019 18:26
02-26-2019 18:26
I thought of that before but (incorrectly) concluded that it would make the main stat in the app show active minutes instead of steps for whatever reason... (this was when I'd first gotten the Fitbit Versa in November 2018. Maybe that was how it worked then..?)
I set it to active minutes now since that's never gone above 0 so it should stop notifying me...
(I'll let you know if that works).
Although that doesn't change it's status as a bug, because if you track even ONE exercise that number will increase right? Then you'll have nothing to switch to to prevent the notification. (Which is probably the case for the vast majority of users).
It needs an on off switch for each goal celebration, that would allow anyone to customize it for whatever workout schedule they have.
03-05-2019 18:30
03-05-2019 18:30
That does work to stop the notifications but again please keep in mind my previous post on why this most likely won't work for anyone else.