Software release 2.30.26

[Brad_Olwin]

@stromdiddily said in Software release 2.30.26:

HRV matches with WHOOP perfectly after first night…hopefully that continues so I can get out of the subscription nonsense

When testing with this version of firmware I was getting identical readings between an AW and Race/S9PP. I don’t wear the Vertical much to bed as it is a bit large for sleeping for me. I would expect the HRV to continue to be accurate.

[nassoscal]

I find the new update a bug step in the right direction. I do like the new features, the responsiveness of the watch and the new UI. Well done.

Sleep might be a bit off but not a major issue for me.

Went for my first run after the update but it seems to be a bit off in distance/pace…it could be my impression but I have been doing the same route for years. Just putting it out there (with caution)

But here comes the question… I can’t seem to locate the recovery time in the menu after the update. Can someone guide me in the right direction, please?

Thank you.

[Dimitrios Kanellopoulos]

@Kai-Liu the update does not happen if you have an alarm set

[Marton Attila]

I really like the update overall. I was just wondering about the “Resources” which is better than before for sure. You are no longer going down to 0% after a easy run. But, I noticed there is no more label as stressed during the day or even recovery. Only active/inactive and that’s it. Before basically you could “recover” if you were sitting for example. Or you would get stressed quite a lot in front on the PC working. Not a big deal honestly.

Fitness CTL/TSB works fine after a soft reset.

[pilleus]

I created a structured workout (picture 1) and loaded it in my treadmill workout as Suunto Plus guide on the Vertical.

I connected the Runn treadmill sensor as foot pod and the Polar Verity Sense as external heart rate sensor. Both were shown as connected, but I was astonished that the wrist OHR was flickering too. I checked the options, the switch was OFF. I switched ON and OFF again, no difference, the OHR was working despite the Verity Sense was connected. So I disconnected the Verity Sense because I was not sure, which device would capture the heart rate.

The Verity Sense was connected to a Garmin Fenix 6X Pro too, so I had a corresponding capturing of the heart rate.

Picture 2 shows the intervals and the heart rate of the Vertical, the OHR worked flawlessly and during the training I could not see any differences to the shown values on the Fenix. Wow!

And in picture 3 you can see the identical heart rate values of the Polar Verity Sense, shown in the Garmin Connect app.

Despite of the permanent and not stoppable OHR on the Vertical it is a great result and no difference to other OHR devices I used the last time.

[Walter Samuel]

Thanks for the update! My question is - why isn’t there a more detailed sleep analysis like Race has?

[suzzlo]

@Walter-Samuel Race uses Gomore algorithm. Vertical uses new Suunto algorithm.

Gomore has been added to the software after Vertical release day, so it’s license is not included.

Any improvement added to the Suunto sleep algorithm, could be included without any license issues

At least is what I have understood

BR

[Walter Samuel]

@suzzlo Thanks for the answer It’s a shame, maybe we’ll have to wait.

[suzzlo]

@Walter-Samuel the good thing is that if Suunto is in control of the algorithm, they should be able to correct problems (in case they are)
In my experience, “Resources” have never worked ok. I hardly get more than 60%-70%, and the answer was always that these was a Firstbeat problem (or at least Firstbeat&Suunto integration problem)

I hope it can help to deliver good metrics

[Martin Vrska]

@Dimitrios-Kanellopoulos The data from the Suunto application does not synchronize with the watch - again I had to do a soft reset for the correct values. Any advice?

[houndsgarden]

Hallo zusammen, kann es seit, dass nach dem Update die Erholungszeit nicht mehr angezeigt wird? Ich kann sie nicht mehr finden.

[Wilson75]

Hi folks, did you notice an excessive battery drain?

I didn’t have the time to test the new firmware. I updated my watch directly at the release date with 54% and today 20%.

[A Former User]

@Wilson75 not on my watch. Had about 70%+ before update (can’t remember the exact number) and did 8h of activities already and have 57% now… quite the opposite (and impressive!).

[A Former User]

@Martin-Vrska @Dimitrios-Kanellopoulos I’m also experiencing the same behavior. Data is not syncing unless I perform a soft reset. Not critical, just reporting.

[Mff73]

@Wilson75 said in Software release 2.30.26:

Hi folks, did you notice an excessive battery drain?

I didn’t have the time to test the new firmware. I updated my watch directly at the release date with 54% and today 20%.

Any battery “issue” right after FW update could be just normal, or at least one need to do a full cycle from 0 to 100%.
Let’s confirm or not after.

[Tieutieu]

@Wilson75 not extra consumption notived.

That’s the gps precision that bothers me. Tried yesterday again : the track I recorded was less smooth and less precise than usual.
Let’s try again today…

[Juhani]

Hi, I can repeatedly get my SV to the state where it is not syncing with the app without soft reset. All I need to do is open the map and zoom out to 500m. Then I see only the black grid instead of the map and everything turns sluggish even when I return from the map and the watch is not syncing anymore. I have reported the map issue to support and there are a few mentions on other threads. Maybe related to certain location? I will do a bit more testing over the weekend, unfortunately no travelling in the near future so I will be on the same map area…

[fluca]

@v-sacre I agree with you. It is improved but still you can’t have a recurrent weekend alarm different from the weekday alarm. Which is my use case.
Anyway thanks suunto to try improving this feature.

[Piotr Grygiel]

What about automatic map updating?

[vpet_09]

@Juhani as I wrote in no maps -thread, I am also seeing basically just black grid on every zoom level, this is happening in Finland Espoo area. With the old firmware everything worked just fine, so this seems to be bug in this newest update.