22.18 elevation way off

I think this started with 22.18 (or maybe the version before), but all of a sudden elevation gain is way off, like ~300m instead of ~60m.

Never had any issues before.

  • I’m having a very similar issue, and it started the moment I upgraded to 21.22 from 21.20. I’ve started a product support thread but the only option they’ve offered is a paid exchange, which doesn’t seem like the right next step if this is a firmware issue.

    @garmin-sierra, any advice on what the best next steps here would be?

  • @Dan where are you getting 21.22 from? The latest version available to me is 22.18. I haven't started a product support thread yet - I keep hoping a new firmware update will fix it, but I might give in soon and see what they can do because it's useless right now and throwing everything off - if it thinks you're running a hilly route and you're not all estimates are skewed.

  • 21.22 seems to be the latest live version based on https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/400758/forerunner-955---software-version-21-22---live, so that’s what I’m running. Are you using a beta firmware perhaps?

    It does sound like we’re having an identical problem, so I suspect there’s a regression that got introduced (and presumably landed in the live version in 21.22 and in the beta at some point as well), and maybe it only affects certain hardware versions (which is why not everyone is seeing it?)

    I asked in my support thread if there was a way to reflash 21.20 onto my watch (which would let us verify whether this was indeed introduced by 21.22), but it doesn’t sound like that’s possible.

  • Sorry @Dan - I overlooked 21.x vs 22.x - yes, I am on the beta. My watch does say Rev A even thought I was told I was sent a unit with the updated hardware. Maybe the label on the box is wrong, or maybe Rev A doesn't mean what I would assume. Maybe it is time I try to get a replacement.

  • This is actually getting silly. Here is what it looks like:

    But this is what it should look like:

    Clearly it's a complete mess at the moment.

    Thank goodness for Strava's "Correct Elevation" feature!

  • Updated to 22.21 and today is warm so temperature shouldn't be an issue and yet still I am getting:

    instead of:

  • This is a 5x1200m training on a linear track with nearly no elevation gain/loss "in real life".

    Done calibration just few seconds before start, real starting quote was 110m, but the watch immedeately registered 140m since first second. Why?!

    Done a 1200m to south, then recover steady for 1min, then 1200m to north, steady for 1min and so on.

    2 things are funny:

    1) as usual, quote is increasing when watch temperature is decreasing (start the run with 1° outside)

    2) during each rest, no moving, quote is decreasing by about 4m!

    This is the behaviour of my watch since day 1 in november 2023

  • While I never found the elevation of my Garmin watches reliable (sometimes showing elevation changes even on track workouts) I must say that I've noticed that during the last month or so some of my runs shows no elevation at all and that is in routes I am used to and do have a rough idea of the elevation.

    Something went wrong again at one of the latest updates... 

  • Just as an example I did my long run today. Not a lot of elevation but surely had some but my watch shows it was 100% flat... 

  • Did you have really 0 elevation or something around?

    There is a known bug which might cause you get really 0 elevation for an activity. But this is IMHO the only bug.

    All other issues seem to be hardware related. (But it is better to let the users think it might be software so you do not get that much replacement requests Imp)

    According to what I have observed here in the forum, there are 3 types of devices:

    Type one - works great withing about 1% deviation

    Type two - has some drift (at the acclimatisation periode) but works then within an acceptable range

    Type three - displays clearly wrong values

    I would try to get a replacement.

    One side note to the elevation correction with the map model - this works if you are in a pretty flat terrain but if you are in a hilly area or in the mountains 2m off with your position might cause several meters elevation. Thus you need a lot of filtering (which you can see, looking at those smooth curves). So I made the experience that the elevation change calculated based on the map model in nearly all cases underestimates the real eleveation change.