Versa 2 - Alexa - "Connection Lost" - must sync Fitbit to use?

[kiapple]

I just got my Versa 2 a couple days ago and I am having trouble connecting to Alexa. When I try to connect, I get an error message (CONNECTION LOST - Sync device in Fitbit mobile app. Let app run in the background to use Alexa"

I have checked my settings for both Fitbit and Alexa (I have an Iphone XR) Both are set to Background App Refresh, Location - Always and Fitbit is set for All Day Sync.

My question is: Do I need to open the Fitbit app on my phone every time I want to use Alexa? If I open the Fitbit app and sync - then Alexa will work. Do I have my settings right or is this how Alexa works on Versa 2? I'm a little bummed because I thought I only had to push the button on Versa 2 and it would work. It's just as easy to open the Alexa app and use it on my phone.

[Rich_Laue]

Spoiler

Ocaisionly I get this message, then when I tap the Alexa icon on the screen I find Alexa now works. 

[Ferigm1]

I'm not force closing the app, I have it running in the background, and I still need to open the app, have it on the screen in order to be able to use Alexa. I didn't have this problem at the beginning. I've reset my home wifi, my phone and turned on and off my fitbit. Any ideas on how to fix this? It's very annoying getting the "connection lost" label every time I want to use Alexa and the fitbit app is not in my phone's screen. 

[Sunshinestlmo]

I'm having the same issue and it's very annoying. I could just use Google on my phone. It's faster. I am going to pay attention to if I am force closing FitBit by swiping up because I do this all day.  I will see if that makes a difference.

[Captroper]

I ended up just returning mine and getting a galaxy watch active 2 instead. The issue was so frustrating every single day. The active 2 has had none of those issues, though the battery life is significantly lower... like 2 days instead of 4 or 5. So, everything's a tradeoff I guess. 

[tahoedee]

Exactly HOW do you do that on an Android device?  I'm ready to return this piece of garbage Versa2 and go back to my Samsung Gear Fit2....  

I can't even SYNC the stupid watch to the stupid fitbit app - I am getting the spinning wheel.

I have Alexa actually OPEN and on my screen on my phone.  I have Fitbit OPEN and on my screen on my phone.  NOTHING works.  I purchased this SPECIFICALLY because of the Alexa feature.  It's going back to Amazon with a bad review tomorrow.

[adelrosso74]

I returned Fitbit and I bought a refurbished Gear S3 Frontier at half
price. Another planet! Never a disconnection. Very happy!

[tahoedee]

This watch is a real pain - it disconnects, stops syncing, and the Alexa feature is hugely unstable.  I'm going to return mine - this after following all the instructions everyone gave.  I'm going back to my Samsung Gearfit 2 Pro which ALWAYS worked perfectly.

[Rich_Laue]

@tahoedee was support able to help after you contacted them? 

[MandyLynnJ]

I have it running and still says it isn't able to connect 

[Lybra975]

Usually either turning bluetooth off and on helps fix. If not then going to the app and force closing does. Shouldn't have to do this daily. Also, I have the Note8 which is just about the only Samsung phone that's not supported. Why?? Who knows. I previously had the Charge 2 and that began causing issues for everyone. Couldnt read texts so I gave in and upgraded. Now this?? My god Fitbit, you could at least make your products work properly. 

Sent from Yahoo Mail on Android

[MandyLynnJ]

I have a note 9 and no matter what I do it doesn't work I got this just for Amazon.  I am about to call the company.  I cant find where to keep the app running in the background either

[spuck20]

Why is this thread marked as answered?  Keeping app open isn't the solution.  I can get mine to work by forcing closed the Fitbit app, reopening, and then synching.  After that, Alexa on the Versa 2 works but for only about 20 minutes.   Have all-day sync on, but it frequently goes hours without syncing.  

Come on, Fitbit.  I really want to like this device and bought it against my better judgment based on the garbage Fitbit pulled with the Charge 2 screen cracks and green lights lock-up of death, and it's looking like I didn't learn my lesson.

[Rich_Laue]

@spuck20 threads get marked as having a best answer by the original poster that started the thread, it is the original poster that gets to decide which answer was the answer that fixed their issue. They are not speaking for anyone that has jumped into their conversation. If a user wants individual help then they really should start their own individual thread, rather than jump on a thread that already has been answered and then complain that it has not been answered for them. 

My question is why do users who have a problem, and find that the best answer does not work, even decide to jump into a solved thread instead of creating their own thread with their own issue. It also makes it confusing when one is trying to help 5-8 people with 5 -8 slightly different issue.  At least one poster above is asking for help with notifications , which has nothing to do with the subject of the thread. 

Fitbit Charge 2 was pulled because the Charge 3 was released and replaced the Charge 2  it is the same for automakers who come out with a new model and stop manufacturing the old model. 

As for Alexa on the phone, 

You mention Keeping  app open, what app, is to be left open?

For Alexa or notifications to work, as the best answer points out, the Fitbit app has to have permission to run in the background. Having the Fitbit app open is a good for troubleshooting a problem with Alexa or notifications. Once a user gets it working they can move the Fitbit app to the background, if then Alexa fails the user needs to check the Fitbit's app permissions. On android under phone settings - Apps - Fitbit - Battery - Allow Background use. One also wants to disable power management for the Fitbit App. Some Android phones will need this disabled, once they get Alexa to work, they can enable this and check which way to leave optimization checked. 

If Alexa works with the fitbit app in front and open but fails to work when the Fitbit app is moved to the background, the user needs to check the fitbit app's permissions. 

[MandyLynnJ]

actually all my permissions were correct.  I had to delete everything off my phone and reinstall it.  I figured it out on my own.  I knew how to set up all my permissions.  

Moderator edit: format

[ChelseaFay]

Unfortunately that does not fix the issue. I have fitbit app in the background on at all times and I have it set to all day sync as well as allowing it to use background app refresh in my iPhone settings. Yet every time I try to use Alexa I have to go back into the app and manually sync it before it connects (which defeats the purpose of having Alexa on the fitbit)

[LisasClanOf4]

I received this Fitbit Versa2 for Christmas to replace my Blaze(love my Blaze but thought having Alexa on my wrist + ect would be better).

I have a Samsung Note 9 & have this same problem. Syncing doesn't help. Rethinking on going back to Blaze...

[Rich_Laue]

This sync message is a little deceptive. 

For Alexa to work, the Alexa App needs to talk to the fit it app on the phone. Then the app sends the audio to the Internet. Waits for a response from Amazon and sends it back to the Alexa app on the tracker. 

A sync only confirms that this may be possible. 

For this to happen, the Fitbit app needs to have permission to run in the background while the phone is locked. Also on android the Fitbit app will need to be in main memory. The app will not run in background of loaded on an SD card. 

Check the Fitbit Help for notification issues and Alexa help. 

[Jmarie2192]

I have this same problem but it happens to me regardless of it the app is open in the background. I never swipe away apps and Fitbit is always running in the background but after awhile I get the connection lost message when trying to use Alexa. I have to go back to the Fitbit app which was still running in the background and force it to sync to get Alexa to work. I have verified that all day sync is on. Why do I have to manually sync my Fitbit to get Alexa to work? This feature is useless if I have to go to my phone to sync every time I want to use Alexa. I might as well use the Alexa app on my phone or stick with Siri 

[Rich_Laue]

@Jmarie2192 do you get all notifications that your supposed to get? 

I assume you have checked the phone settings for background permisions. I have noticed on my android that if the screen locks while the Fitbit app is in front, a firmware update fails an often notifications stop working. 

I also find that if Alexa or notifications stop, rarely happens, a restart of phone seems to work. 

To me this is not a big issue since android still has a memory management issue and the phone needs to be restarted ocaisionly. Android also reminds me to restart the phone. 

[Jmarie2192]

As far as I know I’m getting all of my notifications. There is definitely something wrong. All of my permissions are set correctly from both phone side (iPhone) and fitbit side.
I try to use Alexa and it gives me the connection error. I go back to make sure Fitbit is still running in the background and it is. I have to manually sync and Alexa will then work. Just now I went to grab my Fitbit from the bathroom from when I showered earlier today and now it’s telling me to go to the app to set up Alexa again. This thing is so aggravating. Not only is my Fitbit Pay not accepting my bank yet but this now? Alexa and Fitbit Pay were the two reasons I upgraded from my original versa and now I basically have a more expensive versa 1. Both upgrades don’t work properly. Disappointed ☹️
Joy