Suunto Vertical 2 – Bluetooth issues: connection loss after a few minutes and/or after stops”

[manno02]

Hardware
iPhone 17 Pro, 512 GB
iOS 26.4
Coros Dura GPS device
Heart rate devices
Suunto HR belt, purchased March 2026
Coros upper arm heart rate sensor
Polar upper arm heart rate sensor

Apps
MySuunto version 3.9.0
Coros app version V4.5.8

Watch
Vertical 2, purchased October 2026, SN 2543C6005743
Software version V2.53.42, installed 7 April 2026

Previous versions
2.50.28 same error as in the current version
2.50.26 same error as in the current version
2.48.16 no error regarding multi‑device management of HR devices

Error description
Since update 2.50.26 and in all subsequent updates, the use of multiple HR devices is no longer possible. The connection between the watch and the HR device drops after a few minutes, the value on the watch display either freezes or no value is shown anymore. This also happens when the correct sensor is selected in the options before starting the workout.

As soon as one or more HR sensors are connected to the watch and at the same time to an external GPS device (here Coros DURA), reliable measurement is no longer possible, the connection is lost, sometimes after pauses, sometimes after a few minutes without any apparent reason.

Even if only the Suunto HR belt is connected to the watch and the Coros Dura and all other HR sensors have been deleted, the watch loses contact with the belt, even though it was displayed correctly at the start.

The error is reproducible, but the trigger cannot be attributed to a specific duration or always to a stop. In most cases the disconnection occurs within a few minutes.

Screenshots of the last activity showing the error in the MySuunto app and on the Coros Dura are attached.

I tried to transmit the logs to Suunto on 8 April 2026 at 18:50 but it didn’t work until 1910, I will add this information.

[manno02]

[enneo]

Same here! I need to disconnect and reconnect the sensor in order to restore its functionality. I have only a single Suunto HR belt.

Hardware
Pixel 8a
Android 16

Suunto Smart HR belt

App version 6.7.12

Watch
Race
Software version v2.53.42, installed 7 April 2026

Previous versions
2.50.28 same error as in the current version
2.50.26 same error as in the current version
2.48.16 no dropouts

Logs sent at 19.28 CEST

Screenshot from yesterday:

[manno02]

Still it isn’t possible to send the logs to suunto

[manno02]

Logfiles successfully sent at 10:26

[isazi]

@manno02 wait, the Suunto HR belt has only one Bluetooth channel, so it can only connect to one device at the time

[SuperFlo75]

I know these dropouts since November 2025, as I updated to 2.48.16… for me, the Suunto HR belt is useless since that time… it began on SV1 with 2.28.26, but it’s also present on my SV2 wich I bought 01/26… I posted this problem several times here in the Forum… But actually I doubt that someone is concerning about this problem

[manno02]

@isazi

Yes that’s true and that’s why I shiftet to other HR from COROS and Polar.
But if I select the suunto belt on the watch before a workout, the watch should keep catching the signals of the selected sensor
It seems to me that the sv2 has a problem with handling the signal and priorizing
As I said it worked very fine without the suunto belt and with different other HRs before the update tragedy that startet in Novemwr when the watch got trouble on IOs machines. But that is another point

[Elmiuel]

Hello everyone, same problem here (again) because a while ago Suunto’s technical service replaced my Suunto belt due to the same connection problems, after approximately 6 months of use of the Suunto band.
Tomorrow I will completely disconnect the band, install a new battery (after resetting the Suunto band) and then test it again with activity.
I’ve also considered that it might be possible using “Sports Mode Customization” after the last update a few days ago…it’s a shame and quite strange because.
Today I even started experiencing watch restarts when I unpaired the power meter from the bike, as I was ruling out sensors. After a 55-minute activity, it started disconnecting again approximately every 2 minutes.
I’ve attached images showing the clock reset and error message, in case it provides any useful information.