Hi guys (again),
let’s not spam this thread and create a new one at the Lounge of this forum so we can see how we can solve this issue with the belt.
I have been also a victim of the belt not getting good readings but I managed to still use my 1,5 years old one with this:
But please lets create a new one at the Lounge yes please?
Hello. The synchronization with movescount duplicate all the moves i imported with the beta version of suunto app. I have deleted the duplicated in sport tracker and i have know duplicated run in suunto app i can’t deleted.
@TELE-HO said in heart rate...:
could chlorine be more damaging than sweat and seawater?
It could be but what i`m cared about is that i am out of options just because Suunto belts does not lasts at all.
And this thing costs 20Euro are they kidding there is at least 500% profit.
So I dont have alternative in the pool i ve checked Polar and Garmin and i am not satisfied what they provide in terms of drills and HRM.
Actully started pool swimming is how i get found Suunto watches. For all my other activies i`m ok only with HRM and a phone.
@aldo70 said in Cannot Pair App to Spartan Ultra:
@dimitrios-kanellopoulos yes, this is a good news, the bad one is that I have to send my spartan to be repaired (gps not working well) and I will be using my Ambit3 … which is not supported by the app. Anyway I am happy to be connected again !!!
first world problems (joke). Happy it went good.
@Terppi I agree with this assessment. I’ve also an Ambit3peak and I see the same problem. The way I deal with this right now is to only sync when my iPhone is plugged in and have Auto-lock set to 5 mins in Displays & brightness.
I just checked mine and they are consistent in the watch and on SA. Two other things to consider. Did you set up custom HR zones? If so, did you also set up the Default Zones? Depending on the type of exercise, you may get the default zones instead of running or biking.
@Luche Very happy this worked out and glad all is working now. I did not want you to lose any moves, that is why I did not suggest a hard reset immediately. Thanks @Dimitrios-Kanellopoulos for helping and filing the bug.
@tuomas-lannes the export from St is pita.
Has a lot of errors. The most bug problem is wrong timestamp order that’s why this.
Soon comes paetners connection and .fit export.
Gpx export cannot support good values. Eg cannot have headers with sums etc. Gpx is a bad format by design.
So let’s wait a tiny bit to get the .fit export that should come soon ish now