Software Update 2.44.46 (2025 Q3)

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.

timecode

I have noticed that my watch is loosing power quite a lot since the last update. Will try to discharge and charge again and compare. For example yesterday afternoon I had 29%, this morning 7%.

SODIUM

@timecode Same as me

Tieutieu

@timecode a bit more maybe on my SRs, but on my SV after a full circle of charge, it consumes less than before.

timecode

@SODIUM @Tieutieu thanks, will check it out after a full cycle. Noticed the same on my wife’s SRs too.

Likarnik

@Dušan-Ković I have same with two powermeters (two bikes), when I make a change (not always), I have do double check if PM is awake and then manualy connect it to watch. A litle less complicated thjan repairing but still requires manual intervention

animalart

@bigwheels87 I’ve finally found the bug ! A factory reset changed nothing. My feeling about the blood oxygen measurement time matching the heart rate monitoring stopping was right. It is the blood oxygen measurement that fails ! I deactivated it and my sleep was normally monitored.