I just started playing with Inner Balance app upload to HeartCloud. I found a toggle under settings to sync sessions to HeartCloud, and some sessions have been uploaded, which is a positive sign.
I'd really like to find out if they have a way to export data, preferably with proper fully specified time stamps and preferably including high-res time series data within each session for at least HR/R-to-R interval spacing and their coherence metric. It would be even better if they have OAuth account binding and APIs.
Anyone know what the deal is?
What I've seen so far:
It's great that the app can upload to HeartCloud, but frustrating that they seem to lack controllability and visibility about the process of sessions being uploaded. For example, I let some folks at the QS Pgh Meetup tonight use my setup. I didn't particularly want those uploaded to HeartCloud, but it looks like one was. Then I did a session at home myself which I'd like to see uploaded. It shows up under Review/History in the app, but hasn't shown up on the HeartCloud web site. I wish there were a way to prod it into syncing such a session to HeartCloud, but if there is I haven't found it. (Note that while there is a "share" icon that shows up at the bottom of the session review screen, instead of sending useful data it just seems to send an advertisement. Bleh!)
Looking at the sessions on the HeartCloud web site, it looks like there is at least some time series coherence data being uploaded. The "Training History" session review screen shows a date, start time (though only in local time, sadly), duration, and a little graphic for "
[font='Helvetica Neue', Helvetica, Arial, sans-serif]Coherence Over Time". [/font]
Inspecting the element for the little graphic yields a couple of elements that look like this:
[font='Helvetica Neue', Helvetica, Arial, sans-serif][/font]
It's possible that the combination of those elements, the start date/time, and duration could be parsed into some partially usable time series coherence data. However, that path has pretty low time resolution, and timestamps generated that way are not likely to be very precise. It would be pretty pitiful if that were the best answer we could find for getting the @$%@% data out of their system. That's even worse than the HRV/SweetWater XML hacking described in the previous post.
I'm hoping for a better answer. Does anyone have some useful pointers?