Suunto app Forum Suunto Community Forum
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

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

    Scheduled Pinned Locked Moved Suunto Vertical 2
    8 Posts 4 Posters 181 Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M Offline
      manno02
      last edited by 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.

      M isaziI 2 Replies Last reply Reply Quote 1
      • M Offline
        manno02 @manno02
        last edited by

        IMG_7813.png IMG_7812.png

        1 Reply Last reply Reply Quote 0
        • E Online
          enneo Bronze Member
          last edited by 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:

          1000093912.png

          Ambit 3
          9 Baro
          Race Ti

          M 1 Reply Last reply Reply Quote 0
          • M Offline
            manno02 @enneo
            last edited by

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

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              manno02 @manno02
              last edited by

              Logfiles successfully sent at 10:26

              1 Reply Last reply Reply Quote 0
              • isaziI Offline
                isazi Moderator @manno02
                last edited by

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

                Watch: Suunto Vertical 2 Titanium Black

                Blog: isazi's home

                M 1 Reply Last reply Reply Quote 1
                • SuperFlo75S Online
                  SuperFlo75 Silver Members Bronze Member
                  last edited by 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 🤔😢

                  Suunto Vertical 2 Titanium Sage
                  Suunto Vertical Titanium Forest/Dark Ruby/UTMB/Courtney_Edition
                  Suunto Wing
                  Suunto 9 Peak Pro Titanium (owns my wife now)
                  Suunto Spartan Ultra
                  SA iOS 3.9.0 (22101)
                  Instagram @superflo75

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    manno02 @isazi
                    last edited by

                    @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

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post

                    Suunto Terms | Privacy Policy