@yoora Came here looking for a solution to a similar question. I recently ran a race that is a short 5K (the actual distance is closer to 4.68 km). However, my watch reported that I ran 5.18 km, a full 0.5 km farther than the actual course length with a significantly faster average pace than I actually held. When I navigate to Settings -> Connectivity -> Paired Devices -> Stryd X on my watch, it shows “SPEED & CADENCE, POWER”. I’m assuming these are the metrics the watch is sourcing from the pod. Does this mean that distance is coming from GPS? This was a downtown race, but there is only one “tall” building that is 17 floors, the second tallest is 8 floor, and the rest are 4 floors or shorter. It was a clear sky, and the street is very wide. The watch has very good view of the sky. So I don’t think buildings would cause poor GPS signals. I ran this race with other friends, and all their watches recorded 4.5-4.7 km. I’m the only outlier with 5.18 km. None of them have Suunto though, but as I understand it, I have multiband GPS, so it should not have been a problem anyway. So what is sourcing pace and distance? The watch or the pod? Or is pace coming from the pod and distance from the watch?

@2b2bff Yeah but like I said, first, I don’t want to wait for it to auto-pause after it detects I’m resting. A few seconds is an eternity if I’m trying to get precise data on a 50 free interval or other such short intervals. I need it to pause the instant I say stop, which is how my Garmin operates and how I would expect any useful swim function to operate. This is also how the Race S USED to operate, but now it doesn’t anymore. As a triathlete whose primary discipline is swimming and who competes in masters meets, improved swim functionality was a key reason I bought the watch as an upgrade to my old Garmin, but now it’s worse than my old Garmin in that regard, so why did I even bother? I got less than 6 good months of use out of the Race S and it’s close to garbage to me now if I can’t pause and get precise interval data on my swims. I’ve reached out to customer service because I don’t want a subpar work-around. I want the functionality back that I paid for, and I strongly suspect it had to be an OS update that destroyed this functionality.

@PsaRasmus-G How many POIs do you have stored on your watch? I suspect there might still be the same issue older models had where they were supposed to show the 16 closest ones, but it never really worked properly. Ever since then, I’ve kept my number of POIs to 15 max and it works fine. ​Old threads about this: https://forum.suunto.com/topic/6762/serious-navigation-concerns-when-poi-s-are-not-showing?_=1764528809393 https://forum.suunto.com/post/144249 Come on, Suunto, this needs to be solved!

Ok, thank you for the feedback! Then I reduce my question to Bike Pod (no readings) and Power drops ( dropping to zero during the run). I don’t get values from a bike pod with Vertical and RaceS with current firmware. Did a restore of 2.44 on the RaceS - also didn’t help. So three samples in total and I am not the only one. Pod works with Garmin 910xt, Garmin 235, Laptop (ANT+ stick) and Suunto Ambit3 Vertical. And the Power Drops to Zero - I had them on every Run until it was resolved with 2.44. Also this was a common problem in 2.43 I think. Maybe a 2.39 could solve both issues? Its Hometrainer weather in Austria and I want to use the Pod…

@Brad_Olwin thanks for the reply and pertinent information.

Also nothing from my (Elite Misuro) bikepod with November Rain Firmware. Should this be fixed with the current version?

I buyed it to try and unfortunatly I can answer the question. It doesn’t work with Suunto - but with Garmin 🤮 The Sensor connects via Bluetooth, but delivers no readings. On Garmin with ANT everything works out of the box

I was fiddling with my watch and accidentally deleted all the watchfaces on the SA, and to my surprise, I found this cool easter egg. Out of curiosity, is it supposed to be an energy-saving WF or what? [image: 1764488937437-signal-2025-11-30-084638.jpeg]

@zagazoo said in ZoneSense bug for Runs?: @Brad_Olwin Thanks Brad - I’m on IOS app and release version but so far only two test walks have displayed. ZS Can you provide an image of ZS working on your watch? You are sure the belt is connected and sending good data? I have not had a problem with this.

@Sportsfreund So sorry to hear that. Love love love Suunto, just wish things were a little more “working” right now.

And about the quality: First day, two crashes . Really hoping for a stable firmware

@StuieD Yes. Very annoying since it messed up the sleep timer and therefore also a lot of other topics

@mando funny I thought that the torch was a gimmick and now find myself using it all the time! I find the V2 easier to read than the V1. Display is lovely and clear.

@santo75 Kind of agree. The vibration is quite weak, especially on autolap.

I wonder if it’s gotten worse with updates. When I first got the watch I was impressed—the OHR was way better than my old Garmin 745. But the last few weeks/months it’s gotten really bad. 80bpm while sitting down tying my shoelaces (should be ~40bpm). Today on a short 20‑min easy run it spiked to 163bpm (my max HR is in the 150s). At first it would shoot high for the first 10 minutes then settle, but now even long runs have random spikes mid‑run. I tried tightening the strap, but after a few runs I now have a rash on my arm from the watch!!! Usually taking the watch off for 30 seconds helps, but lately even that doesn’t work—I have to repeat it multiple times. Today’s run it just kept spiking again.