Suddenly I can't access breathing rate data

[mrchurch]

As of a couple of days ago, I'm not able to access my Breathing Rate data. I get the message:

    PERMISSION_DENIED - The caller does not have permission

Has something changed??

[UserPun]

I'm getting the same issue. Not sure what happened?

[mrchurch]

It's weird. The breathing rate data is being gathered by my device, it's shown in the Fitbit app and online, but when I try to download the data from the Web interface, it's suddenly not available. Apparently I no longer have the required permissions to access that data.

Fitbit haven't changed the interface, at least not according to their website, so I'm at a loss as to what has happened here.

[UserPun]

Yeah, I'm seeing the same.

It seems the Swagger API Explorer continues to work, once you authorize it: https://dev.fitbit.com/build/reference/web-api/explore/

I did try reauthorizing my app, but I continue to get `PERMISSION_DENIED`...

[anoncat]

Having the same issue here.

Are we all using a Personal type application? As the Swagger API Explorer might continues to work if the issue only affects personal type applications but not server type applications that has been granted access to Intraday APIs.

I have also created a issue through google's issue tracker about the problem but simply received a response asking me to request for Intraday access, despite already stating that my client is a Personal type application. Added another comment clarifying my issue but have not received a response yet.

[mrchurch]

Yes, I'm using a Personal application. I'm using the Intraday by Date endpoint (/1/user/[user-id]/br/date/[date]/all.json), and the last time it worked was 4th June. Every day since then, it's "PERMISSION DENIED".

All rather annoying.

BTW, my phone app can still obtain and display some type of Breathing Data.

[masahiroshindou]

Hi there, I have same issue discussed here.

I got my own breathing_rate data at 5th June at last time.

In addition, I could not obtain my own heartrate variability for yesterday.

Python's "aiohttp" shows the API response:

* 403, message='Forbidden', url='~/hrv/date/{yyyy-mm-dd}/all.json'

* 403, message='Forbidden', url='~/br/date/{yyyy-mm-dd}/all.json'

[UserPun]

Hey, did you hear back anything on this?

I see the issue is still ongoing for me...

[mrchurch]

Yes, it's still a problem. I've been in contact with Fitbit support, and
FINALLY got through to the right department. They've been looking at the
issue for over a week now. No joy yet, but I'm still reminding them every
day that we need a resolution to the problem.

Hopefully, by the time I get back home from holiday, they'll have sorted it
out.

BTW, Fitbit support are bloody useless. Took them eleven days to tell me
(after a lot of back and forth) that I was talking to the wrong bloody
support team...

[macbitt]

That "PERMISSION_DENIED" error might be due to a recent Fitbit update, possibly related to app permissions or Premium access. Try updating the app, logging out and back in, and checking if Breathing Rate is still enabled in Health Metrics. If you’re not on Premium, that could also be the reason.

[UserPun]

Thanks for continuing to look into it @mrchurch.

Hoping you can get it sorted out with their support. It's unfortunate about how long they're taking...

[UserPun]

Hmm, this is via the WebAPI - I've actually tried re-authenticating my 'personal' web app (by asking for more permissions than what I had previously configured).

Or, are you saying to update the iOS/Android app? Not sure how that would help, but my iOS app is also up to date.

[GordonFitbit]

Thank you for your patience.   If you're still having problem accessing your personal breathing rate data, please call the endpoint in your application, then provide me with your client ID.   I'll take a look in our logs to see if I can determine the problem.

[GordonFitbit]

Hi everyone,

I have been able to reproduce the problem where owners of "personal" applications are not able to query their own breathing rate intraday data.  I will be filing a bug to engineering today.  When I receive an update/fix from engineering, I will post the update here.

Gordon

[mrchurch]

There is another ticket open on this issue on a different thread. You might
want to contact THEM, because it has been over a month since they started
looking at this and they haven't been able to respond in a timely manner on
this.

It's issue number 426402647 with the "Fitbit Developer Support" team.

[GordonFitbit]

Thank you!

[UserPun]

Also, please note that this seems to impact 2 endpoints:

• br: /1/user/-/br/date/[date]/all.json
• hrv: /1/user/-/hrv/date/[date]/all.json

[mrchurch]

The Fitbit Support team have finally been able to reproduce this error, as of 4 days ago. No indication of when a fix will be available, of course.

But I live in hope...

[mrchurch]

I've already reached out to Fitbit support. They have finally reproduced
the issue and have created a ticket to get it fixed. Still waiting on the
fix, though.

[UserPun]

Just checking if there was any update on this, by any chance?

As of today, I'm seeing that I can't query spo2 either... 😞