Versa notifications not being consistent

[Littlemis]

Is anyone else having the same issue as me? The notifications for text messages and other notifications were working on my Versa. They now keep stopping. I have to then go into notifications on my app and it keeps saying phone restart. I restart my phone and then it works for a while, then it stops again. I should not have to keep restarting me phone every hour for the notifications to work. It seems Fitbit have quite a few small issues with the Versa.

Moderator edit: subject for clarity

[aaandh]

I have my Versa connected to my phone, and it suddenly keeps telling me that the Versa can not be found. I have tried all the "steps" on your link to no AVAIL. I also took a screen shot of the error i am getting on my phone, and tried to attach it to this, but your other link shows steps that do not appear for me. I only just got this Fitbit yesterday....might be returning. I tried to see if there was an app update, and the App doesn't even list the VERSA in its supported trackers list. Does Fitbit know what it is doing???

[Pga2rplayer]

That’s good news and happy to hear. I’ve got an iPhone 8 Plus and was having those issues.

They pushed through an update to their app yesterday so I’m hoping it helps.

Sleep tracking is no longer an issue and I am receiving all of my text notifications.

Fingers crossed.

Cheers 

[Pga2rplayer]

Fitbit did push through an update yesterday. Since the update I’m receiving all my texts and calls and the sleep tracking now appears each morning when I log on.

Fingers crossed. 

[WoodieHouse]

I have done every single thing on the list in the article you referenced.Repeatedly. I've even done a factory reset on the Versa and that didn't help. I've gotten a couple test texts, but not many. It still doesn't won't stay paired with my phone's Bluetooth, so it won't give me notifications for calls or texts. On the rare occasion I can receive a test text on the Versa, if I turn off the Bluetooth and turn it back on, it won't even connect for a second. Like someone else said, you have to pair it again, and it MAY work for a few minutes until it disconnects again. I'm on Day 2 of trying to get this to work and I'm ready to return it to Best Buy. It just won't do what it's supposed to and I'm beyond frustrated. My phone is Moto G5 Plus running Android 7.0 with completely updated software. 

[Mladen]

And, my notifications are gone, again. New day, new Fitbit app update, this time they're gone for good. I deleted and re-installed app several times, cleared chashe, all that. Now, it's just permanent "Restart your phone to restore tracker bla bla message"

I guess I will give them a week or so to sort this out then I am returing my Versa. I am only willing to wait that long as I really like this tracker... (only if it did what they advertized it would do)

If anyone from the Fitbit App development team is reading:... Versa 32.32.4.19 Firmware. BlackBerry KeyONE model BBB100-1, running Android 7.1.1 Android Security Patch Level March5, 2018

[lukebach]

I was having the same problem...the problem for me was my phone was on silent.  When your phone is on silent, the app will not push notifications to the versa.

[ghammer1980]

I think that is a "feature", a horrible one at that. If my phone is on silent, I'd rather have notifications going to the phone.

[Lufalulz]

For Android phones, there's an option to allow the Fitbit App to bypass the Do not Disturb mode. Meaning that it will capture all the notifications and send them to the watch.

However, while the phone is in Do not Disturb mode, is very likely that the other apps won't send you notifications and that way the Fitbit App won't have anything to copy to send to the watch.

[dianewordsmith]

And my text notifications are no longer working. I've tested several times. Phone calls come through to the Versa but text notifications have stopped. I checked all the settings, nothing has changed and everything is as it should be. Can someone advise why this is happening and how to resolve it?

[dianewordsmith]

Ok. As noted in the article below, I quit the Fitbit app, turned off bluetooth, waited 10 secs, turned it back on, opened app and did a sync. A test text came through. But why is this happening repeatedly? We shouldn't have to jump through these hoops repeatedly to have the device function as it's supposed to. 

http://help.fitbit.com/articles/en_US/Help_article/1610/?q=Notifications&l=en_US&fs=Search&pn=1#trou...

[MikeyP181]

