Software update 2.30.32

[Egika]

@Theo-Lakerveld said in Software update 2.30.32:

7 day avg. HRV = 69, last night HRV = 76. Suunto coach states that last night is below avg. Bug?

The coach is referring to the 7 day average in relation to the long term normal range.
Individual outliers you will have to judge yourself.
I think this approach has room for improvement, but this is the way it is currently designed.

[Egika]

@Theo-Lakerveld said in Software update 2.30.32:

Tonight was the first night I had sleep detection without falsely reported awake time. Let’s see if this is structural. In case Suunto has managed to “fix” the sleep detection algorithm, they should surely mention it in the fw release notes.

this is part of the “Improved stability” aka bug fixing

[GiPFELKiND]

Okay, it’s starting to seem like SUUNTO doesn’t take its customers seriously, nor the problems mentioned. I’m slowly getting the feeling that in this forum we all are beta tester and reporting the relevant problems directly to suunto didnt work. Waited for this update for so long and this TSL CTL problem of correct synchronization has not been clarified and solved!? Sorry, such a shame for you! I’m not surprised why other companies steal first place from Suunto. Exactly because of things like this. SUUNTO doesn’t care about the beta testers… the main thing is that the money comes into the coffers

[Tieutieu]

Sorry but I can’t stand the permanent sarcastic tone and « it-doesn’t-works -Suunto-is-fooling-us » anymore.

Few month ago this forum was first of all a help center between users, and source of informations.

It’s now full of haiters and people that seem to think that developers are paid for nothing…

Also tons of new threads opened because :

• one don’t want to search or read the manual
  OR
• threads are so soon polluted that finding informations becomes impossible

Sorry for this post, but no one here is gona directly change Suunto’s marketing, strategy or software development.
But I’m sure they read everything is said here and improve as fast as they can.

So keeping telling again, again and again that things are bad will not makes things go faster, but makes this forum much less fun and useful than it was and than it should be.

I think that we should open a « cry and shout out your angriness » thread that nobody would read but where everyone should post their anger.

My point is not « all problems must be hidden », but that to make things go forward, a problem must be described, circumstantialed. And doing that gently works better…

[I’m a simple user, Suunto fan, ready to help. I’m no beta tester or linked with Suunto from any way]

[mikekoski490]

@Tieutieu Well said.

And to shift things to saying some positives on the update, my 12k trail run today was awesome, as finally able to zoom out the map, which came in handy as with the rain and dark here in Canada I missed a return trail fork. When I figured it out, normally in the big scheme of things on my track the 500m would not have been helpful, but this time the 2k zoom out was absolutely beneficial. Also finding the raise to wake a lot quicker, and of course the GPS track/distance/pace was awesome.

Using an HR belt as usual, but still finding the OHR sufficient for sleep tracking, which overall is spot on.

[Todd Danielczyk]

@mikekoski490 That zoom out is incredibly useful! I did that on a hike last weekend, where I wanted to see where I started. Zoomed all the way out and panned and saw exactly where I was in the hike and what it would take to get back to my starting point.

Decided to stop, eat a snack and have some hot coffee as I looked out on the frozen landscape. Reminding myself why I bought a Suunto Vertical and why I enjoy my outdoor activities. Ranting was a million miles away from my mind!

[wmichi]

My experience so far with the update:

• Raise to wake is much more responsive.
• UI generally feels a little bit faster
• Sleep: Spot on last night
• GNSS accuracy seems improved, although it was already very good
• Not fixed: CTL/ATL/TSB/TSS still not the same as in the app
• Not fixed: Fullscreen notifications during training (like duration target, intensity target) are not closed automatically and I have to press multiple times the crown to make them disappear
• Not fixed: On the data screen with the intensity zones, the duration inside each zone is wrongly calculated when using a HR intensity target zone
• Not implemented but also not promised: Out of zone alerts during structured workouts

Even though there are still bugs, I am happy with the update. The only thing that’s really annoying are those notifications during training. I am already sick of pressing the crown to see my data fields.

[Brad_Olwin]

@GiPFELKiND @wmichi

[Brad_Olwin]

@wmichi said in Software update 2.30.32:

• Not implemented but also not promised: Out of zone alerts during structured workouts

Who promised this?

[Mads Hintz-Madsen]

@Brad_Olwin great if the app and watch is in sync for you but that doesn’t really help us for which this is not the case

