Withings change to Oauth 2.0 Nokia / Withings Healthmate

[Marlene.C.E]

Hi

I cannot get my Nokia(Withing) scale measurements imported with the fitbit tool.

https://www.fitbit.com/weight/withings

It does access my account and I'm allowed to select a profile but there is an error when trying to download my data.

• Unable to download Withings data at this time. Withings server returned the following error: Cannot set value of the field additionalMeasurements Field: more

My email is correctly in lowercase as previous posts on this matter suggests.

Fails on both Crome and Edge browers.

Withings does not have any settings on https://healthmate.withings.com/ that seems to be of help.

I'm currently trying to use IFTTT.com to sync but so far it's been less than ideal. For example the weight is doubled when syncing which gave us a good laugh at first..

Pulling my hair over this, especially after reading a fair bit on this forum about syncing before buying the scale.

Is this because Withings is changing to oAuth 2.0?

If not, will it become an issue when they change?

Is it possible for a developer to take a second look at this Withings to Fitbit tool?

Here is some information from Withings regarding their API changes:

http://developer.withings.com/oauth2/release.html

http://developer.withings.com/oauth2/#tag/introduction

Any and all help that you have is most apprieciated.

This is a present for my wife and the Fitbit integration was a key selling point.

Shes using a Fitbit charge 3.

Thank you!

/Marlenes husband Ola 

[SueChem]

Yep, same here.  But this topic says "solved", so I doubt we're going to get any help!

[LanuzaFitbit]

Hello @Brimmers, @elraulo, @cuba_guy, and @SueChem.

I apologize for the delay in my response. Thanks for sharing that you seem to be experiencing the same issue again.

My question in this case would be to ask if you are all getting some sort of error message or if you have tried to disconnect and reconnect the apps from each other. If so, what happens when you try to reconnect them.

I look forward to your reply.

[Dwight27]

Same problem here. Not a problem with the scale. It is syncing just fine with the Withings app. The problem is the integration between Withings and Fitbit. 

[Abys515]

Hi,

Here is the error message I get:

• Oops! An unexpected error occurred. If it continues please report it at help.fitbit.com. Error id: AC44E66F:4284_A92D8E75:01BB_5CBCEB7B_38B4F96:4E29

[Brimmers]

Same message for me, not willing to unlink as this just makes the issue worse!

[Brauer]

This is the error code I get (mine scale stopped synching on April 15):

• Oops! An unexpected error occurred. If it continues please report it at help.fitbit.com. Error id: 6CA2D74B:F182_A92D8E75:01BB_5CBDDCF2_4427CD8:4E29

[Brimmers]

@LanuzaFitbit  any update on this? My accounts have now unlinked and won’t re-link!

[Dwight27]

I give up. Too many issues that I am tired of dealing with for too long. My Aria scale and Fitbit Charge II are in the trash. Replaced with Nokia Body + scale and Withings Hr Sport watch. Life is now good. 

[Abys515]

@LanuzaFitbit  Any update on this?

Further, my Withings account is now unlinked by itself, without me doing it. Just logged in today to see if I could import Withings data and it asked me to link the accounts! It was already linked, last year onwards. Anyway, tried linking and it says (I put in the right username/password and I know because it asked me to choose the user - showed my family’s names):

• Unable to authenticate Withings user. Withings server returned the following error: Exception receiving access token

Seems to me Withings is not happy with what Fitbit sends in its request.

Fitbit, When will this be resolved?

[Brimmers]

@Abys515 @LanuzaFitbit 

I have exactly the same problem, sent @LanuzaFitbit a personal message yesterday but they have chosen to ignore me. The customer service at FitBit is atrocious and they are about to lose a customer. This issue has gone on for 16 days now and it’s not the first time😡

[LanuzaFitbit]

Hello everyone.

Thank you all for taking the time to let us know about this. I apologize for my delayed response. 

This information has been passed on to our team so that it can be looked into. I will be sure to let you all know as soon as we have any updates or news on the situation. 

Thanks for your patience and understanding on this matter.

[loothi]

Same problem, can't get my weight from Healthmate to Fitbit anymore.

Cleaned cache and incognito

Error is

• Unable to authenticate Withings user. Withings server returned the following error: Exception receiving access token

[SunsetRunner]

This issue is not solved. Please revert the status.

[Ludio]

You all are not going to believe this but they flagged it as being solved.

[Brimmers]

It was solved then it broke again, then they fixed it again and now it’s broken again............😡

The worst thing is they don’t seem to care, I for one won’t buy another FitBit product due to the lack of customer service. Why don’t they respond to let us know what’s happening and respond to the personal message I sent to @LanuzaFitbit 

[siul1979]

It's not that it was marked as solved now. This was an old problem and they fixed it. It's broken again, but since it's an old thread, hate they don't support resetting the status.

Hopefully they fix it soon again.

[GuyOnTheAir]

Problem definitely not solved.  This used to work fine in the past but I hadn't used my scale in awhile, and now that I was it wasn't syncing.  So came to try to figure out how to link the two again, and it doesn't work:

• Unable to authenticate Withings user. Withings server returned the following error: Exception receiving access token

I can log into the Withings site just fine.  The wizard is broken.

[msdancenh]

This is the same problem I'm having too

Sent from Yahoo Mail on Android

[LanuzaFitbit]

Hello everyone.

Thanks for bringing this up and sharing that you are experiencing this issue too.

As it has been mentioned this is an issue that happened in the past and it was resolved. Since then it has happened again and our team is looking into it. As soon as we have any updates we will be sure to let everyone know about it.

Please let me know if you have any further questions.

[SunsetRunner]

Hi @LanuzaFitbit, I have a question.
Since this issue has been rise few time now and it can be considered at least a P2 bug, I wonder if you can give us a some tangible timeline of what and when your developers team is going to take action.
As you mention this is a recursive issue and if the API are not changing suddenly any other day (which I assume is not the case) either the bug has not been addressed properly in the first instance or your QA team didn't check the issue at the time of the first solution release.

My questions:
Investigation: is there someone actually looking at the issue? if not, could give us a worst case date you are planning to look into it?
Estimation: if the estimation has been done, could you tell us when you are thinking the solution can be released? (after proper QA testing this time).

General tip: Usually people here get stressed and angry not because the issue itself (we are here to help you to do a better product) but because the lack of clear communication from the moderators ("our team is looking into it" or "bugs fix and performance improvements" are not enough). I know it's risky to expose yourself with REAL data or timelines, but it is part of your job be sure the customers have the clearest info about what you are doing. I assure you people will get less angry.

Thanks,