03-10-2016 17:34 - edited 03-11-2016 14:40
03-10-2016 17:34 - edited 03-11-2016 14:40
Fitbit Update 3/11/16:
Hey all,
I realize for most of you bitTicker was an important part of your experience with using Fitbit. With each iteration, we definitely aren't looking to limit functionality. Quite the opposite really, we're always looking to improve. Receiving notifications from various apps can be a huge factor when it comes to using activity trackers or smart watches and there's certainly potential for this feature to exist. If this is something you're interested in, I'd suggest voting for this notifications Feature Request. The Feature Request board is a great place to get the attention of our engineers and developers.
I wouldn't recommend reverting the Fitbit app version to 2.19, especially since you don't always know the source of the download.
In the meantime, looks like bitTicker is still working for @homebound:
homebound wrote:I have a Blaze and my BitTicker is working fine. I use it as "text" replacement not as "phone" replacement.
FitBit 2.20.1 , Blaze Firmare 17.8.102.7. All notifications are coming trough as they always did.
Hope this helps. Remember to vote for that idea to bring more attention to it! 🙂
Fitbit Update 3/10/16:
Hey everyone,
Here’s the situation with bitTicker.
Though we’re not familiar with how bitTicker works, the recent bug fix for outbound call notifications for the Fitbit Android app may have caused bitTicker to stop working.
This was a bug fix, not an intentional block of bitTicker. Since we don’t support bitTicker, there are no plans for reversing the bug fix.
You can reach out to bitTicker directly for further information.
03-10-2016
03:52
- last edited on
03-10-2016
10:19
by
MatthewFitbit
03-10-2016
03:52
- last edited on
03-10-2016
10:19
by
MatthewFitbit
i use BitTicker on my phone, until this morning it worked well.
now with the new FW i see that i get no notification from the phone.
BitTicker seems to be working fine, but i think fitbit FW was changed so now it's not supporting BitTicker anymore.
Moderator Edit: Clarified subject
03-10-2016 04:16
03-10-2016 04:16
According to the bitticker site this is not going to be resolved either
03-10-2016 04:21
03-10-2016 04:21
yes, i just saw it now.
also talked to BitTicker over the mail.
this is bad.
until fitbit can give the same solution as BitTicker does, they should not block it.
03-10-2016 06:45
03-10-2016 06:45
03-10-2016 07:31
03-10-2016 07:31
Extremely disappointed that my BitTicker app stopped working after the latest FitBit update FitBit, please either revert your notification code, or improve your product by offering txt notifications as a feature! I was happy to find BitTicker because it made a good product great--it notified me on my Charge HR when I would get a txt--a feature glaringly missing in the software....If you're reading this and recently lost this ability too, please add to this thread! Very dissapointed.....
03-10-2016 08:16 - edited 03-10-2016 08:21
03-10-2016 08:16 - edited 03-10-2016 08:21
@dvdscr wrote:i use BitTicker on my phone, until this morning it worked well.
now with the new FW i see that i get no notification from the phone.
BitTicker seems to be working fine, but i think fitbit FW was changed so now it's not supporting BitTicker anymore.
The FW isn't what breaks it, it is the app update. I am still on v102 but updated my app before remembering that it could break BitTicker. I saw the notice from the app developer this morning. I really hope Fitbit adds this feature ASAP!
03-10-2016 08:53 - edited 03-10-2016 08:54
03-10-2016 08:53 - edited 03-10-2016 08:54
Also disappointed that this was blocked by way of the app update. Can't fathom why Fitbit would do this. Please remove the block of this very useful function.
03-10-2016 10:10
03-10-2016 10:10
03-10-2016 10:24
03-10-2016 10:24
I've moved this discussion to its own thread, since it is not related to the recent firmware update.
03-10-2016 10:44
03-10-2016 10:44
@MatthewFitbit I see you changed the title to "bitTicker integration not working"
What I'm trying to understand (and I'm admittedly frustrated), is whether it's "not working" or rather "functionality that has been disabled by fitbit." Is this a bug that needs to be fixed, or is this a design decision? The app developer's site seems to indicate the latter...
03-10-2016 11:00
03-10-2016 11:00
03-10-2016 11:43
03-10-2016 11:43
@McG_32 Currently the Blaze, Surge and Alta are the only Fitbit products with SMS notifications. As far as I know (or at least since I bought mine in December) the Charge HR has never advertised having text notifications, only call notifications, even with V102.
03-10-2016 12:37
03-10-2016 12:37
@kalimm That's true from the standpoint of their standard ad materials, but fitbit directly, in-app supported third-party notification extensions (for lack of a better word); it didn't take a lot of research/effort to find that SMS notifications were supported through bitTicker. If bitTicker was a root-required hack, that would be a different story.
All that said, I'm still waiting to hear if this is a bug or an intentional design decision. If it's the latter, I'd like to understand why they would choose to remove functionality.
03-10-2016 13:06
03-10-2016 13:06
Fitbit dod not take into consideration, or test bittick before releasing their firmware, it the same as when Android released v6.0, and this release caised Fi5bi5 issies.
03-10-2016 13:54
03-10-2016 13:54
Well this sucks.
Fitbit is really trying to dissapoint their userbase. Sorry to say this is the last Fitibit product I will ever own
03-10-2016 14:17
03-10-2016 14:17
03-10-2016
15:29
- last edited on
03-10-2016
15:44
by
AndrewFitbit
03-10-2016
15:29
- last edited on
03-10-2016
15:44
by
AndrewFitbit
Only thing we can really do is bring attention to this. If it truly is just an app issue, I might have to install the older APK. There's no reason to half remove this feature.
The Charge HR is a phenominal product. Given that the third party integration is still there, I'm wondering if this is a case of forgetting to uncomment code.
Moderator edit: content
03-10-2016 16:15
03-10-2016 16:15
03-10-2016 16:31
03-10-2016 16:31