@aiv4r Coros has the TIDE watchface. Garmin as well. If you are a multi sport user you need the TIDE info. Suunto included the sport mode “surf”, thank you. But you need to know the tide as well for you surf spot when you are out there in the line up.

@SuperFlo75 Just got my new Polar H10. Paired with the Race 2 - works perfectly without any dropouts until now. Will be interesting whether the Suunto Smart Sensor will work as well (again) when returned from Suunto Repair…

I have the same issue. Race S, Wahoo HR ticker + 3rd party strap. It often takes ~5 mins from start of activity for HR reading to become accurate (e.g. 150bpm Vs 40-60 BPM shown). The HR strap is definitely connected before I start recording the activity and displays the accurate HR reading until I hit record, which is when it often goes funny. This is pretty frustrating as it makes pacing more difficult and messes up the stats for my runs, so it’s difficult to see any HR trends I may have. I don’t believe it’s a strap or sensor issue as I never have issues with them while using my Wahoo Roam bike computer or any indoor cycling training software. The watch also displays an accurate HR from the strap when not recording an activity, so seems like the issue lies with the watch (particular model or my specific watch perhaps…). Any thoughts? If this continues I’d be tempted to put in a warranty claim, which is a shame because everything else about the watch is fantastic.

@Maxime-Bouvier io ho lo stesso problema e ho già postato un’uscita con Garmin coros e Suunto. Secondo me è un problema firmware perché per il primo anno è andato benissimo. Ora da circa due mesi ha problemi.

Questa è un’attività in montagna di giugno 2025. Un anno fa[image: 1781120433280-1000077770.png] Perfetto… Credo sia un problema di firmware o algoritmo

And again… Yesterday: [image: 1780838327522-fa8eed77-8833-45d8-9dc2-beca0563c166-img_6864.jpeg] Today: [image: 1780838297911-90adf7e4-0439-4ee3-9ff1-fb999c01aae1-img_6865.jpeg]

@Squirrel - thanks for the tip. I rebooted watch and iPhone a couple of times, and the watch faces now show on the store when they didn’t before. Back in business. Phew!

@Egika no, you totally understood my question, and I was hoping the answer would be what you said… Thanks!

Hi to all Since I have some poor recording of the cycling power in my suunto 9 baro I am evaluating the purchase of an hammerhead karoo 3. Can somebody list which parameters are correctly imported in the activity and which parameters needs to be manually entered? Thanks I advance

@maszop sometimes you realise at the moment to download maps and … Yeah, otherwise this is just a discussion.

@withManish On iOS there is rungap for datamigration. And I use strava and intervals.icu. It collects data from multiple sources (I had different brands in the past). But most importantly, data of 5 or 10 years ago hardly has any relevance. But I’m no hardcore data collector.

Hopefully they’re able to fix it soon. It feels like with every update they just introduce more problems. Currently still experiencing the auto-update bug (can’t disable it essentially), and now the battery bug has gotten even worse.

@Squirrel thanks!

@sky-runner it does actually. It always starts to connect to the last used, but advances to others it finds. But you can disable each sensor per activity and it will remember this…

@aiv4r Thank you! I’m now looking for AirBnB accommodation for the UTA 22 next year I love this watch but I’m kicking myself for not trying on the Race 2 and the updated bands at the Suunto stand…

@SamuelP I once had a problem installing watch faces, so I reset the settings. Now I’ve decided not to wait for the watch update after all, but to reset the settings instead. Of course, it’s a shame that I have to set everything up again, download maps, and wait for the HRV and ZoneSense ranges to be calculated. I’m curious to see how Suunto will resolve this issue—will the new software version help, or is the problem somewhere else entirely, meaning I’ll have to reset the settings anyway?

after everything you already tested, this really does sound more like a firmware issue on the Suunto Race S after 2.39.20 than a router/network problem. The interesting part is your router logs showing absolutely no connection attempt from the watch. That usually means the WiFi module itself is not initializing correctly after the update, not just failing authentication. I d still try one last simple test: connect it to a very basic 2.4 GHz network without mesh/repeator features, WPA3, band steering, or hidden SSID. Some devices become weirdly picky after updates. But since you already tested multiple routers and hotspots, I honestly doubt your network is the real issue here. Feels like the update broke WiFi handling for some units, especially since the problem started right after the firmware upgrade and before the maps could finish downloading.