@nmiguelrf I don’t remember well whats was the reason but this was in the watches (Spartan for sure and even early firmwares for the S9B, but I do not remember well) and had some downsizes too, so they switch to determine the zones using the phone. I think that if you search in the forum you can find some threads about this. So, you have to sync your phone to get the correct zone in your watch. BTW, for me it is ok how it works now.

@elbee slower development and fewer bugs is always preferred. or let’s say: slower development and in general more complete and matured firmware, software, features… (…still don’t understand how my windows laptop takes ages to connect to the one single connected headphones while my mac just connects when I take them off the charger )

@Milan-Šádek Thanks for confirming! I was actually worried about losing my physiological metrics like HRV baseline and training load history (coming from a Garmin background, a hard reset usually wipes all that training status data). But since Suunto stores all these trends in the cloud/app, I feel much safer doing it now. I’ll go ahead with the factory reset tonight to clear out whatever is blocking the sync, and then reinstall my offline maps. I’ll let you know if it successfully fixes the “My Plan” workout sync! Thanks again for the help.

From support (email) today: Quote: Our technical team has confirmed that the watch may crash under heavy usage. They have identified this behavior and are working on optimizing it in a future software version. In the meantime, we recommend the following temporary workaround: Reduce the use of high-energy Suunto applications when possible. Restart the watch before starting your exercise or activity. These steps can help improve stability until the optimization is included in a future update.

anniversary edition not available anymore in french store, I guess it’s sold out

@Stefan-T. I now can confirm this behavior. Today, after 13 days with some training and also HR broadcasting, I was down to 2% so I put it in the charging craddle. Some hour(s) ago I checked and the watch was on 100% and I put it on again. I could actually monitor, hot the percentage dropped and no I’m on 97%, which is about 1%/hour. That would give me some 4 days!! I I’ll did the soft reset and was back on 99%. So it’s definitely a software issue, that after charging some “counter” is running nuts So I hope this is fixed in the next FW update…

@SergioB It’s working perfectly again. I guess iOS 27 had a bug. After the latest iOS update, everything is working 100% now.

@raphaelh Will do, and thanks! BR Carl

The problem is still viral Silence from the support This still fucks me up

@Squirrel Thanks a lot for the clarification! That actually makes much more sense now. I’ll record my CTL, ATL, and TSB values for the next 2–3 days and compare them to see if the numbers match yesterday’s CTL − ATL. Thanks again!

@sky-runner Tested today and multiple normal routes were synced during same activity. SV2 and Android, but some firmware and app versions ahead for testing. At least some hope…

@skifast12 sorry, I mixed you up with the topic creator. In the first post has been written an interval.icu SuuntoPlus Guide…

@toesalad fur sure it would!

To add to @sergiob You need to make sure that you’ve enabled Turn-by-Turn navigation in the app at the respective route (same screen where you mark to use the route on your watch)!

@surfboomerang looks similar

@Stefano-M64 said: in Italy, 3BMeteo app works usually very well, don’t know if it is accurate in other countries too. Have you ever tried MeteoBlue for the mountains? It’s really useful for my Alps. Its multimodel is manna

@Łukasz-Szmigiel The ones I used didn’t have those tags and have been around for years, so they’re probably directly from Suunto.

@cosme.costa said: Rearding the OFF ROUTE alerts when you are on track, check what I said. Is the route created with SA or imported? I think I’ve seen it both ways - both when it is created in SA and when it is imported. This has never happened before but started happening regularly after the last update. What the new implementation doesn’t take into the account that the map may not be accurate enough, so it may think you are off route because the trail on the map is slightly off from the real trail.