I got my Versa yesterday and have had to un-pair/re-pair multiple times to get push notifications working again.  I've had similar issues with the Flex 2 and Charge 2.  Here's what I've found, hopefully it helps others and gets noticed by the Fitbit devs:

It appears that any of these devices paired with an Android phone may be at risk, where as soon as you connect a second Fitbit to the same phone they both stop receiving notifications.  I found a help article that alluded to this, stating that push notifications on Android will only go to one device at a time, whereas Apple phones will push to all connected Fitbits.  This is disappointing since I'd like to swap out my Versa with my Flex 2 from time to time for different activities.  In my case the notifications would not push to either when both were connected. 

Specific to my Versa, several times it would be receiving push notifications fine and then randomly stop working.  The most consistent fix I've found for this is to follow these steps in this order:

1) Un-pair the Versa from the Fitbit app (go into the device settings and tap the trashcan icon)

2) Turn phone Bluetooth off and back on

3) Within the phone's Bluetooth settings, choose Forget on the Versa

4) Go back into the Fitbit app and re-add the Versa

5) Verify everything is working by using the test phone call notification option within the Notifications settings of the Fitbit app.

I tested the above steps with the Flex 2 and Charge 2 as well, seems to work every time any of them stop receiving push notifications, but again only one device can be paired at a time.  Hopefully they can address this with an app and/or firmware update soon, maybe with the big May update that's coming.  

[MikeyP181]

Let me just add that when you do have more than one device paired at a time you have to be sure to un-pair and forget ALL of the devices before re-adding your preferred device.  

---

@MikeyP181 wrote:

I got my Versa yesterday and have had to un-pair/re-pair multiple times to get push notifications working again.  I've had similar issues with the Flex 2 and Charge 2.  Here's what I've found, hopefully it helps others and gets noticed by the Fitbit devs:

It appears that any of these devices paired with an Android phone may be at risk, where as soon as you connect a second Fitbit to the same phone they both stop receiving notifications.  I found a help article that alluded to this, stating that push notifications on Android will only go to one device at a time, whereas Apple phones will push to all connected Fitbits.  This is disappointing since I'd like to swap out my Versa with my Flex 2 from time to time for different activities.  In my case the notifications would not push to either when both were connected. 

Specific to my Versa, several times it would be receiving push notifications fine and then randomly stop working.  The most consistent fix I've found for this is to follow these steps in this order:

1) Un-pair the Versa from the Fitbit app (go into the device settings and tap the trashcan icon)

2) Turn phone Bluetooth off and back on

3) Within the phone's Bluetooth settings, choose Forget on the Versa

4) Go back into the Fitbit app and re-add the Versa

5) Verify everything is working by using the test phone call notification option within the Notifications settings of the Fitbit app.

I tested the above steps with the Flex 2 and Charge 2 as well, seems to work every time any of them stop receiving push notifications, but again only one device can be paired at a time.  Hopefully they can address this with an app and/or firmware update soon, maybe with the big May update that's coming.  

---

[ycwkpp898]

I am having the same problems, bought the fitbit versa today set it up. and no notifications. 

I have a Honor 9 on 8.0.0 firmware. latest app for fitbit too.

I have turned off Bluetooth and uninstalled app and nothing. 

[kb1086]

Notifications are really inconsistent. Sometimes I get them right away, sometimes after a few minutes, sometimes not at all. 

Sometimes I have to manually sync the Fitbit, and then they start working again. Other times I have to force stop the Fitbit app.

Some people say that you can't have multiple devices connected via Bluetooth, but that seems like a huge oversight. I should be able to listen to music with my headphones AND get consistent notifications from my Fitbit.

It's really frustrating that this isn't working well. It's one of the main reasons I bought the Versa.

My hardware:
Motorola Droid Z Force (Android 7.1.1)

Fitbit Versa Special Edition

LG HBS910 bluetooth headphones

[r1skbreak3r]

