08-29-2017 13:12 - edited 08-30-2017 08:39
08-29-2017 13:12 - edited 08-30-2017 08:39
As i go through the codes from the sdk-hr-meter example from https://github.com/Fitbit/sdk-hr-meter/blob/master/app/index.js
It is updating the screen with a rate of 2Hz (0.5s), may i infer that the max heart rate sampling rate from HeartRateSensor() API of Ionic/Fitbit Os will be also 2Hz? Can you controll the sampling rate with the API? What's the max sampling rate i can get from this api?
08-29-2017 13:29
08-29-2017 13:29
Just find the Sensors API doc: https://dev.fitbit.com/guides/sensors/heart-rate/ and https://dev.fitbit.com/reference/device-api/sensors/#sensorreading , which indicates a reading of hr with 10Hz or 30Hz also possible, but still it would be great to know what's the limit of the sensor hardware of Ionic.
09-26-2017 10:17
09-26-2017 10:17
Does anyone know what type of Heart Rate data comes through the Sensors API? Is it averaged/ aggregated Heart Rate, Beat-to-Beat Interval (RRi or BBi) displaying the time between each successive heart beat, or something else?
Any samples of the data would be fantastic to see!?
11-07-2017 02:25
11-07-2017 02:25
@Bond-JamesBond wrote:Does anyone know what type of Heart Rate data comes through the Sensors API? Is it averaged/ aggregated Heart Rate, Beat-to-Beat Interval (RRi or BBi) displaying the time between each successive heart beat, or something else?
Any samples of the data would be fantastic to see!?
I would like to know this too. Has anyone got an answer?
01-24-2018 18:40
01-24-2018 18:40
A little late seeing this but here is an example of what I download from a 3rd party source for one minute of my sleeping from my Ionic. Over 24 hours it averages 24 HR points/minute. Typical 35000 plots/day
01-25-2018 13:56
01-25-2018 13:56
According to my experience, higher rate of grabbing heart rate is helpless and even with side effects of in inaccurate read out and power consumption.
I even experience hardware or firmware level failure during my test while grabbing data on brust mode. (which was already deleted under current firmware)
I end up with these way to balance the accuracy, power consumption and response:
start up the default heart rate call back
average every 20 seconds as current output
but double confirm of all read out which is 30% changed by second and third reading
I am to release my app named Heartbeat after power comsumption test under coming Ionic firmware upgrade.
hope it helps
01-25-2018 17:18
01-25-2018 17:18
I would like the ability to capture every heart beat in a sample size of say five mintues. I would then be looking at time (ms) between beats to calculate Heart Rate Variability HRV
05-15-2018 10:10
05-15-2018 10:10
Can HRV shown with real time data?
Thanks.
01-11-2019 11:42
01-11-2019 11:42
For those looking to measure heart rate variability (HRV) I just uploaded eHeart Rate Variability clockface to the gallery. It calculates SDRR (not SDNN because it doesn't filter abnormal beats), RMSSD, and pNN50 in real-time in 1 minute increments. It is based on HR in place of RR intervals which is not ideal.
To Fitbit: is there a way to access RR intervals?
01-11-2019 11:51
01-11-2019 11:51
@Mark2018 wrote:Can HRV shown with real time data?
Thanks.
For those looking to measure heart rate variability (HRV) I just uploaded eHeart Rate Variability clockface to the gallery. It calculates SDRR (not SDNN because it doesn't filter abnormal beats), RMSSD, and pNN50 in real-time in 1 minute increments. It is based on HR in place of RR intervals which is not ideal.
To Fitbit: is there a way to access RR intervals?
06-02-2019 11:23
06-02-2019 11:23
@dragonBTV wrote:According to my experience, higher rate of grabbing heart rate is helpless and even with side effects of in inaccurate read out and power consumption.
I even experience hardware or firmware level failure during my test while grabbing data on brust mode. (which was already deleted under current firmware)
I end up with these way to balance the accuracy, power consumption and response:
start up the default heart rate call back
average every 20 seconds as current output
but double confirm of all read out which is 30% changed by second and third reading
I am to release my app named Heartbeat after power comsumption test under coming Ionic firmware upgrade.
hope it helps
@dragonBTV Are you using the batch mode or have you set a timeout/interval to sample every 20 seconds? I am trying to get one HR reading per minute, and the min frequency that it seems I can set it to is 1, as in once per second (https://dev.fitbit.com/build/reference/device-api/sensors/#interface-sensoroptions).
Thanks in advance for sharing!