bitTicker Notifications

[AndrewFitbit]

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.

[Graxlos]

As well as fixing external call notifications.

Marrma I agree with you 100 percent. My response to you was only a tip to show you that it could still work. I currently have the old version of the app on my private phone and the updated on my work phone.

[Marrrmaduke]

@Graxlos No prob. 🙂 I think many people will benefit from your tip. Not everyone knew about 2.19 after all. What I'd like to know now is how you managed to force your fitbit to pair with 2 different phones! I really would like a similar setup (phone/tablet in my case). 😮

[Graxlos]

I didnt. If you have the fitbit synced with one phone the other phone fetches the data from fitbit.com.

That is that I do have both phones paired with it, but I only enable bluetooth on one of them.

[Marrrmaduke]

@Graxlos. I see. That's what I thought. 🙂 Thanks!

[Zigzampow]

I went back to my pebble. I got a Fitbit to compete with my family, but that's the only benefit. My pebble integrates with Google health, myfitnesspal, etc.... And for 90 I get a lot more than for my 130 charge.

[Samnotwise]

bitTicker is not the real issue here.  The real issue is why cannot the FitBit and Fitbit Charge HR be updated to allow notification of text messages?  If it is a device limitation, please provide some detail - If it's simply FitBit is not willing to provide, please "man up" and say so.  Thanks.

[PR51]

@Samnotwise, agreed. Fitbit should be capable of implementing this feature pretty easy, but they don't want to do it because of their business plan. Fitbit needs to understand that their product are activity bands, not intelligent watches. Their business is to sell w/o customer service. Look what they did with the charge, why one waterproof and one sweat resistant? Have just one, waterproof, best out there and that's it.

[cmlegend]

2.19 works amazing with bitticker... Problem is now I'm stuck with that version until fitbit releases a 3rd party notification mod. Not sure if that will ever happen

[BabaBooey]

I assume this is just fitbit trying to get people to upgrade to new devices.

[dethknite]

Well it worked.. I upgraded to a garmin forerunner.

[Rich_Laue]

Nope @BabaBooey, it's a case of a problem where some people's wrist's was vibrating while making outgoing calls. Fitbit found and corrected this problem. Bit ticker was taking advantage of an open door the l that accidentally closed when Fitbit took care of the buzz.

[LakeWorthB]

I'm another one hoping that fitbit either ads support for text messages on Charge HR, or allows support for bitticker.  

[radyk]

Just finished reading this thread. Make no mistake about it, if Fitbit was interested in supporting these third parties regarding call notifications they would make it easier instead of more difficult or impossible. They would provide an API for such tasks that simply would not break upon a "bug fix". For whatever reason (generally money right) they are not supporting third parties that can add value to their product, at least in this regard. It is a shame, because wihtout the third parties or a great native solution by Fitbit some other company will come a long that gets it right. For me, notifications never seemed to work properly natively until I found Bitticker, that is odd considering I have a new android phone and one of the newest fitbit devices. If Fitbit cannot stay current with all the products and expand their official "supported devices" then let a third party take care of this aspect. It is cheaper for them and they can focus on the real future of these devices. Anyway, enough, for now simply delete your current fitbit app and install 2.19. It's as easy as a google and download although a few security settings may have to be temporarily changed. But it's no big deal at all despite Andrew's warning. 

[Rich_Laue]

Fitbit does provide an API, for anyone to access your data.

Bitticker was sneaking itself between the App and Fitbit. Yes at one time this worked until Fitbit fixed am unrelated problem with the atm buzzing during outgoing calls. 

All bit ticket needs to do is reformat the message so that it looks as if it is a caller id. This is happening because bitticker is sending an incorrect formatting of the message.

[Graxlos]

This is not true.

The API is broken. Using the Skype caller is broken as well.

No external callers work anymore.

[Marrrmaduke]

It's not Bitticker. I can't use any other external callers. It's Fitbit.

[ColinW]

Well this is interesting as an alternate option ...

https://www.kickstarter.com/projects/597507018/pebble-2-time-2-and-core-an-entirely-new-3g-ultra

I can't see my replacing with another FitBit device, after this behaviour by the FitBit team - which I don't see as anything other than cynical.

[Graxlos]

I was pretty close to preordering a pebble 2 time but I think I'll wait for
the reviews and pay full price if it's good. There are a few pretty cool
alternatives already.

[Rich_Laue]

@Marrrmaduke i suggest making sure yoir phone is compatable,  then looking at this help doc from Fotbit. 

@Graxlos the API is used for third party services to access your fitbit data through the internet. The api is strickly for wuthin the web, messaging happens within the phone.

I have a google sheet setup to read my fitbit data, this does use the api.

[Marrrmaduke]

@Rich_Laue External callers worked for me before the 2.20 update, so no, it's not my phone. Everything worked again when I downgraded to 2.19. It is the API like other users have reported. Fitbit can cripple their app the way they see fit. They can ignore their customers as well. But again, the customers can ignore Fitbit's products on the store shelf next time they shop for a new tracker. That's how I see it. I can't fathom how any company can improve their products if they ignore their community's plea so blatantly. It's a pity because otherwise I have enjoyed my Charge HR (with all its little bugs). I am not sure I enjoy the company's policy though. Just my 2 cents.