Here is the first answer from Hammerhead Support: Thank you for contacting Hammerhead Rider Support, we are happy to answer your questions! Here’s the quick version of what’s happening: the Karoo records the full activity data in the FIT file, including heart rate and your configured zones. When that file is imported into the Suunto app, Suunto applies its own logic to calculate and display things like zone summaries, training load, and similar metrics. On Suunto devices, those values are generated on the watch and saved using their own proprietary FIT fields. For activities coming from an external device like the Karoo, the Suunto app would need to recalculate those metrics on their end to show them the same way as native Suunto activities. Because we don’t have access to your full Suunto training history, we can’t generate Suunto‑specific numbers that will perfectly match their ecosystem. Any changes here would need to come from Suunto’s side. One thing that sometimes helps is making sure your HR and power zones match between your Karoo and Suunto profiles. We appreciate you raising this, we’ve heard similar feedback from other riders, and we continue sharing it with our Product Team. Please let us know if you have any additional thoughts around this. Thanks again for your patience and for riding with us! Best, According to @dimitrios-kanellopoulos there are no Zones in the fit-file from Hammerhead and maybe something is wrong when Hammerhead produces or exports that file. I have mentioned this in my answer to Hammerhead and sent them the same fit-File. Now waiting for their next answer.

@sky-runner said in Unboxing 90th Anniversary Edition: @Freezer When the 90th anniversary edition is supposed to ship? Some people seem to already have it. Like 2 weeks ago i was able to add Vertical 2 Limited 90th anniversary to basket and pay for it in Poland smartwatch shop. I havent seen any info its gonna be send after 10th march. Not sure if I would buy it I wouldnt already got it on my hand :D. It looks cool but as Race 2 owner I dont need it. Its cool for collectors. I’ll sell my watch when Race 3 will be released and if cool enough for switch.

@2b2bff Well it’s exactly the topic I was talking about to start with.

@Adrian.S agree on treadmill elavation gain, would be nice if one could edit it on the watch after the run, like distance but at least we have elevation gain in the app now for treadmill, so step by step.

@Horizontal_2 That initial steep decline is probably related to charging without charging. The current cycle does not show a similar steep discharge at the beginning. Basically, I am currently satisfied with the consumption/battery life of the watch. I have had the watch for 1 year, but it was purchased second-hand. The original owner claimed that he had only used the watch for a few months.

@Ecki-D. But to me, this is definitely a used battery issue, as if i switch on the watch for running, it will turn off instant.

@cosme.costa Having Suunto OHR armband would be cool. Sorry being offtopic

@Nandodiver i’m a 3-star CMAS diver. for training purposes, we dive to a maximum depth of 42 meters. they said that due to Suunto issues, their sensors were unreliable, but I really liked the Nautic S, especially its visible screen and design. thank you very much.

@Egika Is there a table/list that lists the various user requests? Because it must be difficult and redundant for the development teams to read all these discussion threads.

@Egika [image: 1770907355583-1000144681.jpg] I did more runs like this

@shamilt1 Suunto uses something called FusedSpeed. It uses GPS and your steps to calculate your distance. So it is possible the calculation differs, especially as GPS coverage gets bad…

My run today was spot on. Used the Run with the Coros HRM and it was exactly the same as the Polar chest strap. Before I had followed the suggestions and uninstalled and reinstalled the app. So it does seem that at least for this run it has eliminated the spiking. However it has been mentioned in previous posts that uninstalling and reinstalling the app solved the problem each time in occured suggesting it is a temporary fix and not a permanent solution. It also doesn’t alter the data that is already present and incorrect from previous runs so I do believe it’s an issue Suunto need to look into.

@gipfelkind I found the cause: the Morning Report is triggered by arm movement while I’m still in bed. If I don’t see it and leave it undismissed for an hour, it vanishes and cannot be accessed again that day.

I just gave up with all the sleep and recovery tracking and use it as a normal watch. More batterylife and no stress with useless functions that work when ever they feel like

