Software release 2.30.26

SuperFlo75

It‘s installed… let‘s see what will happen

A Former User

@Dimitrios-Kanellopoulos you mean HRV? All good, just noticed. Thanks anyway!

Tieutieu

@tomasbartko I also have a different value in watch and SA for HRV.
In SA my 7 days average HRV is 35, but in the watch it is 34.
Last night average HRV is ok, same in SA and watch.

@Dimitrios-Kanellopoulos said in Software release 2.30.26:

@Tieutieu wont be its not fixed in this release. Sorry for the bad news

Sorry I had not seen your answer before answering.
No problem for me, this is “adjustments”

Antoine

@tomasbartko what is that problem ?

Antoine

@Tieutieu no more 1 day delay ?

Tieutieu

@Antoine 1 day delay seems to be correct for every values except 7 days average hrv

babychai

@Tieutieu
my 7-day avg is match SA and SV.
so i think CTL STL TSB still got 1 day delay. your watch is restarted after updated. restart will solve today delay but not tmr. so tmr you will see 1 day delay issue there again.

Tieutieu

@babychai That’s what @egika also mentionned to me.
Let’s see tomorrow. But not a big deal anyway (for me at least)

Frederick Rochette

@Tieutieu It’s ok thanks to the watch restart and only thanks to that unfortunately.

AnonVerticalOwner

For those looking for the 2.30.38 release notes!

babychai

i notice when the watch face is dimmed, TSB will show yesterday value. when screen is activated it will show today value.

GiPFELKiND

@babychai said in Software release 2.30.26:

@Tieutieu
my 7-day avg is match SA and SV.
so i think CTL STL TSB still got 1 day delay. your watch is restarted after updated. restart will solve today delay but not tmr. so tmr you will see 1 day delay issue there again.

Hey why the delay wasnt solved? With the update? Today the values again shows 1 day with delay. The watch starts after the update yesterday new, but today the old Values. Have i make a reboot again and the values tomorrow are correct for the future? Thank you for help

Mads Hintz-Madsen

@GiPFELKiND wild guess: Solution isn’t ready yet!

You are not going to get it any sooner by keeping posting about it The issue has been acknowledged. We will get the fix when it is ready and has been verified in testing.

EDIT: If it really bothers you a lot then just use the easy workaround - it only takes 12 seconds per day (i.e. long press the top right button for 12 seconds every morning after waking up). That is what I do.

GiPFELKiND

@Mads-Hintz-Madsen said in Software release 2.30.26:

@GiPFELKiND wild guess: Solution isn’t ready yet!

EDIT: If it really bothers you a lot then just use the easy workaround - it only takes 12 seconds per day (i.e. long press the top right button for 12 seconds every morning after waking up). That is what I do.

For that the watch is not produced press everyday the button for 12 seconds the watch is produced for good working and stable Software AND now very important to show and mirrow the correct values. Therefore a suunto watch is make for!

Mads Hintz-Madsen

@GiPFELKiND I totally agree. I also want this issue resolved. And it will be resolved.

But you can still enjoy the watch while we wait for the fix, e.g., by using the workaround It is not going to break the watch if that is your worry.

Antoine

@Dimitrios-Kanellopoulos Hello and happy New year .
Any approximate date for the correction of CTL STL TSB 1 day delay ? Thanks

Przemko Karpinski 0

@Dimitrios-Kanellopoulos has any of yous experienced no fitness vo2max levels. I run everyday For 1 h and still no estimates , rebooted couple of times to calibrate and nothing so far any advice?

surfboomerang

@Przemko-Karpinski-0 Wild guess… could it be that OHR, cold weather and the new Suunto algorithm are an issue?

I had VO2max values since the release of the SV when it was still using the Firstbeat algorithm. After the last update (with the Suunto algorithm) my VO2max didn’t change for a couple of runs on OHR. The weather here became colder and OHR readings more inaccurate. I switched to the belt and the first run VO2max values started to change again.

No idea if it was pure luck or not.

seanvk

@Antoine Is there a work around for this that doesn’t involve a hard reset of the watch?

Antoine

@seanvk i don’t think… we have to wait for an software update.