​Hi everyone, ​I contacted Suunto Support regarding an issue with Heart Rate zone distribution and TSS calculations for activities synced from my Hammerhead Karoo unit. ​Currently, third-party imported activities ignore custom HR zones set on the watch and instead rely on Suunto’s default backend algorithms. As a result, rides synced from my Karoo end up with mismatched HR zones (e.g., shifting Zone 2 efforts into Zone 1), which directly distorts HR-TSS, CTL, and ATL tracking in the Suunto App. ​I strongly request that Suunto allows manual HR zone configuration directly within the Suunto App (or enables synced activities to respect the watch’s custom HR zone settings/LTHR). This would ensure that data imported from head units like Hammerhead is categorized accurately. ​Below is the official response I received from Suunto Support confirming this current limitation: Thank you for contacting Suunto Support and for providing the detailed information. We understand that you are recording cycling activities with your Hammerhead Karoo 3, which are then automatically synced to the Suunto App, and that you have noticed differences in the heart rate zone distribution between the Hammerhead platform and the Suunto App. Regarding imported activities from third-party platforms, the heart rate zone analysis displayed in the Suunto App is calculated based on the settings and algorithms used by Suunto. The HR zones configured on your Suunto Race S watch may not be applied to activities imported from other services, which can result in differences between the original platform and the Suunto App. At the moment, the Suunto App does not support setting independent heart rate zones specifically for imported third-party activities. Therefore, there is currently no setting available to force imported activities to use the HR zone configuration from Hammerhead. We appreciate your feedback regarding this functionality. We will forward your comments to the relevant team as user feedback for future improvements. Thank you again for your understanding and support. Kind regards, Suunto Support Team

I’ve noticed that significant battery drain is caused by the 24/7 heart rate monitoring mode. Previously, the watch would measure heart rate every 3 to 5 minutes; however, after the software update, it monitors continuously—24/7—without any breaks unless you take the watch off your wrist.

@snow had it from May last year & until June this year it was fab, no issues whatsoever. Just since June the issues seem to have been. Updated the app, software, etc, used S+, not used S+, but seems no pattern

@Ecki-D. I sync to Strava, crop there, export GPX, load it to Sport Tracker (after deleting the original). It works, but it is like trying to scratch your left ear with your right foot . Btw. This feature was asked for for at least 10 years

@tm3610 said: Any idea if there are rumors of a new Run or smaller, budget variant? IMHO a Run 2 and a Race S successor is to come in the next months. The real question is when…

@2b2bff it happens the same to me, but I haven’t understand the pattern yet. Sometimes I see only one activity type, sometimes more than one. The only thing I have discovered is that the summary discards always at least one activity, it is never complete.

@athinakap30 With every new software update, the battery gets worse; no matter what setting you use, the juice doesn’t last as long as they are claiming. The last battery issue was addressed in firmware version “2.48.16”, and later firmware versions have been pathetic for battery performance, and Suunto engineers have ignored it royally (busy developing more bugs ) I have been suffering from this issue for a very long time; resets, factory resets, and firmware rollbacks have not worked. Every time I do that, I spend more time reconfiguring whatch.

@isazi Yeah, let’s hope they implement it as soon as possible.

@Goatee Suunto reached out to me via email asking for more information (watch serial number, app version, etc.). I sent them the deets, so I’ll see where things go from there. Hopefully we can isolate the bug and get it fixed.

@Kowalski I’m waiting for a successor of the Race S as well, decided not to go with the Race 2. But it felt surprisingly small for its size…

@Kowalski I don’t know. I’m not a Reddit admin, so I don’t know the tools they have at their disposal to detect stuff like this. It may have been that there was malware hidden in the file hosted in the Google Drive file, and the Core 2 leak was the bait to get you to open it? Just speculating.

A year and half since this issue has been reported. There are 27 30 upvotes. Are there any plans to fix this?

@tomvanacker well known. I usually charge my watch shortly before going to sleep. The stress is somehow reset while sleep tracking, So, it doesn’t bother me much.

@Marcel-W hast du dazu einen Screenshot, was du meinst? Beide Werte sind doch da. HF sogar über die Zeit als Graph…

I’ve been having this problem on and off for a couple of year, first with Suunto Race and now with the Race 2. Tried everything but seems factory reset is the only “reliable” solution. But randomly it stops syncing and restarts again. Since this is affecting many users and have been a problem for years it would be nice to get Supports view on this. Anyone gotten a reliable fix/workaround?

@Egika said: @elbee I have checked. This is going to be fixed. At least it is in the current test version. Thanks for checking! It’s appreciated.

@Sunday really? This is available on Suunto Run. Really starting to feel like the Run has the superior amount of qol compared to every other Suunto watch.

@André-Faria then this defect must have been developed over the last two weeks… But yeah, not impossible. I have this watch for about 18 months and it did already restart three times over that period. Something that is almost acceptable, although it has been once in the middle of a race…

@Gunnar Tried everything in this direction. Nothing works. Funny thing is that when wrist is in water and not swimming, HR value is plausible, but when i start swimming then it goes up to over 170/180 plus. I think it’s a combination of bad sensor design and possibly software