HRV not recieved

[JHultman]

We have a situation where we dont get hrv requests anymore. 

For example: /1/user/******/hrv/date/YYYY-mm-dd/all.json

Where ****** = fitbit id and YYYY-MM-DD is the date. 

Has the API been changed?

[GordonFitbit]

Hi @JHultman 

I am able to get HRV data for myself, so I don't think the problem is wide-spread.   I'm going to reach out to you directly to get some information from you to troubleshoot.

[JHultman]

Well. My problem is i get null, or empty value. normally if no data exists i gemet at least "hrv:[]" as initiator. 

[JHultman]

Also, i do get hrv values, but empty response was a system crash as i did expect at least a empty key 

[GordonFitbit]

Thank you!   I've been able to reproduce this problem and have reported it to engineering.  I'll let you know once I get an update from them.

[JHultman]

This is not only hrv but on other measurements as well. I do belive all will be corrected as this seems to be a central issue

Cheers

Johan

[GordonFitbit]

Yes.  I have seen the same problem with HRV, breathing rate, temperature and SpO2.   I have bugs out for each of them.  I believe I know where the problem exists, and the team is currently investigating it.

[mkbutler]

Tagging so I can find out when this is fixed.

[GordonFitbit]

Hi @JHultman 

From my testing, it seems HRV, Breathing Rate and temperature have been fixed.   I'm checking on the status of breathing rate.

[JHultman]

That sounds great!

Thanks a lot!

/ Johan