Thanks Egika, will give that a try

@Mff73 It worked!! Thanks so much

Watching this one…got rid of my S9 and now with my A3P I cannot update my zones which makes them pretty useless tbh.

@xaltuton No problem :), the issue is not syncmytracks, but SA/ST import API (the one that is “open”) which is not letting pass these values. If/When SA official import API will be open, we may have nice ways to import.

@isazi Thank you, I’ll look into those apps.

@Cuba1hr said in Migration to Suunto App in 04/2020 and very unhappy with the result: Those minor things that SHOULD be easily fixable-activity setting memory and more screens…I don’t know why those features for SuuntoPlus arrive so slowly. I don’t get it why not more than 3-4 screens if it was possible on the Movescount, how long we have to wait for something that was already available. I think the same, that updates should be released more often.

While waiting for the POIs to arrive, I recommend that you create micro itineraries on the desired port, so that during navigation you can activate navigation to it. I know it’s not the ideal solution, but if it serves to give you direction in case of need, it works

@Chindris-Bogdan don’t worry! Maybe it was still syncing the data from the cloud to your app.

Used the app on Sunday too, syncing my long run without issues.

@margusl Very interesting post. I like your summary of the … flexible … approach to customer interaction. Another wrinkle is that Suunto must have lots of usage data on MC, possibly giving them an idea of the worst-case returns scenario from discontinuing MC-as-is. Out of total MC-related product sales, how many actual MC-users are there? 80%? 50%? How regularly are activities sync’d and viewed? Sports mode settings changed? Routes planned and transferred? In some business school or other, somebody’s probably done a study on what proportion of people, when totally pissed off, will actually bother to demand a refund. And how many would seize on the opportunity regardless of alienation. And what part price plays in that, etc., etc.

@nickshutt sorry, I don’t seem to have this issue.

Today we had a new version but nothing noticeable in iOS. I like this waypoints.

@Prenj we don’t know how many watches of that type are in stores worldwide and on stock in Finland…

There is a document on how epoc is calculated at https://assets.firstbeat.com/firstbeat/uploads/2015/10/white_paper_epoc.pdf There is an Ambit app that uses stryd power reading to calculate your energy efficiency similar to the running performance on ambit which was far more accurate than relying on gps data. http://www.movescount.com/apps/app10645993-Average_energy_efficiency Notice the level of filtering on Ambits Running Performance graph relying on gps vs the energy efficiency app relying on power data. By the time you notice changes in Running performance graph to figure out whether you have proper hydration or enough carbs; energy efficiency app would react much sooner as it gets its data from accelerometers vs. gps and barometer on watch used by running performance. Your body makes subtle changes to adapt to current situation, it does not think about finishing line, thats what brain is for (or not). The sooner you notice the sooner you can react because physiological response to recover gets Progressively slower the father you fall in anaerobic energy debt. Constantly changing wind speeds would render ascent descent baro sensor data invalid even on a flat surface no matter ambit or s9. Epoc modeling has a delay, see white paper, basically loose ohr or belt ruins it. Real time running economy would react sooner than any other method. Your model is based on power, sensor will not become loose or fall off (less likely than belt or ohr) Or better yet, Having a small “sandbox“ for custom equations and graphs sent to SA from s9 like we did on Ambit To MC would stop avalanche of nagging user requests to add features. It would also let us innovate without consuming other peoples time on development. Few 32 bit floating data as temporary registers to implement equations is not much of a footprint these days. Add a few kb of data to support at 10s logging interval. It would just be much more fun even if it fed you meaningless numbers. <nudge> <nudge>

@Brad_Olwin it seems that if I forget from the app the S9 disappears also from the Bluetooth devices. The same is not true for the S7, probably because it is connected to both SA and Wear.

@Captbrad always or just recently ? Could it be linked to that ? https://support.strava.com/hc/en-us/articles/360042757051