Send HR data to Map My Run

[ToddSteever]

I love my fitbit force and I have kept it at risk of getting the dreaded rash as there was no other ideal replacement available. I think I have found it in either of the two options with HR monitoring!

I use Map My Run for workout tracking. Will these devices be able to send that data stream to the app?

[Michael]

@ToddSteever From Fitbit's post on the API forum it looks like that HR data is going to be available to third party apps, but it will be up to whoever created/maintains the interface to update it to take advantage of the new data. (Most likely that would be the Map My Run people, since I don't think Fitbit creates the interfaces themselves.)

So you might want to check with Map My Run to see if they plan on adding support.

[coldfact]

It would be great if this was just regarded as a "generic" bluetooth heart rate monitor... then apps would not have to purpose build functionality (using the API for it).

For example, I have a Polar H7 Bluetooth sensor - the various apps I use that need heart rate (HRV or running) ask if I allow them to use accessories, once allowed, use this sensor. I don't think any specific "Polar H7" functionality enabled them to do so - just that there was a bluetooth HR monitor available.

[bbarrera]

---

@Michael wrote:

@ToddSteever From Fitbit's post on the API forum it looks like that HR data is going to be available to third party apps

---

Average HR data for a full day, according to both the post and reviewing the API. 

Useless if you want to export a run or other activity.

[Michael]

---

@bbarrera wrote:

---

@Michael wrote:

@ToddSteever From Fitbit's post on the API forum it looks like that HR data is going to be available to third party apps

---

Average HR data for a full day, according to both the post and reviewing the API. 

Useless if you want to export a run or other activity.

---

@bbarrera Actually the post says "We're also excited to announce that the Fitbit API will provide access to the all day heart rate and GPS data from these devices." (You will notice that it says will provide, not that it does provide, I doub they will release the API before the devices.)

The API you were probably looking at, API-Get-Heart-Rate, is listed as deprecated and has a note next to it that says "will be replaced with heart rate time series endpoints". So I think we just need to wait until the Charge HR and Surge are released and then we will see the new APIs that Fitbit makes available.

[bbarrera]

Thank you for pointing out my error, and I agree the new API is not available yet.

That said, the current public APIs provide all-day summary information and my expectation is that this will not change. It is hard to intrepet what Fitbit means by "all day HR" and "HR time series endpoints" although given current public API my eyes focus on the terms "all day" and "endpoints" which imply summary information (and yes, "time series" could imply more fine grain information).

Hope I'm wrong, and that exporting activity level information will be possible. Without activity export, both the Charge HR and Surge are closed platforms and basically unusable with Strava or TrainingPeaks or ...

[Michael]

You can see the API-Get-Intraday-Time-Series API call to see how data can be retrieved, but that API call is only available for partners. Hopefully the HR data won't be restricted the same way.

[bbarrera]

Taking "HR time series endpoints" literally says the API will return two HR values, one from the beginning and one from the end of the time series.

[SunsetRunner]

@bbarrera I think they mean high and low rates during a timed activity. Begining and end would be pointless.  Average rate also would be nice though. That's how Endomondo captures my workout rates while I am wearing a monitor.