04-27-2017 23:04
04-27-2017 23:04
Hi all,
I have been patiently awaiting the firmware update for my Blaze to enable
it to receive notifications from my windows 10 phone. I know that Beta testing
has been going on for a while now, but I cant find any information regarding
its general release to users. It was hinted that the release would take place
during April this year, which we are now at the end of.
So my question is. Does anyone know the current situation ?
Is the testing a failure, being delayed, abandoned, or due for release any
second now, as of 28/04/17
Answered! Go to the Best Answer.
04-28-2017 05:42
04-28-2017 05:42
Hi, @SunsetRunner, you can read more about this on the Windows 10 forum. I believe that the testing has been quite successful, but there are some further fixes required (mainly on Microsoft side) for the release to be stable enough to offer it more widely. I think the Fitbit team are still hoping notifications will be generally available some time in May, but my understanding is that that will depend partly on the required updates/ fixes from Microsoft being implemented first.
I am looking forward to this too!
Sense, Charge 5, Inspire 2; iOS and Android
04-28-2017 05:42
04-28-2017 05:42
Hi, @SunsetRunner, you can read more about this on the Windows 10 forum. I believe that the testing has been quite successful, but there are some further fixes required (mainly on Microsoft side) for the release to be stable enough to offer it more widely. I think the Fitbit team are still hoping notifications will be generally available some time in May, but my understanding is that that will depend partly on the required updates/ fixes from Microsoft being implemented first.
I am looking forward to this too!
Sense, Charge 5, Inspire 2; iOS and Android
04-28-2017 05:59
04-28-2017 05:59
Hmm,
It all sounds a little like "ping pong"
If my memory serves correctly, Fitbit initially announced that notifications to trackers from windows phones were not possible due to missing Gatt server software.
Earlier this year, Microsoft updated the phones software to include the missing Gatt
server. Fitbit then stated that notifications still would not be possible, as there was missing software on the trackers,
.Having resolved this ( although in theory it never existed, re. re my first senence) its now
pingponged back to Microsoft to resolve.
Had I known this issue at the time, I would not have opted for the combination I did.
So we will have to wait another month in the hope of resolution.
Many thanks for your reply
04-28-2017 06:04
04-28-2017 06:04
@SunsetRunner, if you read through the more than 1000 replies on this thread which follows the beta testing you will see that both Fitbit and Microsoft have been very hard at work on this and it is not as simple as you say.
When this does come available, if I understand it correctly, your phone will need a further update from Microsoft as well.
Sense, Charge 5, Inspire 2; iOS and Android
05-20-2017 14:02
05-20-2017 14:02
I recently updated the firmware on my 950 ( sorry cant remember the version number ) and then checked the microsoft changelog for this version. Particular mention is made to fitbit devices in the changelog list
eg, pairing and Notifications. omg at long last its finaly nere the update we have all been waiting for. ER, no it isnt !
Did all the usual deleting device from phone, re pairing, syncing etc etc, called my mobile from another phone, Still no notifications !
The April update that was delayed for a month still has 2 weeks before its June, Im not feeling
optimistic.
08-07-2017 05:27
08-07-2017 05:27
I had a Microsoft Band and it went bad. Had warranty and went by Microsoft store. Since its no longer available they sold me on the FitBit Blaze and ASSURED me it was the same, including display calls, text and calendar notifications. Well, it does not do that. Has anyone heard what to do next? I have a Lumia 950, which I really like. Phone is updated to the latest. Should I return the Fitbit Blaze? But what would I get? This stinks!!!
08-07-2017 07:22 - edited 08-07-2017 07:25
08-07-2017 07:22 - edited 08-07-2017 07:25
This is not the strongest selling point of this tracker...
I noticed following limitations, however:
1. They don't work while syncing
2. If other non-BT 4.0 LE device is connected
3. Should you go outside of connection range - it won't recover.
4. If they stopped functioning only reconnect helps. Even better to remove device, reboot phone, then connect again.
Conclusion: Yeah, it is beta. Non-reliable at all!
08-08-2017 11:00
08-08-2017 11:00
I've been waiting 2 years.
08-08-2017 12:24
08-08-2017 12:24
Sorry for your wait @SunsetRunner, it was only this year that Microsoft decided to add the proper server to allow notifications to go out to Fitbit and several other trackers from other companies.
Things have not been a smooth as hoped for. Fitbit and Microsoft are still working on the bugs.
08-08-2017 13:24
08-08-2017 13:24
Hey there @Edfutbol, @VoronServer and @SunsetRunner! Just as @Rich_Laue mentioned, Fitbit is continuously working to have the notifications option working with Windows apps. At the moment, there's a Beta App already that users are testing, so when it gets implemented you can have this option properly enabled.
Your patience and understanding is appreciated, while this gets implemented.
Want to get more active? Visit Get Moving in the Lifestyle Discussion Forum.
12-15-2017 05:18
12-15-2017 05:18
Hi,
anything new? I can transfer the test message from my MS 750XL to the Blaze but no notifications come through. Allowed the fitbit app to access notifications. Rebooted both devices, removed and re-coupled. Nothing
Rainer
12-16-2017 12:22
12-16-2017 12:22
A warm welcome to the Community @Rainer.Prem! Thanks for the details that you've mentioned. Currently, Microsoft Lumia 750 isn't a supported device yet. This may be the reason why the notifications aren't working, Fitbit is continuously testing new devices to be added to the list.
Your understanding is truly appreciated.
Want to get more active? Visit Get Moving in the Lifestyle Discussion Forum.