Connectivity problems concerning heart rate after update
-
After the January update the connection between external hr sensor (COROS) and watch is not working properly. When starting an activity the connection ist on but after the first stop at a traffic light and with Autostop the connection is lost and doesn’t come back. After syncing when stopping no hr data are transferred. I tried to disconnect and connect again but this doesn’t help. Is there a solution for this problem ?
Kind regards
Axel -
Still unsolved seems to be a reason to get unsatisfied
-
Suunto support told me to step back to an older version for vertical2, I tried it but that didn’t work reliable So I got back to the newest version that still doesn’t work
Rather frustrating the support says sorry and that they will do something in the future
I will send the watch back , after 2 month of usage -
@manno02 does it work when you turn off auto-stop?
-
@2b2bff
No not at all
The suunto support told me to buy an original belt from suunto
That works but is not really a solution for me. If I connect the belt to a COROS dura parallel the hrm goes connects to the COROS and the watch connection is lost even if the connection was earlier
I don’t like it !! -
@manno02, please see: https://forum.suunto.com/topic/14749/bug-vertical-2-randomly-dropping-external-bt-sensors-and-not-reconnecting
AFAIK it also affects Race 2 and Vertical 1.
The issue seems to be solved in the next FW 2.52.8 that is on the 90th anniversary Vertical 2 and will hopefully be available soon for other watches too.
PS - BT connection dropping has nothing to do with (non)original Suunto HR belt. The problem occurs with the original Suunto heart rate monitor and the Polar H10 and Garmin HRM-PRO.
-
@manno02 With the Vertical 2 I use the Garmin HRM 600 strap, the Polar Verity Sense, and the Coros HR belt.
When swimming, the strap often loses the Bluetooth connection in the water, but it reconnects as soon as it’s out of the water. The strap also maintains the connection despite these interruptions, even if I pause the activity.
Does it only happen to you when auto pause is enabled?
-
@Manuel-Extreme
Yes I use the function of Auto stop normally but I tried it without that didn’t help
The problem is erratic
