Suunto transition to new service platform, planned End-Of-Life for Movescount set to 2020

[marguslt]

Current info on Movescount Services to Suunto Services transition - https://www.suunto.com/transition

Right now Ambit3 & Traverse can transfer logs through new Suunto mobile app to Suunto Services and also receive SGEE updates and at least some features might follow.
But it seems there's not much planned for older non-BT models.

So if some work has been done or planned on offline sports mode customization, navigation ( GPX to route, POI managment), settings interface etc, I'ts probably good time step forward :)

It's also likely that not all the data currently in Movescount does not fit into new Suunto Services, thus there might be some data loss once transition between services goes live. So I believe quite many would be interested in everything regarding data export as well - tools, userscripts, just findings.

For example, for some time now Suunto has provided a batch export ( http://www.movescount.com/settings#export ), but it lacks quite a lot of extra data like notes and tags. Yet there's http://www.movescount.com/Move/MoveList , providing json for summary, notes and tags (often used for tracking gear mileage) for all the Moves. Perhaps it's time to collect all those bits and pieces to wiki to provide means of data rescue for more people and speed up potential development?

[Gerold-R]

I still use an Ambit 2S and I am interested in offline sports mode customization. Is the data structure fully known? I stopped my own analysis a long time ago but during my tests it turned out, that it is possible to create displays showing fields which are not allowed on an Ambit 2S.

Ok. Air pressure value is not valid (shows only a default value), cause there is no room to add an air pressure sensor (MS5540C used in Ambit 2) in the watch case, but temperature is correct.

[JothanChanes]

Hi,
I also have an Ambit 2, and I love this watch. The quality of the watch was why I chose it over the Garmin Fenix, which was unstable at that time (hardware and software). It'd be a shame if the software is now limiting the use of this great piece of hardware.

How is the state of development of openambit, any current plans? I think a group of users should approach Suunto and push them so that they open their protocols and software specifications. After all this would be the most ethical thing for them to do - as they built a watch that may last for a decade, then drop software support after a few years. Either that, or to upgrade un-connectable products to new ones :-P

[schalekamp]

With the current OpenAmbit gui you can at least download your sports activities to XML logfiles.
You can then convert them to GPX with the python script and upload to your favorite service (mine is Strava). One way to go would be to replace the upload to movescount with an automated upload to Strava. Another option would be to make libambit available to python using swig or boost.

So at least my Ambit2 is not completely useless in one year. It feels like bait and switch though.

[myadzel]

Basic support for alternative app (desktop application only, without web service):

1. download activities (GPX, SML);

2. download and upload POI and routes (GPX);

3. creation screens, screen settings and types of activities (XML);

4. update satellite data.

[gustavo-iniguez-goya]

I don't know if this is interesting or not, but I've been working on improving the gui for my own needs (learning a bit of qt along the way), so I've been playing with some ideas:

• a calendar view
• a week view

The new views would have the background of each cell/workout colorized based on the PTE of the move (green-easy, red-hard). And besides this, it would display the Recovery Time. If for example you do 2 hard workouts with no enough time to recover between them, the Recovery Time would be added up to the remaining time to recovery.

One of my ideas is to display a dialog when clicking on a move to edit it, basically to allow to set the feelings (perceived exertion scale) of the workout. But the main goal would be to detect automatically symptoms of overtraining, based on morning bpm + feelings + recovery protocol at the end of every workout (how well you recover from a 1' all-out sprint. not on active recovery days).

If all this is done well (using sqlmodels/views), it'll be very easy to integrate charts.

On the other hand, I guess that it would be easy to add strava support, to upload moves automatically. Or other platforms with public APIs.

[JothanChanes]

Hi, that's some great effort thanks. Currently, I don't know which platform I'd actually use to log all moves. The bigger issue, IMO, is the possibility to upload routes/POIs, which is kind of essential to me. Another thing, though possibly not that important is to enable/disable or even create/edit sports modes. It'd be a dream if we could convince Suunto to open-source their protocol specification or even the Moveslink2 library. Then we could work from XML files, like they are transferred now from movescount to moveslink. Do you think we can muster enough users to make a difference? I already contacted support, but I got a very generic answer :( Johannes.

…

On Thu, Jan 24, 2019 at 10:26 PM Gustavo Iñiguez Goia < ***@***.***> wrote: I don't know if this is interesting or not, but I've been working on improving the gui for my own needs (learning a bit of qt along the way), so I've been playing with some ideas: - a calendar view - a week view The new views would have the background of each cell/workout colorized based on the PTE of the move (green-easy, red-hard). And besides this, it would display the Recovery Time. If for example you do 2 hard workouts with no enough time to recover between them, the Recovery Time would be added up to the remaining time to recovery. One of my ideas is to display a dialog when clicking on a move to edit it, basically to allow to set the feelings (perceived exertion scale) of the workout. But the main goal would be to detect automatically symptoms of overtraining, based on morning bpm + feelings + recovery protocol at the end of every workout (how well you recover from a 1' all-out sprint. not on active recovery days). If all this is done well (using sqlmodels/views), it'll be very easy to integrate charts. On the other hand, I guess that it would be easy to add strava support, to upload moves automatically. Or other platforms with public APIs. [image: openambitgus] <https://user-images.githubusercontent.com/2742953/51707807-724aea80-2022-11e9-9c3e-f3e8d437de2e.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#216 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ApO16dVBB31AEoGzW9FP3WRCE3kGJbrDks5vGiURgaJpZM4aA2Od> .

[centic9]

FYI, the Suunto page now has different wording which indicates that basic support for settings may stay in place for watches like Ambit 1 and 2, see https://www.suunto.com/en-gb/Content-pages/digital-service-transition/

---

The vision for our digital service transition is to deliver a more understandable and relevant service experience that meets the expectations of our entire community as we go forward. To accomplish this, the following key actions are planned:

Movescount App: As mentioned in our April communications, we will remove the Movescount App from Google Play and App Store, we target this to be completed on December 18, 2019. After this time, users that have the app on their phone may continue to use it, but the service will no longer be maintained, and if you change phones or delete the app, it will no longer be available for download.

Moveslink2 and Suuntolink: By summer 2020, Suuntolink will replace Moveslink2, offering our Ambit and Traverse owners a renewed service experience. Suuntolink will be the connection to Suunto app and access to new and incremental benefits from our partner ecosystem. We will keep everyone updated with more details to ensure moving to Suuntolink, and taking Suunto app into use, is as easy as possible.

Suunto Movescount.com (web service): Our web service will continue to evolve in 2020. We will no longer call it Movescount and its role in our services will be to enable key functionality (including watch settings, routes and sport mode customization) for Ambit (1, 2 and 3) and Traverse family watches only. We are planning these web-based updates for the second half of 2020 and will keep everyone updated on the changes coming. No changes are happening right away.

[fmoerl-real]

It seems, the day is there. Today, I was not able to sync to Movescount.

[Gerold-R]

Maybe it depends on what you are using to sync your moves. My latest move (~8km walk) appears in MovesCount.

[marguslt]

@Gerold-R , you are not using the same appkey as Moveslink2 / Openambit, do you? ;)

openambit/src/openambit/mainwindow.cpp

Line 31 in 2802e5e

#define APPKEY "HpF9f1qV5qrDJ1hY1QK1diThyPsX10Mh4JvCw9xVQSglJNLdcwr3540zFyLzIC3e"

Because this has been disabled:

$ http https://uiservices.movescount.com/devices/gpsorbit/binary appkey==HpF9f1qV5qrDJ1hY1QK1diThyPsX10Mh4JvCw9xVQSglJNLdcwr3540zFyLzIC3e
HTTP/1.1 401 Unauthorized

With Suuntolink key:

$ http https://uiservices.movescount.com/devices/gpsorbit/binary appkey==DbCBVqja20NKdrimBHQxtYIdczUJ56WHIWlC6A7vp6NPC0D0a8wA5d0ODyywFKe6
HTTP/1.1 200 OK

(and yes, if I'd use Openambit for Movescount upload, I'd replace the old key )

[fmoerl-real]

in my source files, (2020-09-19), there is the old APPKEY.
Because of the upload worked fine on Saturday, 2021-02-06, the key must have been disabled during the last days.

[marguslt]

in my source files, (2020-09-19), there is the old APPKEY.
Because of the upload worked fine on Saturday, 2021-02-06, the key must have been disabled during the last days.

Yes, on 2021-02-09 : https://www.suunto.com/Content-pages/suuntos-digital-services/

[Gerold-R]

No. We use the AppKey from SuuntoLink now.

[centic9]

For me the app-key from Suuntolink does not work:

± curl --verbose "https://uiservices.movescount.com/devices/gpsorbit/binary appkey==DbCBVqja20NKdrimBHQxtYIdczUJ56WHIWlC6A7vp6NPC0D0a8wA5d0ODyywFKe6"
....
< HTTP/1.1 400 BAD_REQUEST
....

I also tried replacing the key in Openambit to ensure prior authentication is done