Sommet - your android/linux app for Ambit, Traverse and Kailash

VoiGAS

Tried it with the Ambit 3 Vertical. Took a few attempts to sync Time and GPS, but it worked. I can also read sport modes and POIs - very nice!
Not sure if the Suunto App in the background makes problems…

André Faria

@VoiGAS said:

Tried it with the Ambit 3 Vertical. Took a few attempts to sync Time and GPS, but it worked. I can also read sport modes and POIs - very nice!
Not sure if the Suunto App in the background makes problems…

USB Otg or bluetooth? Since I don’t have any ambit 3 vertical, there is a slight chance there are stuff that may be slighly different than the ambit 3 and so not working till I get som descr files or pcap dumps.
For example the Traverse was different.

Thanks for the feedback.

VoiGAS

@André-Faria it was Bluetooth, I have no USB-c to A converter so far.

André Faria

New release of the app, with new features, verified support of watches, and mac version tested.
First page updated.

Dimitrios Kanellopoulos

@André-Faria lets go!

André Faria

@Dimitrios-Kanellopoulos said:

@André-Faria lets go!

Thanks a lot for your support Dim!
New site so it can be more “visibile”: https://skinnie.github.io/sommet

Also some news:
iOS build and plays nice with bluetooth and Ambit 3!
MacOS build plays nice by cable (didn’t test by BT yet)
Applied for Suunto API (let’s see how it goes)
Building a weather in route “tool”.

A bump for the missing part:
Training Plan/schedule moves hit a wall, so if someone wants to help/can help…that is the last feature missing to implement from movescount

André Faria

Guess claude on ultra code was able to recover the missing schedule workout!
Soon on the app (when my credits renew ahahha)

zt_zzzzz

The previous version of USB could not connect to Ambit2, but this time it can connect normally.

André Faria

@zt_zzzzz thank you for the feedback. the previous version only based on libambit and maybe something was wrong. the newer versions had a true watch to check, everything is now hardware tested on ambit 2. can you tell me which operative system are you running that gives you that error?
It seems windows, I still haven’t debug it there.
I also see gps orbit failed, and some characters in other language than english, is your operative system in that other language?

zt_zzzzz

@André-Faria said:

@zt_zzzzz thank you for the feedback. the previous version only based on libambit and maybe something was wrong. the newer versions had a true watch to check, everything is now hardware tested on ambit 2. can you tell me which operative system are you running that gives you that error?
It seems windows, I still haven’t debug it there.
I also see gps orbit failed, and some characters in other language than english, is your operative system in that other language?

Windows 10 Chinese version

The problem now is that when Ambit2 is plugged into the USB port of the computer, the system will keep popping up hardware (Windows have a sound prompt.Sommet display connected-checking…->connected-checking…).

(When the Suuntolink is not turned on, the computer also has the same pop-up and hardware insertion sound prompts, but after turning on the Suuntolink, it will no longer pop up.)

Then it connected again, and then it popped up again. I tested it on different computers in the office and got the same result. I plan to go home in the afternoon and change a data cable and try it again with another Ambit2 and my home computer.

Chinese->English.Machine translation result, just make do with it.

André Faria

@zt_zzzzz I still didn’t had the time to test on windows, but theorically fix the translation issues and the fact of server not running and gps status no updating . you can test new release and if not fix I will plunge during weekend on windows.