For me personally, the CTL and ATL are updated right away in the app after a workout (and sync). On the watch however, CTL and ATL are not updated after a workout. Also the TSS is not updated on the watch.

I think that we have seen enough examples on the forum that some people are still suffering from this out of sync issue.

It is not the end of the world as one can just check the app for updated fitness stats but it does trigger some OCD ️

[Brad_Olwin]

@Mads-Hintz-Madsen Mine have been in sync the entire testing of this firmware and before. Perhaps the issue is related to the sync. Are all users seeing mismatch on Android? I am on an iPhone and tough to trouble shoot when it has not happened for me on Race, Vertical and 9 Peak Pro.

[Mads Hintz-Madsen]

@Brad_Olwin At least I’m on Android but I don’t believe it’s related to the sync process. I would expect that the watch is capable of updating TSS, CTL and ATL without any syncing. Even without syncing, the watch isn’t updating these values for me.

It could also be some side effect of some specific customization of the used sport mode (cycling for me) or some SuuntoPlus apps?!

For my next workout I will disable all SuuntoPlus apps and use a basic non customized sport mode just to see if it makes any difference. So very basic vanilla setup.

Edit: My speculation is that the TSS of the latest workout (in my case) isn’t handled properly in the watch. In my training widget, today’s (Friday) workout doesn’t show up in the TSS figure but the duration of my workout is recorded correctly in the same training widget. Since TSS is the basis for CTL and ATL then this “improper” handling of the TSS could be the reason why the app and watch seems to be out of sync. See figures below:

[wmichi]

@Brad_Olwin Nobody. That’s exactly what I haven written: “not promised”. Sorry, I couldn’t resist to write this. I miss those alerts so much, it breaks my heart

Regarding the training stats stuff: In my case TSB is not the same value as in the app after doing a workout. It’s still the same value as yesterday. CTL, ATL and ramp rate match the values in the app. Also the TSS for today stays blank on the watch for the current day (only the duration is updated after a workout). And the total TSS for the week is also wrong (it’s missing today’s training).

BUT at least in the morning app and watch display the same values.

I am also on iOS. I used custom sport profiles (cross country skiing) without Suunto Guides/Apps.

[wmichi]

@Mads-Hintz-Madsen That’s strange. For me CTL/ATL/ramp rate match the values displayed in the app after a workout. They are always in sync For me TSB/TSS of today/total TSS of current week are not updated.

[Marius Jacobsen Eggerud]

@Brad_Olwin I am on Android and app and watch are not in sync.

[Mads Hintz-Madsen]

@wmichi when I did my first workout yesterday after yesterday’s update then app and watch was in sync so I actually thought the issue had been resolved.

But after today’s workout I am again facing the issue that CTL, ATL and TSS are not updated on the watch.

It seems like different people have slightly different issues here. That maybe explains why it is not fixed yet! SW bugs can sometimes be quite tricky so maybe it is not straight forward to get this fixed even though one might think that it should be an easy fix

[wmichi]

@Mads-Hintz-Madsen Yeah, as a user you just see a couple of numbers. How difficult can it be to sync them properly between the app and the watch? But a user just sees the tip of the iceberg and has no idea how complicated software can be.

Maybe it has something todo with the timezone we are in and when we do our workouts?

@Brad_Olwin Have you done a hard reset after installing the firmware on your device(s)? Maybe this would solve it?

[SuuntoR]

@Brad_Olwin @Mads-Hintz-Madsen

This happens also with iphone. And also when using only the original sport modes.

I think this happens in overnight situations: if ctl, atl, tsb numbers are in sync at night between the watch and the app, they wont be anymore in the next mornig if you sync with the app. And after that tss somehow “freezes” and new tss numbers won’t show up in the watch stats after a that days workout (like pictures on above posts show). Only the power off and on will help on this, after that the numbers are the same on the watch and the app. And I believe after power off and on numbers will be the same, without even syncing with the app. It seems those tss/ctl/atl/tsb are somehow stuck on the watch and restart brings those back to life.

Wasn’t this data sync problem one of the known things which should have been fixed? I believe somebody told it was even recognised as a “massive bug”?

[Mads Hintz-Madsen]

@SuuntoR I think that you are right that the first thing that goes wrong is that the training metrics in the watch don’t update after midnight (but they are updated in the app).

The fact that the training metrics then don’t update in the watch after a workout (for some of us) might then just be another effect of the root cause (mixup of dates, timestamps or something similar in the watch?).

[GiPFELKiND]

@Brad_Olwin Iam on Android too