On wrist-calls on Versa 4 aren't working

[Technik21]

Has anyone had issues receiving call notifications on their Versa 4 or Sense2?

I had a Versa 4 with the latest software update that enables the On Wrist Call feature.

However the feature didn't work, and I tried it on a replacement Versa 4(as I returned the first one thinking it was faulty), but the second watch had the same issue.

I exchanged the second Versa 4 for a Sense 2 watch, and again no On wrist call notifications coming through.

I contacted Fitbit Tech support,  whilst over 2 days they suggested and checked settings on both the watch and my mobile phone. They were stumped and suggested I exchange the watch.

I have a Samsung A40, and all permissions and notifications are enabled.

So when I send a Test Notification or someone tries to call me, the watch will briefly show for 1 second a notification on screen and then the notification disappears, even though the Test Notification is still in progress. No vibration either after 1 second.

I also tried the Versa 4 and the Sense 2 on another phone (Samsung S22), but although the watches displayed a call notification correctly, there was no way of answering or rejecting the call from the watch. A message then appeared on the watch to say that there was a problem connecting.

So unless these watches are not compatible with Samsung Androids, there seems to be a problem with the latest firmware update as this affects both Versa 4 and Sense 2.

As mentioned, Fitbit tech support verified that all settings were correct on my mobile, and even tried a factory reset on the watch, removing and reinstalling the Fitbit app, but to no avail.

Very Frustrating!

Moderator Edit: Clarified subject

[Guy_]

Hi @Technik21 - thanks for reporting the problems with on-wrist calls on a Sense 2 or Versa 4 with firmware Version 1.184.52, it could well help others having the same issue.

[MarreFitbit · Accepted solution]

Hi there, @Technik21. Welcome to the Community Forums. Thanks for trying to troubleshoot the issue with your Fitbit devices before reaching out. I understand how you must be feeling. @Guy_ Thanks for helping out!

While reading your post I was wondering if you had another Fitbit device prior your Versa 4/Sense 2? If so, it seems that your Fitbit device cannot connect properly to your Fitbit app since you haven't yet forgotten the connection between your old Fitbit device and the phone's Bluetooth which would explain the connectivity issues you're running into. With that said, try the steps below: 

• Unpair your new Fitbit device and old one from your phone's Bluetooth and Fitbit app.
• Force quit the Fitbit app.
• Turn off other Bluetooth connections when not in use. This can help to prevent connectivity issues or Bluetooth interference.
• Shut off your phone and turn it on after 1-2 minutes.
• Turn on the Bluetooth on your phone.
• Plug it into the charging cable and open the Fitbit app.
• Set up your new Fitbit device again.
• If there is no connection, restart your Fitbit device.

Hope that helps. 

[Technik21]

Hi @MarreFitbit , thanks for your reply.

I will try your suggestions and confirm either way if this works or not.

Thanks for your help.

[Technik21]

Hi @MarreFitbit 

Well there were no previous Fibit devices listed in my Fitbit app, just the current Sense 2.

I thought I would go through the process of removing all Bluetooth references for the Sense 2 and remove the watch from the app again.

Rebooted the phone and watch, and again paired watch to phone. Checked all Permissions were allowed (except camera) and notifications all enabled within the app. 

The "Send Test Notification" still shows for 1 second on the watch before disappearing.

I did notice when looking in the phone's Bluetooth settings that the Sense 2 and Sense 2 Calls were paired, but if I open the Sense 2 Calls settings within Bluetooth menu, that "Use for Calls" is unchecked and it shows as "Connect" at the bottom. If press the connect icon, or slide the Calls tab on, then after trying to connect, It says it cannot connect.

I remember querying this to tech support, and they said this only becomes active\connected during a connected call. So not sure if there is anything to investigate with this.

I suspect it could be a software issue which is why I was curious if anyone else is having the same problem currently. 

[ShellyRenee777]

I myself am having issues as well and I just got this watch on Friday. I tried the above steps after noticing that same thing as Technik21- the Versa 4 Bluetooth calls was turned off and it would not let me turn it on.

Once I completed the steps suggested by MarreFitbit, my watch begin to sync properly in the app and notifications restored, however my watch does not show under my phone's bluetooth settings. I have all notifications allowed between the phone, the app and the watch.

This really is disappointing considering how I had ZERO issues with my Versa 2

[JenEquestrian]

I am having the same problem as the other user. I have a Samsung S22 Plus and had a Versa 2 which is completely removed from my Bluetooth list of devices and I replaced it through the app with my new Sense 2. I cannot answer calls on my new watch. I followed all the instructions you posted and that didn't solve the problem. Also, my new watch does not have the Google Maps tile. Support has not resolved this for me. Any additional help on this would be appreciated. 

[JenEquestrian]

I am having the same issues as you. I have a Samsung S22 Plus. I got a Sense 2 for Christmas and I can't answer calls. I had a Versa 2 before but it's no longer connected to the app or on my Bluetooth device list. Also, I am completely up to date and don't have a tile for Google Maps. Do you? 

[daltonsmom07030]

i have the versa 4 and an android.  I was able to answer calls on my watch with no problem until about a week ago and now i get the couldnt connect error.  I have unpaired, re-paired, checked settings and still does not work either.