@Joaquin wonderful work, Joaquín. Thank you! Is there any estimate for when this update will arrive in Race 2?

@dreamer_ You were right: Pace 4 - black crystal and cloud white. https://x.com/corosjapan/status/2057639416659947996?s=46

@cosme.costa said in Strap/Band color suggestion for 90th Anniversary Edition: I do not agree that Suunto’s textile strap is low quality. There are two reasons why I wrote that: The metal clasp at the end of the strap fell off within a few weeks. I was able to fix it back with pliers, but that felt cheap! it came with 2 straps included - a short one and a long one. Well, the short one was too short and the long one was borderline too long. After a couple of months of wearing it, the strap lose a little bit of elasticity that it had and stretched out, so now it was way too long for my wrist. Also, because there no longer was any elastisticity, sometimes it felt uncomfortable on multi-hour trail runs. My wrists aren’t meaty. In comparison, the 90th anniversary strap feels so much more comfortable. It is very similar to Garmin Ultrafit strap too that I used for several years in the past.

@Brad_Olwin Really? Very interesting as XC Skiing is my other Usecase for the Vertical. Sun and Snow together are so bright that the MIP really shines. Also the Solar power collection is welcome. For running I really like the Race S as it is much lighter and the OHR works perfectly since the last update. Waiting for an Ocean 2 Titanium in the Race 2 case. If the new display is that much better it would serve all my demands. But as long as RaceS (discounted), Vertical Titanium (used) and Mares Divecomp together cost less than the Ocean I will stick with this trio

@Joaquin Be careful not to chase perfection and in the end nothing is completed. The komoot route is a bit cumbersome and komoot is far from perfect (even if I tell komoot to not change the route, the route on my suunto race s is different than on my wife’s apple watch.) The garmin/wahoo way (select a gpx file and use the open with app) would be an improvement, even if not all tbt alerts are perfect. My first gps watch (a ambit 3 sport) only had breadcrumb navigation. Did I ever got lost? No. My watch after that, a forerunner 935, had breadcrumb and tbt alerts. (Which didn’t work well. A route could only have 50 navigation alerts and if you did your route reversed you lost all tbt alerts). Did I ever got lost? No. My first watch with maps (a forerunner 965) and having some context is nice. Eventually garmin fixed the 50 alert limit, but not the reverse problem and they introduced a timing bug (up to 10k the alerts are before a corner, after 20k alerts are in a corner, or after). And yes, on a twisty road you get alerts for every corner. Did I ever get lost? No. Now I have a suunto. Komoot is fine, but could be better. Autodetect of going reverse is good. No problem if I do a round route and the end is detected before the start (garmin has problems with this. Navigations stops when you reach the goal, which could be before you actually started). Autozoom actually works as one would except (garmin had autozoom, but that doesn’t work, or not as one should expect). But do I get lost ever? No. In the end, all are equally good in the “do not get lost” requirement. Is everything perfect? No. But don”t wait until everything is perfect. Release small steps. Get feedback. Improve some more.

@Highlands big thank

Thank you everyone i will wait

@Feissty Maybe a trivial question: Have you enabled location services on your smartphone, and does the Suunto app also have permission to access your location? At least on Android — unfortunately, I can’t say how it works on Apple devices. A simple test is to tap the map icon at the bottom of the list in the Suunto app. You should then see your location displayed on the map. [image: 1779457690263-screenshot_20260522_153607_suunto.jpg]

No day without another new vibecoded service. This one is at least more-Suunto specific, not yet another “I made MCP server so you can connect Claude to your Suunto data” (then repeat spam post for Garmin/Coros/etc.) It’s great that people are doing various services, but seems like LLM made this so easy that people not thinking enough about the implications. Vibecode first, market second, reasoning later if ever. But yeah, already think on making paid options What’s the point of the service? What it adds in comparison with Suunto App? Majority of the users sync their Suunto Watch with Suunto App, so even if some third-party service can extract and upload watchfaces, they will likely by overwritten when user sync his watch to SA. Or if they care to change IDs then you can end up with duplicates. And I can continue with other questions, like what happens if Suunto do changes to WF API/format. Then you can break something in the watch using third-party service like this. Find out how to make custom WF? OK, same as above, the fact that you can find out, doesn’t mean it’s good - maybe Suunto is not releasing it because it’s not yet ready for general audience and risky to break the watch. All in all, for the author: good catch to reverse engineer the protocol, for ordinary users: beware.

