help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Sense 2 won’t connect to Alexa

Replies are disabled for this topic. Start a new one or visit our Help Center.

‎04-07-2026 19:34

‎04-07-2026 19:34

For over a week now, I can’t connect my Sense2 to Alexa. I’ve disconnected it and when I go through the setup again, I get to the Amazon page asking me to allow Fitbit to connect to Alexa and when I click allow, it immediately tells me that it can’t connect. But, when I exit setup, it shows me that I am connected. But when I press the button on my watch, it asks me to set up Alexa. I’ve tried turning the watch off for a few minutes after disconnecting from Alexa and trying the setup after I turn tue watch back on, but it still won’t work.

Best Answer
4 REPLIES 4

‎04-09-2026 04:21

‎04-09-2026 04:21

EXACT same behaviour for me.  It has been this wasy for a month now, since they updated the app to v.4.65.  It was working perfectly up to app v.4.64.  Not sure if is connected to the "no notifications" issue that started happening around the same time.  Lots of other threads on here talk about it.  I have a ticket open with Google/Fitbit regarding the Alexa thing and all they say (as of last Sat.) was that they "are aware" of the situation and working on a fix.  They are at Fitbit app v.4.66.1 now and still no fix, so...

Best Answer

‎04-09-2026 19:01

In response to farrellcsun

‎04-09-2026 19:01

Thanks for letting me know.

Best Answer
0 Votes

‎04-13-2026 15:09

In response to FilmGeek80

‎04-13-2026 15:09

I have the same problem - just started after the last update. The original post and the response were on 4/7 and 4/9. Today is 4/13. Any word on a solution? Have you tried contacting Google?

Best Answer
0 Votes

‎04-14-2026 02:36

In response to bfstea

‎04-14-2026 02:36

Hi bfstea, sorry you are having issues with the Alexa thing.  I'm on a separate thread that was mainly discussing the lack of notifications on the Sense 2 since app update 4.65.  However, the thread also discusses the Alexa set up error that started happening at the same time.  On 9 April, someone on the thread said fitbit app v.4.67 was released which did seem to fix the Alexa connecting error.  Three of us were able to successfully do it after being broken for a month.  See the thread towards the end: https://community.fitbit.com/t5/Sense-2/Sense-2-notifications-are-not-working/m-p/5824062#M35419 

Basically, after updating fitbit app to v4.67: 

"Originally when I updated I still had the connection error for Alexa although in the app it said it was connected.  I disconnected in the app, tried to reconnect and finally had the allow all prompt."  

and

"I removed the Fitbit app, forgot 'Sense 2' and 'Sense 2 Calls' from my Bluetooth settings, and then reinstalled Fitbit version 4.67. After changing my iPhone language to English (US) and the region to Australia, I paired the watch and connected to Alexa via the Fitbit app. also try login with google account not Fitbit" 

Good luck - it should not be this hard!!

Best Answer
0 Votes