Some specs for the "custom JSON config file"?

[erikstar]

Hi!

I have no old experience with any suunto system. Not for "movescount" or successor and not for any linking software for suunto devices. So for me the Ambit 2 is just a very nice gadget I want to get control of. I have absolutely no need for any gui-program or any fance uploading mechanisms to suunto, strava or whatever...

I am curious how the "custom-config json file" work. But I have no specs or examples.

Would it be possible to expose the knowledge so far? Or at least upload some examples.

My guess is that it is supposed to work with files directly downloaded from some suunto-program, but perhaps it exist some knowledge of some well defined json fields that will be understandable...

And if someone could upload some examples... will those only be usable for a specific watch or could I use a uploaded "ambit 2"-file for my ambit 2?

And thanks for the great work so far with openambit!
/Erik

[centic9]

See https://github.com/openambitproject/openambit/blob/master/test-data/test-settings-nologgedrules.json and https://github.com/openambitproject/openambit/blob/master/test-data/test-settings.json for some samples.

You can use openambit-cli to download the settings from a Movescount Account via "--write-config-json" and adjust the resulting files from there. Downloading settings, GPX and routes still works, only uploading moves is blocked now.

[erikstar]

Aha. So I can create a movesaccount account for my ambit 2 (even though I didn't have one "back in the days" when ambit 2 was state of the art?