openmhealth / shimmer

An application for reading health data from third-party APIs.
Apache License 2.0
438 stars 122 forks source link

Fitbit integration #120

Open tmorriso5280 opened 5 years ago

tmorriso5280 commented 5 years ago

Hello, I have been attempting to get Shimmer working for about a week now with no success. I am trying to integrate Fitbit with my Shimmer (to start) and I can't even get that going. I followed the ReadMe, and have created an application on fit bits developer site. I have copied the client id and client secret into my resource-server.env file, and then I am running "sh run-dockerized.sh" (I am on a mac). Then, as it seems the console is not working, I am attempting to use Postman to authenticate with my fitbit application. When I do this I get the following response on Postman:

{ "timestamp": "2019-07-09T01:00:58.325+0000", "status": 500, "error": "Internal Server Error", "exception": "java.lang.RuntimeException", "message": "org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.RuntimeException: A configuration for shim 'fitbit' wasn't found.", "path": "/authorize/fitbit" }

I also see that there are a lot of warnings about deprecated functions when I run the run-dockerized.sh script, and I imagine that Shimmer has not done anything with these based on their GitHub history.

Can anybody help point me in the right direction? The documentation seems lacking and I haven't heard back from anyone at Shimmer, even though I sent an email early last week or the week before. I am so confused and frustrated.

Thanks!

tmorriso5280 commented 5 years ago

Seems that I partially fixed the issue by modifying my client id and client secret in shim-server/src/main/resources/application.yaml.

I rebuilt using this as a guide https://github.com/openmhealth/shimmer/issues/98, and then ran on postman. I received an authorization url which I copied into a new browser window and authenticated. Finally I was redirected to my redirect url http://localhost:8083/authorize/fitbit/callback. I receive a JSON message, but I see that a bunch of my values are null.

This doesn't seem quite right. Any ideas?

HimavarshaVS commented 2 years ago

Seems that I partially fixed the issue by modifying my client id and client secret in shim-server/src/main/resources/application.yaml.

I rebuilt using this as a guide #98, and then ran on postman. I received an authorization url which I copied into a new browser window and authenticated. Finally I was redirected to my redirect url http://localhost:8083/authorize/fitbit/callback. I receive a JSON message, but I see that a bunch of my values are null.

This doesn't seem quite right. Any ideas?

Hi, By any chance did you get this resolved? I have been facing the same issue . First I wasn't even redirected to callback url . I had to modify manually to get the code. But once I received the code, the api response was all null values : { "type": "ERROR", "details": "Access token denied.", "accessParameters": null, "requestParameters": null } please let me know if you know any possible solutions.

walkabilly commented 2 years ago

Hi,

Very common to have null values. Does the account you are using for testing have Fitbit data associated with it? If not you won’t will get mostly null values. This can also depend on the Fitbit device itself. Older devices might not have things like heart rate.

On Sep 9, 2021, at 10:48, Himavarsha @.**@.>> wrote:

Seems that I partially fixed the issue by modifying my client id and client secret in shim-server/src/main/resources/application.yaml.

I rebuilt using this as a guide #98https://github.com/openmhealth/shimmer/issues/98, and then ran on postman. I received an authorization url which I copied into a new browser window and authenticated. Finally I was redirected to my redirect url http://localhost:8083/authorize/fitbit/callback. I receive a JSON message, but I see that a bunch of my values are null.

This doesn't seem quite right. Any ideas?

Hi, By any chance did you get this resolved? I have been facing the same issue . First I wasn't even redirected to callback url . I had to modify manually to get the code. But once I received the code, the api response was all null values : { "type": "ERROR", "details": "Access token denied.", "accessParameters": null, "requestParameters": null } please let me know if you know any possible solutions.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/openmhealth/shimmer/issues/120#issuecomment-916083553, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADI6A5M47WMA3TBLXOW46LLUBCXZ3ANCNFSM4H7AUTRA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

HimavarshaVS commented 2 years ago

Hi, Very common to have null values. Does the account you are using for testing have Fitbit data associated with it? If not you won’t will get mostly null values. This can also depend on the Fitbit device itself. Older devices might not have things like heart rate. On Sep 9, 2021, at 10:48, Himavarsha @.**@.>> wrote: Seems that I partially fixed the issue by modifying my client id and client secret in shim-server/src/main/resources/application.yaml. I rebuilt using this as a guide #98<#98>, and then ran on postman. I received an authorization url which I copied into a new browser window and authenticated. Finally I was redirected to my redirect url http://localhost:8083/authorize/fitbit/callback. I receive a JSON message, but I see that a bunch of my values are null. This doesn't seem quite right. Any ideas? Hi, By any chance did you get this resolved? I have been facing the same issue . First I wasn't even redirected to callback url . I had to modify manually to get the code. But once I received the code, the api response was all null values : { "type": "ERROR", "details": "Access token denied.", "accessParameters": null, "requestParameters": null } please let me know if you know any possible solutions. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#120 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADI6A5M47WMA3TBLXOW46LLUBCXZ3ANCNFSM4H7AUTRA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

yes the account has data. I tried via fitbit debug console. I was able to fetch the data. I ran docker images after modifying resource-server.env (client id, client secret). I entered the redirect url mentioned in fitbit dev apps in OPENMHEALTH_SHIMMER_CLIENT_REDIRECT_URL. But I am getting error : Developer information: invalid_request - Invalid redirect_uri parameter value. Can you please guide me on this too.