As it might help someone else that stumbles on the same problem… At least for me it was this Win11 setting that changed things for the better: [image: 1779361611853-34c5e7c4-b6da-4083-9a1f-d14850795012-image.png] Seems stupid in hindsight, but I was not aware that Default only identifies low-power connectivity Bluetooth devices. Happy days! no I will be able to test my apps!

Anyone have issues pairing a Spark with an iPhone? I have an iPhone 17 running iOS 26.5. After pairing, the Suunto App status for the Spark initially shows a green check, but after 2 seconds shows a yellow dot. When clicking on the Spark icon to configure the Spark, it will initially show the left Spark, case, then right Spark. After 2 seconds one of the Sparks gets greyed out, the case may go grey as well, but not always - It changes. When looking at button customization, the Spark that is greyed out shows a circle/exclamation mark. Says it is not connected. I’ve tried forgetting the Spark from my phone, resetting the Spark, deleting and reinstalling the Suunto app, repairing, nothing works. Same behavior on my iPad. I contacted support who were very helpful but nothing changed. They suggested returning it. Before I do, I want to ensure I am not doing something really stupid, and/or that this is a known problem that has a fix or will have. Appreciate any help ya’ll may have. Thanks!

@sky-runner I agree. Things have changed by a lot . Perhaps trail running is not the scenario nowadays. About that argument and if you go further with that and about the map, do you really use the map in a race with beacons? Personally, it’s very rare for me to waste time using it for running in a race with beacons, but I do not conceive a watch without maps (I’m not saying I don’t conceive the watch without the navigation arrow, of course). But is very likely you are running most races with beacons (there are those that do not have them, of course). Now looking at the shot I posted about the Fenix 8, they are using just a vertical line and not an arrow (I find much better Suunto’s design, not only for this but for datafields with big numbers without text legends). This is not a comparison, It’s thinking about the arrow. But if navigation arrow is (or can be) implemented the other arrow should clearly be removed and changed for something else. I see even mark using an opaque tiny rectangle, and matching the colour of the zone. There was another brand doing that (I think). This is just thinking about it. I’m not saying that should be done (at all). But in the other side, it’s very likely that is not something complicated to implement. It’s just about keeping things clean (and I totally agree with you in that).

@Tieutieu said in New on Dev-side..... Race Pacer with planned segments/paces: the only “issue” you could have with your preload plan is that even if you plan your 2,45km @5:19/km segment like in your exemple, on the field there is a lot of chances that your segment will not be 2,45km Yes, as someone who uses navigation routes extensively I can tell that whatever distance was planned, it always end up being inaccurate. In my experience, when running on trails, planned distances can easily be 5% too short. For example, If the on-the-route distance to a waypoint was 20 km, it reality it can end up being 21 km.

I enjoy both verticals and I have no problem reading them but for the summer season MiP is awesome. [image: 1779639840081-img_1252.jpeg] [image: 1779639840139-img_1254.jpeg]

@Adrian.S here is a way to fix this. Export both activities as fit files. Use a third party to merge the files and export the merged as a GPX exercise. Upload the merged GPX into the sportstracker website. The merged file will be present and if acceptable you can delete the separate original files.

@Squirrel completely agree. In fact, at this moment is very likely the Race and Race S are the only watches of the market without the white/red implementation. It’s not something critical, of course. But now everybody seems to like the flashlight in the watch, it’s one of those details that are very visible

@Dimitrios-Kanellopoulos Another crash today at 11:45 CET. Logs sent at 11:52 CET. Watch used Vertical 2. I’ll send you my mail in PM. So far with the current FW both my R2 and V2 are crashing every 3,4 runs. Custom trail run mode Runna guide selected Navigation route selected without turn by turn Burner and ZoneSense Plus apps External Polar H10 V2 connected to Android (today’s logs sent) while R2 to iOS Details: Upon receiving of the “thanks for running with runna” notification I was heading towards the end of the route and was waiting for the end notification. The runna notification never disappeared. What I have noticed is that the notifications with this FW are not going away automatically (most of the time but not always) until mid button pressed. The details of the run in the application are missing: all the Suunto plus data (burner) and the asc/dsc are both 0. Technique part is missing too. Any news of a hotfix coming or should I downgrade? I’ll be switching to the Ocean for now and the training season, if that doesn’t work back to the Forerunnner. Thank for your help!

@Squirrel thanks!