Software Update 2.48.16 (2025 November Rain release)

[SuperFlo75]

@SuperFlo75 said in Software Update 2.48.16 (2025 November Rain release):

Hello guys, I told you some days ago that I noticed that the Suunto HR belt is not working smooth since the last firmware update of my SV… the connection gets lost every minute… and after some minutes, an acoustic signal tells that the connection is back… before my training today, I disconnected the belt and reconnected it… but nothing changed. The belt was bought 10/24 and I renewed the battery about one month ago… after one year of usage. The problem started directly after the last firmware update… what should I do? @Dimitrios-Kanellopoulos @pavel.samokha would it be helpful to send logs? Is it the watch or the belt? The belt should be under warranty, I think?

I think it’s really crazy that no one of the suunto-near volunteers or forum members @pavel.samokha @Dimitrios-Kanellopoulos @isazi answers about these bugs… but I want to update my observations about the BT belt problem… I just wanted to know if it is the belt or the watch which makes trouble, so it got a new Suunto smart heart rate belt today, and I tried it out. The old belt was disconnected since Monday, if don’t have the ghost problem… and I connected the new one… but there are the same problems as before… during activity, hr is gone every 60 seconds or so, and after a short break, there is the beep when the belt reconnects… that’s the proof that I have a watch problem and not a belt problem.

What I don’t understand is why the belt doesn’t the memory data while syncing… I just thought that it is possible to get hr data while not having a BT connection all the time like during swimming?

This is the HR data of my little indoor Test today…

So, dears friend of the night, what can we do to solve this bug as soon as possible?

[Tomas5]

@SuperFlo75 this seems like you have problem with watch, did you contactect suunto customer service and asked for waranty check or repair? This is just comunity forum, people can suggest some thinks to do but this seems can be solved only by replacement or another kind of fix in service center.

[pavel.samokha]

@SuperFlo75 said in Software Update 2.48.16 (2025 November Rain release):

it’s really crazy that no one of the suunto-near volunteers or forum members @pavel.samokha @Dimitrios-Kanellopoulos @isazi answers about these bugs…

Have to say again that this is a community forum. If I have something to comment I will, but that’s not my duty. If you have issues you should contact official Suunto support channels

[SuperFlo75]

@Tomas5 @pavel.samokha I didn’t contact support until now, as I think that this problem is related to the firmware update, it started after the last update. I noticed that problem during the first trail run after the update, I never had this problem before. That’s why I posted this in this thread, and that’s why I mentioned @pavel.samokha because I thought this is the ‚Suunto firmware update Specialist’? There are several guys here who have problems with BT connections… and after following this thread I think that battery drains seems to be correlated with these BT problems?

[althaea35]

@SuperFlo75 I have had similar problems with Suunto HR belt.

Started a few firmware updates ago with occassional drops. Then more recently it will connect then drop out altogether. This was happening with the provious firmware and same with current firmware.

Last year I replaced the belt, then the sensor, as the old sensor had stopped working as well. Six months in with the new sensor and the same problem.

I have reverted to my 5 year old Polar H10 belt and sensor with no issues. No problems connecting and no drop outs during a session.

This is looking like a problem on the sensor side for me. I am unlucky to have two sensors fail in 18 months or a BT design issue somewhere?

[Brad_Olwin]

Those of you having battery issues, it is not everyone. I have my personal V2 running 2.48.16 and battery life is excellent. Use Suunto Smartsensor nearly every day- no drop outs and no BT connection issues.

[runomatic]

@Brad_Olwin I can confirm that. I have a V2 here for testing right now. After almost a week of intensive use, I still have 64% battery life. I don’t have any BT problems either.

By the way, I didn’t have any problems with my V1 either.

[dani_degi]

no problems with Battery Race 2

9-10 tage 10% a Day… 6-7 hours gps and 1 2 hrs indoor cycl and 1h swim…

easy

[Kramble]

@runomatic said in Software Update 2.48.16 (2025 November Rain release):

@Brad_Olwin I can confirm that. I have a V2 here for testing right now. After almost a week of intensive use, I still have 64% battery life. I don’t have any BT problems either.

By the way, I didn’t have any problems with my V1 either.

Could tell me the daily consumption of your V1 without activities but with OHR24/sleep tracking?
Historically it’s between 3 and 4 % (I’ve got my V1 since the release) but since the last updates it’s between 6 and 7% for me and some others.

[runomatic]

@Kramble said in Software Update 2.48.16 (2025 November Rain release):

Could tell me the daily consumption of your V1 without activities but with OHR24/sleep tracking?
Historically it’s between 3 and 4 % (I’ve got my V1 since the release) but since the last updates it’s between 6 and 7% for me and some others.

I would love to, but shortly after the last update, I received the Vertical 2 to test and have been using only that watch ever since.

[duffman19]

@Brad_Olwin said in Software Update 2.48.16 (2025 November Rain release):

Those of you having battery issues, it is not everyone.

Like most people posting here, I don’t assume my issues apply to every watch and every user. However, this doesn’t negate the fact that many of us are still experiencing one of the problems this update was intended to solve.

I think we’re all in agreement that the battery drain issues are somehow related to overactive BT connections. Personally, I suspect it has to do with the implementation of multiple BT sensor connections as this function has never worked properly for me since it was introduced. Perhaps the issue is only affecting those of us with multiple BT HR sensors? Or maybe it is only specific external HR monitors?

My experience
I have two external HR monitors paired to the watch: a Suunto Smart HR Belt and a Polar Verity Sense. If I use one of them for an activity (let’s say the Suunto Smart for a trail run), and the next time I choose that same activity I want to use the other sensor (so another trail run, but with the Polar VS), it is guaranteed that the watch will not connect to that BT HR sensor even though it shows as one of my available paired devices.

Even if I go into the activity settings (Exercise options > Sensor data) and select the correct “new” HR and then back out to the activity home screen, it will not stay connected. Currently, the only way to connect the new HR is to select a different activity profile altogether (so, let’s say walking), go into that activity’s settings, select the correct HR, back out of that activity (still doesn’t show the HR sensor is connected, btw), go to the original activity I wanted to start (trail running in this instance), and now the correct HR belt will usually show as properly connected.

I’m guessing this wasn’t Suunto’s intended behavior for having multiple BT connections. And since there are so many issues connecting to different BT sensors when attempting to start an activity, it stands to reason that there are also BT issues outside of activity mode that are causing severe battery draw. For me, I still have phantom vibrations outside of activities suggesting that the watch continues to attempt to connect to my external sensors.

Further, the increased battery drain only occurs sometimes. It is not a constant for me. So some sort of action or behavior is causing it, perhaps related to the dance I have to do to get my external HR sensors to connect.

I obviously don’t know the answer, but that’s why I’m posting my observations here in the hope that it will help lead to a solution.