Software Update 2.44.46 (2025 Q3)
-
@sky-runner I saw this as well and not sure a bug. I will inquire.
-
@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?
-
@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.
Vector/T6c/Ambit 3 Peak/S5 Copper/S3/S7 Ti/S9 baro Ti/S9P Ti/S9PP Ti/Vertical Ti/Race Ti/RaceS/Ocean/Wing
-
@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?
SR
SA latest beta
Polar Verity Sense
Polar H10
Pixel 6 -
@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.
-
@sky-runner @Brad_Olwin Not at the same time. I will record video tomorrow and publish it here.
-
@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.
-
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%.
-
@timecode Same as me
-
@timecode a bit more maybe on my SRs, but on my SV after a full circle of charge, it consumes less than before.
-
-
@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
-
@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.
-
Some things where text doesn’t fit within the vertical boundaries and not being visible in the new widget
-
@Brad_Olwin Here is the video that explains it better. Polar H10 is on me in the beginning of the video.
I have both sensors paired to the watch. I expected that I don’t have to manually connect sensors every time I use different one. If they are both paired to the watch why they just don’t automatically connect when BT signal is in range? Why do I have to manually connect them? This is not proper multi-sensor support on the watch as it is advertised, it is a wrong way of fixing a problem. Sorry for the harsh words, but it just doesn’t make sense why the watch cannot connect properly.
-
@Dušan-Ković said in Software Update 2.44.46 (2025 Q3):
@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?
This is not my experience, I have 3 HR sensors paired to the Race 2. An HRMPro, and 2 different Suunto Smartsensors. One is automatically picked up when I start an exercise, whichever happens to be on my chest. You should not need to select the sensor, I do not. However, I wet the belt and put the belt on my chest prior to selecting the exercise. If you have more than one belt nearby sending BT connection, this can be problematic as I cannot tell which Smartsensor is connected. I typically wait until I am ready to start an exercise. In the past, the belt automatically connected, that has not changed.
I watched the video, the problem is the sensor is not transmitting HR. You need to have the sensor on and transmitting, the green at the beginning telling you the Polar is connected is an automatic connection.
-
@Brad_Olwin Well it works every time like on video. In the video both sensors are next to each other because of recording. But I have to do that in front of my building, or at the trailhead. I never carry two of them. And it works like that when sensor is on me. I have to manually connect it if I used other sensor in previous activity. If I used H10 yesterday in previous activity and I want to use verity sense today - VS doesn’t automatically connect. I have to manually connect it. And vice versa.
-
@Dušan-Ković When you see the green connection at the top the screen after selecting exercise the sensor is connected! You do not need to manually connect. Maybe this wasn’t clear in my last post.
Vector/T6c/Ambit 3 Peak/S5 Copper/S3/S7 Ti/S9 baro Ti/S9P Ti/S9PP Ti/Vertical Ti/Race Ti/RaceS/Ocean/Wing
-
@Brad_Olwin I’ve seen the exact same behavior as @Dušan-Ković and I understand what he’s saying. My HR sensors do not always automatically connect, whether or not there is another sensor nearby. More often than not, I have to go into the activity menu and select the HR sensor even if it’s on and I’m wearing it, with no other sensors nearby. Every now and then it will connect automatically and correctly without having to this, but it’s not every time.
I’ve also observed even stranger behavior where I’ll select an HR sensor from the activity setting menu (because it didn’t connect automatically), it’ll say it is connected, and then when I back out to the main activity START screen, it is not connected (no HR band icon).
Point is, the behavior is inconsistent and often confusing. I can usually get the sensors paired, but it often involves digging through the menus and jumping through hoops.
Interestingly, I’m using the same two sensors as @Dušan-Ković - Suunto Smart Sensor and Polar Verity Sense. Maybe it’s just a bad combo?
-
@Brad_Olwin @Dušan-Ković I also have a weird issue with multiple sensors. I tried to connect one Coros HRM and one Wahoo Tickr (both full battery). When both are paired to the watch, and both on me, connected, the watch is still pulling HR from my wrist. When I go to the settings section where I can choose which sensor should be connected, and choose either one of the sensors, I get an error - couldn’t connect to the sensor. The connection only works after a very long fiddling around, or if I unpair one of the sensors. If only one is paired, then I have no issues. If both are paired, it’s very unstable and it doesn’t work properly. Then again if I want to pair the one which I previously unpaired it often ends up in an error - couldn’t pair. Something isn’t right.
