How to view POWER data in SA?
-
@Teutch of you can configure them in your watch, you get the right data in the App.
-
@isazi
I looked on the instructions of my Ambit3 Peak but didn’t find how to modify them. Could you help me?I modified them on Movescount web but on SA I don’t know how to do it (being connected to Sport Trackers it is impossible to change them but you can only enter min and max and calculate the app automatically)
-
@Teutch I cannot help, never used an Ambit. But your issue is clearer now, you would like a way to see the same zones you see on your watch in SA, but you cannot configure them on your watch.
-
@isazi Exactly
-
@Teutch , all Ambit users have the same set of constant HR zone boundaries in SA, those are not aromatically calculated but literally fixed to 108-126-144-164.
-
Coming back to original topic -
I can just confirm Suunto App 4.22.2 does not know about power when activity is recorded with Ambit3P + Stryd ( pre-wind footpod, paired as powerpod).Paired Stryd as powerpod, during the run A3P shows power figures as it should. After a mobile sync with SA there’s no sign of power in the SA app, same applies for SA fit-export and all connected services. Which kind of makes sense as there’s no sign of power in summary.json nor sample.json that are stored in Android\data\com.stt.android.suunto\files\smlzip .
Cable sync with Moveslink2 to Movescount works as expected, MC power figures and power chart are present there and MC fit-export includes power as well.
I use Stryd mostly for pace, so for most of my runs I have it paired as a footpod. That’s also the reason why this SA powermeter issue hasn’t bothered me too much. Until now.
-
@margusl said in How to view POWER data in SA?:
Moveslink2
I can confirm that margusl report above is also a true for A3P and the original Stryd (Pioner). Running power was synched when using MC but not when using SA. Running power in activities synched with MC can be displayed in SA. Power is not available in FIT nor TCX and is (therefore?) not automatically syched to Stryd Power Center (which is their analysis tool).
-
@margusl said in How to view POWER data in SA?:
Coming back to original topic -
I can just confirm Suunto App 4.22.2 does not know about power when activity is recorded with Ambit3P + Stryd ( pre-wind footpod, paired as powerpod).Paired Stryd as powerpod, during the run A3P shows power figures as it should. After a mobile sync with SA there’s no sign of power in the SA app, same applies for SA fit-export and all connected services. Which kind of makes sense as there’s no sign of power in summary.json nor sample.json that are stored in Android\data\com.stt.android.suunto\files\smlzip .
Cable sync with Moveslink2 to Movescount works as expected, MC power figures and power chart are present there and MC fit-export includes power as well.
I use Stryd mostly for pace, so for most of my runs I have it paired as a footpod. That’s also the reason why this SA powermeter issue hasn’t bothered me too much. Until now.
-
So by my count, we are now up to 6 users in this thread that are reporting the issue of not being able to view Power data in SA, and I believe we all have Ambit watches:
- paul870 on 03 Dec
- mzungu on 04 Jan
- lexterm77 on 17 May
- myself (Bucket_Z) on 17 May
- margusl on 22 May
- Fripp on 27 May
@Dimitrios-Kanellopoulos - Was there ever any resolution to the bug that you created for this issue on 25 Feb? Would be nice to have this resolved so Ambit users can have this functionality.
-
Checked if there’s any difference when syncing with Suuntolink (3.0.2), all the rest was the same (A3P + Stryd as power pod), phone’s BT was switched off to hold back Suunto App from syncing.
As a mildly interesting note, Suuntolink actually sends samples with power to SA, but in Summary (data summary that is, sent to SA service), min/avg/max power values are empty. And there’s not much to do with this knowledge as SA still ignores power and exported fit-files have no trace of it either.
Not sure if it’s a sign for hope or is handling the data from Ambits actually more messed up than it seemed to be.
-
@margusl said in How to view POWER data in SA?:
Checked if there’s any difference when syncing with Suuntolink (3.0.2), all the rest was the same (A3P + Stryd as power pod), phone’s BT was switched off to hold back Suunto App from syncing.
As a mildly interesting note, Suuntolink actually sends samples with power to SA, but in Summary (data summary that is, sent to SA service), min/avg/max power values are empty. And there’s not much to do with this knowledge as SA still ignores power and exported fit-files have no trace of it either.
Not sure if it’s a sign for hope or is handling the data from Ambits actually more messed up than it seemed to be.
I wonder what would happen if you changed device id from A3P to S9 it would actually show up as it should
-
@lexterm77 said in How to view POWER data in SA?:
I wonder what would happen if you changed device id from A3P to S9 it would actually show up as it should
For activities the latest Suuntolink is using an API endpoint that seems to be set up only for Ambits & Traverse, in other words, I’m not too keen to mess with device spoofing.
But I went back to fill those empty values in summary with some dummy min/max/avg power figures and …
avg_power & max_power made it also into fit-file session data, but there’s still no power data stream, so it’s use is kind of limited. Though at least Training Peaks picks those up (original w/o power vs “assisted” with avg/max power):
If someone has the right amount of commitment, setting up a mitm proxy for Suuntolink in a controlled network for adding correct avg/max for power before data reaches Suunto App, is actually doable.
Though adding / enabling the same thing in a proper way in Suuntolink would be a really low-hanging fruit for Suunto to pick.
-
@margusl said in How to view POWER data in SA?:
@lexterm77 said in How to view POWER data in SA?:
I wonder what would happen if you changed device id from A3P to S9 it would actually show up as it should
For activities the latest Suuntolink is using an API endpoint that seems to be set up only for Ambits & Traverse, in other words, I’m not too keen to mess with device spoofing.
But I went back to fill those empty values in summary with some dummy min/max/avg power figures and …
avg_power & max_power made it also into fit-file session data, but there’s still no power data stream, so it’s use is kind of limited. Though at least Training Peaks picks those up (original w/o power vs “assisted” with avg/max power):
If someone has the right amount of commitment, setting up a mitm proxy for Suuntolink in a controlled network for adding correct avg/max for power before data reaches Suunto App, is actually doable.
Though adding / enabling the same thing in a proper way in Suuntolink would be a really low-hanging fruit for Suunto to pick.
If I had time I would make a Rasberry Pi pair with Ambit and act as a middle man to connect with phone and do the proper conversion and device spoof and correct data format instead of meddling with SA. Also, you can always snoop BT on data exchange between SA and Ambit to see what is really going on, I bet log file of conversation between those two wouldn’t be that long to figure out.
-
Am I correct in thinking that in 7 days time Ambit3 owners lose the ability to get the power data off their watches by any method? I knew SuuntoApp couldn’t do it but had assumed I’d just have to use the cable for all sync until Suunto fix that.
@Dimitrios-Kanellopoulos can you give any insight on to roughly where in the ‘queue of things to do’ this issue sits? Is it a ‘definitely next release and already being tested’ item, ‘we know its important but we have yet given it to a dev to look at’ item or the dreaded ‘its in a long list of things we don’t want to think about and hope that all the Ambit3s in circulation have hardware failures so that we can just cross it off as no-longer-needed…’?
-
@amasidlover said in How to view POWER data in SA?:
Am I correct in thinking that in 7 days time Ambit3 owners lose the ability to get the power data off their watches by any method? I knew SuuntoApp couldn’t do it but had assumed I’d just have to use the cable for all sync until Suunto fix that.
@Dimitrios-Kanellopoulos can you give any insight on to roughly where in the ‘queue of things to do’ this issue sits? Is it a ‘definitely next release and already being tested’ item, ‘we know its important but we have yet given it to a dev to look at’ item or the dreaded ‘its in a long list of things we don’t want to think about and hope that all the Ambit3s in circulation have hardware failures so that we can just cross it off as no-longer-needed…’?
Not to be intended as a solution, but regarding a computer can’t you import the files from suunto link folder to strava or other platform and see the power ?
-
@amasidlover not sure which is exactly the problem, but actually I can see my power avg data on SA, and the hole graph
And I have SA linked to Runalyze and Quantified-Self services, where I can see other Stryd details.
Can you elaborate a bit more so we can understand the problem (at least me)?
BR
-
@suzzlo In your signature it says you have a Suunto Spartan Sport - do you also have an Ambit3? This is specific to the Ambit3 (and possibly 2 and 1) - neither SuuntoLink nor SuuntoApp read the power data from the Ambit3.
-
@André-Faria said in How to view POWER data in SA?:
Not to be intended as a solution, but regarding a computer can’t you import the files from suunto link folder to strava or other platform and see the power ?
Short answer is No. For Ambits Suuntolink does not leave activity logs. For those tests above, Suuntolink data was captured and altered with debugging proxies.
-
I use a favero assioma power pedal with an ambit 3p and can read datas from the pedal on the watch. My penultimate ride was on 6. September and I got average power on the suunto app but no power plot over time. At this time I synced via movescount app. In movescount and quantified-self I can see the power plot. My last ride on saturday (3. October) don’t show plots or average power data on any platform (neither on suunto app nor on quantified-self). This time I synced via suunto app.
-
Should be the same problem ?
I think is already under fix
