09-15-2019
05:19
- last edited on
09-19-2019
11:52
by
AlessFitbit
09-15-2019
05:19
- last edited on
09-19-2019
11:52
by
AlessFitbit
Anyone get their versa 2 yet and can't connect to Alexa? I've got a ticket in but it's so frustrating to have a brand new watch and unable to use the biggest reason you decided to upgrade
Moderator edit: title for clarity
09-15-2019 06:11
09-15-2019 06:11
Hi @theminders, good to see you in the community.
What issues are you exactly having with Alexa? Have you signed in by doing the following - Account - tap on Versa - Tap on the Alexa tile and sign in? What happens then? If you could be a little more specific that would be helpful.
Thanks.
09-15-2019 06:18
09-15-2019 06:18
09-15-2019 15:58
09-15-2019 15:58
Hello...I am having the same issue. When I click on the "login with Amazon" button I receive the error "unable to connect. There was an error connecting to your Amazon account. Please try again." I followed the troubleshoot option and cleared my cache and cookies but that still didn't work.
09-15-2019 16:02
09-15-2019 16:02
09-16-2019 17:57
09-16-2019 17:57
Same here. There are a couple of threads on Fitbit community now. I tweeted support as well. Can you reply and let me know if you happen to be using an Android phone and live in Canada? So far everyone I have engaged with on this issue is from Canada and using an Android. I would be curious to validate this.
09-16-2019 17:59
09-16-2019 17:59
09-16-2019 18:04
09-16-2019 18:04
Same exact issue. Honestly, this is getting ridiculous. I've contacted them every single day since Friday night. No answer. Wait for an email. So disappointing. The main reason I updated my Versa is to be able to use Alexa!
09-16-2019 18:13
09-16-2019 18:13
Lol, there goes the Canada theory. Thanks for letting me know. I appreciate it.
I read on another thread that a user was told that the S10 is not supported. I have a Note 10+ and a OnePlus 7 Pro. I get the same error with both. I tried with an old iPhone, and it worked. 🤢
Hopefully more people complain so that Fitbit starts to take this seriously.
09-16-2019 18:18
09-16-2019 18:18
09-16-2019 18:20 - edited 09-16-2019 18:21
09-16-2019 18:20 - edited 09-16-2019 18:21
@Skip501 Just out of interest have you tried setting up/logging in over cellular instead of WiFi (I notice in the screenshot you're using WiFi). I had an issue with Alexa voice replies (everything else worked), it turned out to be an issue with my connection as when I switched to cellular it worked fine. Rebooting my router also fixed it over WiFi, so worth a try if you haven't already done so.
09-16-2019 18:28
09-16-2019 18:28
09-16-2019 18:28
09-16-2019 18:28
@N8teGee Thank you. Yes, I tried that. I have no connectivity issues on WiFi or cellular. I also tried a factory reset on the Versa 2 and even a factory reset on my OnePlus 7 Pro. I found a support article by Fitbit that suggests clearing the browser cookies (https://help.fitbit.com/articles/en_US/Help_article/2009#troubleshoot). That didn't work (I didn't think it would). I have tried everything. I believe that the problem is on Fitbit's side. This is not a user issue.
09-16-2019 18:30 - edited 09-16-2019 18:31
09-16-2019 18:30 - edited 09-16-2019 18:31
@theminders please let me know if cellular data worked for you? I just tried cellular again and I still got the same error. Disregard...just saw you replied already.
09-16-2019 18:30
09-16-2019 18:30
09-16-2019 18:32
09-16-2019 18:32
09-16-2019 18:39
09-16-2019 18:39
@theminders For what it's worth mine seems to be without issue at the moment. I know this sounds long winded, but have you tried logging in with a different Amazon account or even creating a new one to try and log in with. I ask this as we can then rule out the issue being anything to do with your Amazon account.
09-16-2019 18:40
09-16-2019 18:40
@theminders I sent a public Tweet to Fitbit and a private DM. No response. I did get an interesting reply to my public Tweet from the managing editor of Android Central. Seems he is having the same issue. He contacted Fitbit's PR department. Here is the tweet in case you (or anyone else) wants to retweet or reply. https://twitter.com/paulmelnyk/status/1173698869496025093
09-16-2019 18:41
09-16-2019 18:41
09-16-2019 18:45
09-16-2019 18:45