Software Update 2.44.46 (2025 Q3)

timecode

@Inge-Nallsson if you set a target, i.e. Aerobic, I believe the color remains locked to green and even if the arrow goes up, it doesn’t show yellow. This is at least my experience.

Inge Nallsson

@timecode Ah, thanks. My mind had started to doubt the analysis. I do have a memory of the yellow segment being activated on the previous occasion, but that could of course be false (first time usage; not paying close attention). I’ll strike out the above post…

Александр Даниленко

I found a bug for a structured workout with a new firmware version.

Here is explanation in the video:
https://youtube.com/shorts/9cXtOQhgeqc?si=wBht-giIK1870Z-4

In the text:

With new firmware if in a structured workout we have several repeats with a set, when we put this set as “Interval” type, we can see what count of this repeat:

It is a really good thing introduced with the latest firmware, but at the same time because we can see the repeat, like 1/3, 2/3 etc, we can’t see the name of the repeat.

For example if at certain repeat I want to see the name of the exercise I have to do during this repeat, I won’t see it. It will only show me count of the repeat.

At the same time, if we use the type “Warm up”, “Recovery” or “Cool down”, we can see the name of the repeat, but can’t see its count:

I think the watch should display both, the name of the each repeat and its count in the set.

Today during swimming training I had problem with this set because of this bug:

Instead of name of each repeat the watch only showed me numbers, like 1/3, 2/3 and 3/3.

And, please, fix this if possible - make a possibility to turn off notification about the HR sensor connection or to adjust which vibrations can work during the training session and which not:
https://forum.suunto.com/post/172599

🥺

sky-runner

I noticed the following bug - not sure if it is a new or existing bug:

If I open Alti & Baro widget outside of an activity (for example when driving a car in mountains) and keep it open for a long time, then the altitude number keeps updating in real time but the altitude graph doesn’t. The graph remains the same as it was at the moment when you opened the widget.

Brad_Olwin

@Dušan-Ković I reported the lack of color in ZS rings as a bug already. If you set a target zone only the targeted zone will be in color. That is standard.

Brad_Olwin

@sky-runner I saw this as well and not sure a bug. I will inquire.

Dušan Ković

@Brad_Olwin I know, this was without a target.

Another problem with this FW is with multiple sensors. I have two HR monitors - Verity Sense and H10. Both added to the watch. I use both, depending on the activity. This is a problem. For example I went for a run and used H10, next exercise is climbing, where I use Verity Sense. Sensors don’t automatically connect. If I use H10 in multiple activities in a row it is fine, but if I want to use verity sense, I have to connect it manually through exercise menu before activity. That happens every time I switch sensors. Why they don’t just automatically connect if they are added to the watch?

Brad_Olwin

@Dušan-Ković That is not how the sensor connections are currently enabled. I wasn’t aware that people would use two different HR monitors in one set of exercises.

Dušan Ković

@Brad_Olwin it is for completely different exercises. Not even in the same day. I expected that if sensor is paired to the watch it will automatically be picked up. Currently, user has to connect sensor each time from the exercise menu. Who even thought that would be a good experience?

sky-runner

@Brad_Olwin Perhaps not at the same time. What was meant is that there are two HR sensor that can be used in the same activity type alternatively, but not in same activity.

I also have two HR sensors paired - a chest HR sensor and Coros armband HR sensor - and I use either one but not both at the same time. Yesterday I noticed that the watch was refusing to connect to Suunto chest HR sensor at the start of a run even though I was wearing it and could see its battery level even I went to the “paired sensors” menu. I suspect it was trying to use the Coros sensor instead, which I wasn’t wearing. So at the end it used neither of the sensors. Finally when I went out of the range of the Coros sensor and tried to start a run again, it connected to the Suunto sensor.

Dušan Ković

@sky-runner @Brad_Olwin Not at the same time. I will record video tomorrow and publish it here.

bigwheels87

@animalart said in Software Update 2.44.46 (2025 Q3):

Hi !
On my end, I also have a bug regarding sleep. Even if I tighten my watch at the maximum so it does not move, I haven’t get a full night of sleep registered by the watch since the update. The first day it stopped in the middle of the night and since I didn’t get any night registered. It looks like the HR monitoring stops as the curves on the watch and on the app are stopped during the night. I had to move my watch on my wrist (and see the green light) to make the HR back again.

Also having this issue.

Also having the recovery value showing inaccurate issue.