Recording of real time Heart Rate for 1 workout

[FitnessDodo]

Hello everyone,

since it is apparently not possible to query a real-time heart rate via a web API, here is a quick question to make it interesting for users of a new app:

Is it possible to start the heart rate recording at the start of a workout and to stop the recording of the real time Heart Rate at the end of the workout and then display it graphically? For example, to read out and display the ideal fat burning range?

I would be pleased to receive an answer.

Kind regards

[Gondwana]

Yes, that's possible. But if you only want to see the graph at the end of the workout, you could use the Web API.

It wouldn't surprise me if there are already clockfaces that display heart rate graphs. If you want to see the graph on some other device, that's harder because the data would need to be exported from the watch (which is possible but difficult).

I thought the Fitbit mobile app could display heart rate graphs too.

[FitnessDodo]

Hi Gondwana,

Thank you for your reply.

I would like to display the data in a new fitness app.

In the app, users will have their own profile and can connect their Fitbit account within the app and various values will then be displayed there.

The connection to the Web API is already working.

I can read out steps, calories and zone minutes. But now I want the following:

- when the user wears the Fitbit watch and starts a workout within the external fitness app, the heart rate monitor should start recording the heartbeats per minute. When the workout is finished, the measurement should stop. The statistics should then be displayed on the external app. So not on the Fitbit watch and not in the Fitbit app, but on an external app. Ideally, the heart rate zones should then be displayed, or when you were in the cardio zone, when you were burning fat, etc. Ideally with graphs.

Can you/ or anyone else who can help me describe how this can work? Or what specific data I need to query?

Kind regards

[Gondwana]

This would be easiest by querying for intra-day heart rate data from the Web API, which will be available after the device syncs (either manually or about 30 minutes).

Using the Device API for this will be an order of magnitude more difficult. If you're determined, have a look at some of my stuff here. Mostly it's about accelerometer data, but heart data is conceptually the same (actually easier because there's less of it).