I do find it ridiculous that Fitbit had the same issues with the Blaze, and then the Ionic, and still haven't figured out how to get notifications working reliably. Mine have been mostly working this week, but do stop randomly with no error message, so I have to go through the process of toggling the various settings (keep-alive/always connected) till it decides to work again.

I've used various smart watches/fitness trackers from Microsoft, Garmin, Samsung and Pebble, and have had virtually no issues with those. Fitbit is the absolute worst when it comes to notifications! Even when it is working, the functionality is way behind what is possible. I don't just want to see messages, I want to delete them, dismiss them on the phone, or do a quick reply.

Come on Fitbit, you have great hardware and an otherwise great app, just fix this one issue and you'll have a lot of happy users!

[MikeyP181]

---

Amending my previous posts, I've found a way to do this in fewer steps:

1) Turn phone Bluetooth off and on

2) Forget the device in phone Bluetooth settings (make sure it disappears from the list)

3) Sync the device within the Fitbit app

 Doing this eliminates the need to delete and re-add/set up again in the app, so all settings are retained, and the device will automatically reappear in the phone's Bluetooth settings as connected, then notifications should resume working.

@MikeyP181 wrote:

Let me just add that when you do have more than one device paired at a time you have to be sure to un-pair and forget ALL of the devices before re-adding your preferred device.  

---

@MikeyP181 wrote:

I got my Versa yesterday and have had to un-pair/re-pair multiple times to get push notifications working again.  I've had similar issues with the Flex 2 and Charge 2.  Here's what I've found, hopefully it helps others and gets noticed by the Fitbit devs:

It appears that any of these devices paired with an Android phone may be at risk, where as soon as you connect a second Fitbit to the same phone they both stop receiving notifications.  I found a help article that alluded to this, stating that push notifications on Android will only go to one device at a time, whereas Apple phones will push to all connected Fitbits.  This is disappointing since I'd like to swap out my Versa with my Flex 2 from time to time for different activities.  In my case the notifications would not push to either when both were connected. 

Specific to my Versa, several times it would be receiving push notifications fine and then randomly stop working.  The most consistent fix I've found for this is to follow these steps in this order:

1) Un-pair the Versa from the Fitbit app (go into the device settings and tap the trashcan icon)

2) Turn phone Bluetooth off and back on

3) Within the phone's Bluetooth settings, choose Forget on the Versa

4) Go back into the Fitbit app and re-add the Versa

5) Verify everything is working by using the test phone call notification option within the Notifications settings of the Fitbit app.

I tested the above steps with the Flex 2 and Charge 2 as well, seems to work every time any of them stop receiving push notifications, but again only one device can be paired at a time.  Hopefully they can address this with an app and/or firmware update soon, maybe with the big May update that's coming.  

---

---

[Littlemis]

I never had two fitbit devices paired or any other blue tooth device and my notifications were still not working ad expected.  As soon as I restarted my phone the notifications would work for maybe half an hour and then an error would show in app saying a phone restart was required for notifications to work.  It was so frustrating and a shame because I like the look and feel of the versa but if it doesn't do the simple features then it's not great in my opinion.  Fitbit couldn't not provide any help with this issue and others I was having so I had to return it.

[ChimpishUK]

Hi, just as purchased the Versa SE I'm also using a BB Keyone.

Have you resolved your issues and are there feature limitations? I see the Keyone isn't in the list of supported devices.

[Mladen]

I have resolved my issues with KeyONE, now everything is working as it should. I did a factory reset on the phone to make sure no app is interfering, and after I re-installed the Fitbit app, everything worked.

Only problem I can see now is that if I restart the phone, I have to disconnect, forget on the Bluetooth and then re-connect Versa to the Fitbit app, but it's not a biggie I guess... how often do you need to restart the phone anyway.

Still, we can hope that Fitbit software division will catch up with its hardware. I am not sure how many people would set aside a whole day to fiddle with this problem and how many would be willing to format the phone... Most people would just see that the notifications just don't work as advertised and return the tracker.

[bri_cheese]

Following.  Same issue with Versa + Samsung S8.