getting too much ascent / descent on flat routes

[GiPFELKiND]

Like @Dimitrios-Kanellopoulos says in another Post - i Open a extra Post for the Elevation “Problem”.
One data set i post here, too.

Hiking_2026-01-09T09_37_55.fit

Here is the Activity at sealevel. My watch counts 222m of positive Elevation…

[surfboomerang]

@Dimitrios-Kanellopoulos As requested…
I did an almost similar round of running before and after the firmware update of my SV1.
The route is totally flat except for one tunnel. This explains the small dips in the altitude graph.

Before the firmware update: ascent 0m, descent 0m

After the firmware update: ascent: 4m, descent 19m

I live 1m below sea level which was nicely recorded before the firmware update. After the firmware I ended the run with -18m

[BastMaSVSRS9PP]

@GiPFELKiND is this maybe the cumulative ascent? Looks reasonable if you add all the „ups“ ? Don’t know just wondering

[GiPFELKiND]

@BastMaSVSRS9PP 222m of positive Elevation while Walking at sealevel?! No never ever. Never had this before. There arent Hills…

[GiPFELKiND]

@BastMaSVSRS9PP there was No Up… 🫣

[BastMaSVSRS9PP]

@GiPFELKiND ok that’s weird then

[sky-runner]

@surfboomerang To me this looks like the barometer port might be dirty. I’ve had something similar recently and fixed that by soaking the watch for a few hours in water with a bit of dish soap, then rinsing and drying it. After that the issue has gone away.

[surfboomerang]

@sky-runner the watch is cleaned after every activity and the baro sensor looks clean.

Wind could be a factor, but I checked a bit further back in history and the last 10 runs before the firmware all show a relative flat line like in the first graph.

[MatthiasKlug]

As @Dimitrios-Kanellopoulos suggested in https://forum.suunto.com/post/183086 i wanted to with additional data (however i am using a race 2 not a vertical 2):

I ran a flat route (track training) - to give you an impression:

With the latest firmware the watch tracked 16m ascent / 0m descent, see picture and .fit file:
Running_2026-01-08T17_37_59.fit
This corresponds with the latest firmware 2.50.26 (altitude and temperature):

For your reference the former firmware was working fine:
Running_2025-12-18T17_41_36.fit
This corresponds with the former firmware 2.48.16 (altitude and temperature):

I couldn’t upload the json files for some reason, please note that i will return to the track on thursday (and most likely every other thursday) so just let me know if there is a setting that i should try and if you need additional infos/data.
Thanks to @GiPFELKiND for opening this thread

(edit: is there a way to scale the pictures somehow? maybe someone can move this thread to ‘watches’ instead of the specific ‘vertical 2’ thread, since this is (i guess) more realted to the firmeware for all watches, rather than a specific watch, thx)
(2nd edit: for my run on the track 2026-01-08 there is potentially additional data available, another race 2 user (same day, same track, and similar training) ran with a race 2, firmware 2.45.16 (NO update that day for him), if that helps)
(3rd edit: i was looking how to downgrade the firmware and found some advice how to (see https://forum.suunto.com/post/159509), cool, it explain how to reach a ‘secret’ DEBUG menu, there ist an option called Algo Logger, so just let me know if using this option could be beneficial )

[Dimitrios Kanellopoulos]

@GiPFELKiND you barometer had noise and ups and downs. So this is not due to the update fyi. WE analyzed the data.

About the other one activity I see fused alti kicking in and that created the ascent. Lets see how this goes need more info