j--l wrote:
Chris@Polar wrote:
Malikules wrote:
Will automatic Trainingpeaks Sync become available, like Garmin just got. From a coaches point of view its a huge asset when recommending a watch for athletes.
Yes, for sure. ;0)
I do hope sync to Strava and file export (standard format, no separate hrm/gpx) are coming... are they?
I'd be surprised if they give us .tcx downloads (since they are a Garmin thing) but to be honest *any* readable format will do for now!!
I'm using two apps/services at the moment to deal with automating hrm/gps files to Strava (And Runkeeper and Endomondo!):
* TxcCreator - Watches for and converts hrm+gpx files to tcx, then uploads (to Strava), sends or saves them automatically. I save to a Dropbox folder.
* tapiriik.com - Sycs to/from Dropbox (tcx files)/Strava/Endomondo and a bunch of others
* veloviewer.com - for crunching data from Strava - seriously if you use Strava you must check this out! It's one of the reasons why having access to all the data is so important, because it makes this kind of site possible. It blows Strava out of the water for data analysis and comparison, but Strava doesn't care because it's not Strava's core business goal. Both can coexist and everybody is happy!
So I have my entire history from PPT5 since 2007 in Strava, Runkeeper, Dropbox and Endomondo now, and they all sync automatically whenever I add a new exercise in one of the places.
The only thing I
don't have - thanks to the huge step backwards here, is heart rate data from my most recent runs/rides anywhere except flow since purchasing the v800. Why not? Several reasons (already mentioned above but I'll summarise because this is important to me):
* We can't yet get heart rate data from flow, or directly from the v800, or any way at all in fact short of studying and manually copying the graphs on flow
* Using the H7 strap alongside another BLE device (e.g. phone) doesn't work because BLE re-broadcasting doesn't yet work with any phones/devices I've tried, so only the v800 gets a signal.
* Using the H7 alongside another BLE device and letting the v800 use the 5kHz signal also doesn't work, as it is too weak to give a reliable reading (see examples above)
The only reason I continue to buy Polar wrist units is because I am so impressed with the
hardware, and the reliability of heart rate data and such - if I was
only interested in the data side of things then I would almost exclusively just use a smartphone now, perhaps with a smartwatch. I knew data export would be delayed since I'm not stupid and I read the release notes when I ordered the v800 - but it was widely reported that the v800 would re-broadcast the HR signal to other devices, and that's really why I went for it - because I tend to run with my phone anyway (for music) so firing up Strava/Runkeeper was an ok workaround until September,
on the assumption they could also get access to HR data from the H7.
My dream would be to be able to leave the phone at home (or tucked away in a pocket somewhere), go out for a run/ride/whatever, then come home, hold the back button to sync - and within a few moments see my exercise reported correctly in all the places I want it to be. In the meantime, I'd be happy figuring out some workarounds, but first Polar needs to fix some roadblocks to even make that possible.
P.s. I tried to write a Greasemonkey script for the flow site to allow me to download (scrape) heart rate data from the graphs (since all the raw data is in the client side Javascript), but whilst it is theoretically possible, the data resolution would be very low, because the data used to draw the graphs is perhaps one data point each 10 seconds, rather than 1 second. I did find some more api calls that seem to get the raw HR data, but I haven't been back to poke around again since the last time - it is the summer hols after all ;o)
P.p.s. Sorry for the tangent rant - this is a thread set up for Chris to answer questions (which is appreciated), not take stuff like this on the chin! There are probably a few questions that can be derived from this, like is Polar aware of some/all of these issues and if/when they will be addressed, but I think it's becoming a case of flogging a dead horse so I'm willing to cool off for a few weeks and see what the team comes up with...