@maszop said in New SMART barometric algorithm: @wakarimasen This has nothing to do with measuring altitude itself — that’s never been a problem with Suunto. Look at the top part of the altitude graph, and you’ll see a jagged line with multiple little, sharp peaks (caused by strong wind) that add up, giving absurd ascent and descent totals. It’s a bit better since the last update, but the results are still absurd and essentially useless for any analysis. Understood. Ascent/ descent isn’t so important for me, I guess. I’m just pleased to get to the top, and know how far there is to go on the way there. My Polar watch ‘over-read’ by 10m at the summit, for comparison.

Suunto please look into this. Give an option to turn off buzz on connect maybe? I’m getting a bunch on my new PP9 and seem to have no reason for them. Supper wasn’t helpful

@aiv4r Here’s hoping that includes us lowly Suunto Run users…we didn’t get the Vertical Week watchface for some reason neither…

A week on & I’ve done a good mix of walks & runs, some hilly & some flat (48 miles with 5111ft ascent). The Race has reported spot on ascent values throughout so the cleaning process above definitely works

@atoponce said in Wahoo Kickr Core 2 speed and distance: @raven On my run this morning, I realized a simple test could be starting the standard cycling sport mode and disabling GPS to see if it collected speed from the trainer. The theory being that the indoor cycling mode is specifically ignoring it. But with GPS disabled on the standard cycling mode, no speed was recorded. So at this point, it seems the best way forward would be to record the activity with the Wahoo mobile app, which does record speed, then use the Suunto API to import the activity, given that the Suunto mobile app doesn’t support importing FIT files directly. Worth a test tonight. When I got my Race S last year, I used the app HealthFit to import some older activities recorded by the Apple Watch, basically “filling things out” to make the start of year 2025. However it didn’t seem to do all the things that would be done if these had been native Suunto activities. Right now I can go to calendar view and see back to Jan 2025, but if I go to Training Zone, my CTL/ATL/TSB graphs are “wonky” until after the point I started using the watch. [image: 1773177192464-dd99bbcd-c9eb-4a7f-8269-3a6dece140a5-image.png] Perhaps I did something wrong, but this experienced convinced me of something I’ve learned with other ecosystems — companies prefer sessions to be recorded with them whenever possible. For Apple, any session recorded by a third-party makes the “Active Calories” and “Total Calories” the same value, whereas with the Apple Watch they differ, with Total including BMR while Active does not. Imports to Garmin might not update their load and recovery metrics. I don’t know the extent to how Suunto treats “non-native” sessions, but my instinct is to try to avoid that. I assume your Core 2 can send two distinct signals? If so, then my recommendation is to have one go to Suunto watch and the other to Wahoo app or whatever, then edit the “Distance” field on the Suunto session to match your app. However, my perspective may be a bit skewed as I don’t do all my analysis on Suunto. I use the site intervals.icu as I can break out my intervals for running, cycling, and most importantly rowing. For my indoor rowing I want to look at my power (watts) and cadence (rpm) data, and Suunto cannot connect to rowing machines at all so I can’t get power there, and it guesses at cadence rather than reads it from the machine. Here’s an example, a short ten minute warm up session I did today: [image: 1773177662776-a6e84e33-5bb6-468e-a725-b59131a8a247-image.png] Notice I have two pushes of one minute each where I average 171w and 177w. At the timestamp I’ve reached my HR peak of 149bpm. Meanwhile, I dual record with Suunto, and it gives me less info, only a HR graph and a fake “speed” graph that uses the reported distance (Suunto guess at it and always overestimates this but I edit it to match) and no ability to see power at all, much less get defined intervals. As I need to use intervals.icu anyway for these sort of things, my motivation with the Suunto app is to get as much relevant data to it as I can natively. So I wanted so the Wahoo import you’re proposing. Even at intervals.icu I don’t show the “speed” graph in my analysis as I don’t see how it can provide me with anything actionable. The session I showed above from Wahoo, here’s how it looks at intervals.icu: [image: 1773178070659-4a23299a-0e33-4e3c-a781-9745ec631ee9-image.png] I could turn on a speed graph, but what purpose would it serve me?