Sense control keeps disconnecting

[Mannbrad]

Sense control keeps disconnecting from bluetooth. Any idea why?  Using ios. Thanks!

Moderator Edit: Clarified subject

[doctor_tom]

This may be true but the problem (for me at least) is that when I receive a call on my smart phone I can see it on the Fitbit but I can't "Accept" or "Reject" the call using the Fitbit.  This is true even though I'm using the Sense Controls to handle Notifications and Calls.  When I look at the Sense Controls in the Bluetooth connections area of my smart phone settings it shows the "Calls" as turned off and any attempt to turn it back on results in the setting turning itself back off and telling me that Sense Controls can't connect.  

That doesn't seem like it's automatically reconnecting properly.

[eezeepee]

@Ajng @doctor_tom Are you guys on iOS or Android? I'm on Android and I just tested it out by calling myself with my work phone several times. I was able to decline/answer calls just fine. Waited a few minutes and was still able to decline/answer.

[doctor_tom]

I'm on Android.  A Samsung Galaxy S21+ to be precise.  It's running Android 12 (One UI 4.0).

[Ajng]

iOS - I’ve given up and got rid of my Sense it infuriates me so much! Gone back to an Alta which works perfectly 🤷‍:female_sign:

[eezeepee]

@Ajng That's too bad. I remember that Altra. My wife had that one too.

@doctor_tom Yeah I'm on a Pixel 6 Pro Android 13 but really shouldn't make a difference. Have you tried deleting the Sense in the app and adding it again? You don't lose any information on the watch and it'll set up both Sense and Sense Controls connections.

[doctor_tom]

Yes I have, and it only solves the problem until either device is rebooted or they lose Bluetooth connectivity with each other, then it re-occurs.

It may be an issue with how Samsung handles the permissions for the Sense app, but i haven't found anything yet to support my hypothesis.

[pmhupman]

Why people keep giving this same answer. I think we all know that but it doesn't answer the questions being asked.

When we get an incoming call, we get notification on the watch, but controls always stop working after the first successful call.

You can "forget" the controls device and reconnect, then it works for another call then quits. 

A great feature, when it works, but It's become a huge annoyance to continually "forget and reconnect".

(for the record, iPhone 11 pro and currently IOS 15.3.1 (but it's been happening since I got the watch quite a few versions ago)

[carguil]

Hello

I also thik that fitbit doesn t react to all those post
So i decided to give my sense back to the shop and try to get my money back it was my third Fitbit and i am very dissapointed with this !!! bad reaction for the client


Envoyé à partir de Courrier pour Windows

[eezeepee]

@pmhupman It doesn't "...always stop working after the first successful call." Like I said in my reply, I couldn't replicate that issue at all whether it was back to back calls or waiting several minutes. I think it's more of an iOS and Fitbit connection issue if anything.

[janmarbol]

No. That doesn't happen. It connects when it wants to. It's been connecting lately, but not always. Furthermore, "6 days of battery" is also hogwash. It gives me two days, IF I am lucky. I don't even mess with it for it to drain battery like that. This is by far the worst FitBit I've owned and I've owned at least four, and this one was the most expensive.

[eezeepee]

@janmarbol 6 days is more of the ideal as it depends on your settings.

What are your settings? I can get 4 whole days with these settings:

Brightness dim, screen wake motion and button, always-on display off, snore & noise detection off, SpO2 on.

The biggest battery drainers, especially overnight, are the snore & noise detection and SpO2, but more so the snore & noise. With that option off, I only lose around 6-8% over 7 hours of sleep. I had it on for over a week and I don't snore and noise is minimal so it wasn't worth the drain. If I turned off SpO2 I would definitely get 5-6 days. I keep that on because it's part of the health metrics.

[janmarbol]

Thanks for your response.

I do everything you mention, except for "snore detection" because I suffer from narcolepsy. I do not have SpO2 on though. I don't understand why something would have so many features that you can't use. It's a watch that is supposed to monitor health. They should at least tell you, you can do this or that with it, but you'll have at best 24 to 48 hours of battery. That alone is a problem, because you have to constantly charge it, so you basically can't use it, either when you're sleeping or awake for a number of hours, so there are no true reliable numbers. One of the reasons I bought it is because they brag about battery life. smh

[eezeepee]

@janmarbol For features like always-on display, snore and noise detection, and SpO2 they warn of the battery impact when turning them on. And you have to keep in mind most battery claims for all electronics is in ideal settings and usage. It's more of a maximum and not an average battery life. 

Also, keep in mind that it does fast charge very well. So when showering and getting ready, 15 to 30 minutes gets me 30-60% battery gained. 

[janmarbol]

I use one of those things only. The sleep one. That's it. The rest is at absolute minimum. My battery lasts at best 48 hours, and it does not charge so quickly either. It was fully charged when I went to sleep last night. Already it's at 60%. Never mind that it connects to the phone when it wants to. If it has all these features, for which they charge you more than other series of their watches, so it should be adapted to work properly. Six days as opposed to two is a mighty difference, and all b/c you use one of the features it brags about. It's not a good deal.

[eezeepee]

@janmarbol It sounds like you basically have the same settings I do and I can get 4+ days just fine. I stated with 99% at 5am yesterday and am at 70% 2pm today. Something appears to be draining your Sense prematurely and it seems like it's a sync or connection issue and not a Sense monitoring one. Have you restarted both the Sense and phone? You can also try removing the Sense from the Fitbit app and adding it again.

[janmarbol]

Yes. I've tried all of these.

[janmarbol]

Thanks for your suggestions though.

[darlacet]

That best response didn't work for me. I have an iphone 12 max pro and sense controls are the main feature I bought this for. I want to get notifications from my work app and since this won't stay paired I keep missing notifications. My fitbit blaze was better. I'm annoyed that I paid $300 for a watch that basically tells time and counts my steps. Beyond disappointed. 

[eezeepee]

@darlacet You don't need "Sense controls" connected for notifications. It's only for calls and music controls. Your issue is with the regular "Sense" Bluetooth connection. Not sure if you're aware, but the Sense follows do not disturb and mute settings on your phone. So if you use them, you'll miss notifications. If you do use them, turn on the option "Always vibrate" in the Fitbit app under notifications.

[darlacet]

That was the solution I was given when I googled my issue. My Fitbit is always paired with my phone via Bluetooth, I don’t have issues with that connection but I don’t get notifications. I did for one day and then they stopped. I didn’t change any settings. 

i’ve already made sure do not disturb on my sense is off so that’s not the issue either.