Well … I can’t reproduce the “zombie” issue, but I’m almost sure it was due to a mix of enabling/disabling/renaming operation (img attached)
It’s possible to have routes with the same name in SA (guess it’s intentional) but this can create some trouble due to the previously identified data problem
*** Boring Test ALERT ***
*** Skip the rest of the message if you’re not interested in nerdy debug stuff ***
Starting point : Previous post
Renamed Route A -> Aren
Sync - 9 Routes in watch - Route Aren in watch
Disabled Route Aren - OK (Toggle off)
Sync - 8 Route in watch - Route Aren removed from the watch
Renamed Route B -> Bren
Enabled Route Bren
Sync - 9 Routes in watch - Route Bren in watch
Enabled Route Aren - OK (Toggle on)
Sync - 9 Routes in watch - Route Aren in watch, Route Bren disappeared
Renamed Route Aren -> Aren2
Sync - 9 Routes in watch - Route Aren2 in watch
Disabled Route Bren - OK (Toggle off)
Sync - 8 Route in watch - Route Aren removed from the watch
Enabled Bren - OK
Renamed Bren -> A
Sync - 8 Route in watch - Error in App “! Failed to add route to watch” (Toggle off)
Renamed Aren2 -> A
Sync - 8 Route in watch - But in SA Route A (Toggle on)
Enabled Route A (the one was Bren) - OK
Sync - 9 Routes in watch - Route A (the one was Bren) in watch but now it’s not possible to know which one from SA was sent as both toggle are on and data are messed up
“cleaned” the SA routes
Disabled Route A (the one was Bren) - OK (Toggle off)
Sync - 8 Route in watch
Disabled Route A - OK (Toggle off)
Sync - 8 Route in watch - Error in App “! Failed to add route to watch” (Toggle off)
Deleted all SA routes
Sync - 8 Routes in watch
Sync via Suuntolink
… now it’s time to move
Can someone tell me if this is still not possible?
I have to miss my watch for a while because it is being sent back to Suunto for inspection so I thought I would connect the heart rate belt with my phone.
I paired the smart sensor in the Bluetooth menu, but Suunto App doesn’t record any heart rate during an activity.
The app didn’t like my too complex password, but didn’t mention to tell it to the user. So now with “simpler” password it works, sounds like a bulletproof. The sync app worked to endomondo like a charm. So everything is ok ! thx!
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
@pedromslopess said in Suunto 9 stopped syncing with Movescount/Suunto Link after firmware update:
@Brad_Olwin Thanks, I’ll check as soon as I get home today. Just one remark… I’m using MC website to make the activity plan, and then sync with MC app, correct?
After the planned activity is sync how do they show in the Suunto 9 ? A notification, or are they in the any menu?
Correct and planned moves will show when you select Exercise as well as in the Training screen and scroll down from Training Screen.
@suzzlo said in i can't open the app!!:
@Carles-Merin said in i can't open the app!!:
, the answers you give in the feedback are simply useless
sorry if my answer are simply useless, I will try not to waste your time, in my next answer…
BR
Hey I will help if I can… so please don’t be put off…
@Keelan-Birch hm, do you see any discrepancies in your activities? For me, everything works just perfectly at the moment. HR graphs in SA, Strava and Runalyze are nicely aligned. and even R-R intervalls (ibi) looks pretty good. But the thing is, that I changed the strap for my Smart Sensor. Since I have new strap, everything is just fine. So, just a thought…isn’t your strap starting to misbehave…?
Maybe true, my point is, times recorded for 1K autolaps in the watch should match times of those 1K laps in the app I’ll give you that the others shown in the app .5KM, 2K and 5K are splits at least this is from running perspective
@Davide-Rizzi Ι think that is due to following the Android guidelines.
The BT “leaks” location if it’s set on to scanning (other devices can see your BT broadcast).
Also this is BLE that scans in the background
@mbartxxx
I would ask support for a warrenty repair. The service of Suunto is excellent and they also need to know what’s wrong with few devices. It’s good that this does not happen frequently to more users but Suunto can only fix issues they are aware of.
@Jose-Luis You have to do a factory reset on your watch to re-establish the link to movescount. Reseting the app or just deleting the route won’t fix it.
@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
