Hi all we spotted this issue and will be fixed server side asap. Thank you

Hi everyone I’m still having this issue on the Spartan sport HR with baro watch. It’s really driving me nuts. Any suggestions?

@Dimitrios-Kanellopoulos This issue is back (it was fixed afair in one of the last version) This happen with import too

@sartoric I have an older version of app from the Play store (not beta) and did the same thing when entering the distance, afterwards I turned wifi on. Just checked that on QS and Strava, distance missing. It would be nice to have that synced.

@Dimitrios-Kanellopoulos said in Adding (removing) routes to watch stopped working: @DavorP I am suspecting that this is the issue. With the waypoint version the app uses a new API (different cloud storage). If you don’t mind, could you have a clean version (no routes) and then import back the old ones ? Clear all routes on the watch Clear all routes (if possible) from the app So Install new version. Then use the new version and see if you have issues OK. I finally made it work. I completely deleted all routes, and repeated uninstall, forget pairings, install process. It works now. Thank you all…

@Dimitrios-Kanellopoulos yes, got it. Would be helpful if there was some message that you need to unpair the old phone from the watch.

@dany-l-23 Ι I will need an activity link if possible. This way they can check the data etc

@Dimitrios-Kanellopoulos sent you a link in private chat on this forum.

Yes, only data from Saturday to Sunday are messed up. For Saturday I have 2 records and for Sunday none. It seems like bug is only when switching from Winter to Summertime. And sometimes there is 1 minute difference between the watch and app

@Dimitrios-Kanellopoulos Thanks

@tiberiu-paun my bad before. I confused the threads

@KristianH there are people like me from Suunto coordinating this forum, but it’s not an official support forum lets say.

@pilleus thank you very much

@Dimitrios-Kanellopoulos said in Ascent missing in old routes: I managed to find the issue. Created a bug for this Good And anyway ascent is wrong. Should be 35m at least I was wrong … In fact the route was drawn from top to the bottom. so calculation is correct considering the direction

In addition, it is unfortunate that it is not possible to change the elevation of an activity on SportsTrackers and Suunto app.

I didn’t know that could be done. My synchronization with strava is very fast.

second test: After the watch reset is working fine is this a firmware bug? do you want logs or some information to debug? I’m disabling the option in the watch to auto-update the date+time from SA for now