12-05-2018 10:25 - edited 12-06-2018 13:36
12-05-2018 10:25 - edited 12-06-2018 13:36
I have been trying for two days to link my wife's FitBit account with our Withings scale. Using the following link https://www.fitbit.com/weight/withings it will always result in the same error.
"Unable to authenticate Withings user. Withings server returned the following error: Unknown status code."
How do we address the account linking issue shown above?
I was able to link my account a year ago, but I recently tried to link my wife's Fitbit account with her Withings profile and it didn't work.
I've added a screenshot below. Note: It's occurring on the FitBit page to link the Withings scale.
Error Example
12-10-2018 13:19 - edited 12-10-2018 13:22
12-10-2018 13:19 - edited 12-10-2018 13:22
If you are hosting code that authenticates to Withings via an API and your system is not calling that API properly, contacting Withings will not fix the problem. This being said, pawning the issue off on Withings is not the right approach. Your web developers should at a minimum validate that the code they are hosting is properly calling the Withings API and if not fix the calls associated with the linkage. If they (the developers) validate that the FitBit site is properly calling the Withings API, and Withings is failing to accept the data sent to them via the web service call. Then we can go to Withings with solid proof the issue exists on their system. Otherwise all we the consumers will have is two companies pointing the finger at each other. Please do us the courtesy of having someone look at this issue. I’ve spent my career in software/hardware and this is not the way to handle such a customer complaint. The current approach holds no one accountable for this issue because we the customers can’t debug these back end calls without your help. We are FitBit customers as much as we are Withings customers.
12-10-2018 14:26
12-10-2018 14:26
Hey guys, also having the same issue, it all startet on November 30th. And guess what i found in another thread here. Someone wrote:
"Not sure if is related, but on November 30, Withings closed OAuth 1.0 API.
They migrated to OAuth 2.0. Maybe a developer needs to upgrade the code."
So maybe this could fix the issue? I don`t think Fitbit really wants us to buy the Aria 2 right? 🙂
12-10-2018 15:47 - edited 12-10-2018 15:50
12-10-2018 15:47 - edited 12-10-2018 15:50
Daniel, you are probably correct or at least partly. OAuth 1 vs 2 is a huge difference as it’s a complete rewrite and the signature generation has different requirements. What we don’t know is if FitBit pulls the data from Withings or if Withings pushes the data to FitBit. Either way both companies are huring their users for not being homogeneous. You can’t have a feature that people use and then stop supporting it/us. I have a family of six and we all use FitBit trackers and Withings scales. Many of us wouldn’t have purchased Withings / FitBit if the integration didn’t exist. I have some of my family linked (pre-integration issue). Others on here took support’s advice to deactivate and attempted reactivate. They are now stuck in a broken state per supports advice.
1. To link accounts we must login into FitBits web portal.
2. FitBit’s portal asks for our Withings credentials.
So who is responsible for this integration? IMHO it’s FitBit because the account sync page is on FitBit’s site and it request’s our Withings login credentials. This process most likely creates the authentication token that FitBit uses to pull the weight information from the linked account.
12-10-2018 15:55
12-10-2018 15:55
Yes, you`re right. To be honest i don`t know which party can fix the issue permanently. The error message says that withings server is not responding correctly. The question is why. Because of fitbit that is still sending a bad request or because of withings having issues?
Anyway it`s just guessing. Hopefully fitbit again takes a deeper look to see if they can help us. Also there are more than a few users connecting their withings scale to fitbit. And every single one has to enter data manually now. Come on it is 2018...that`s not smart 🙂
12-10-2018 22:38 - edited 12-10-2018 22:49
12-10-2018 22:38 - edited 12-10-2018 22:49
Editing: I realize this site doesn't make it clear who is replying to whom! I take it you're replying to Fitbit, Ludio, and I agree wholeheartedly.
Lanuza Fitbit:
Please show that you care about your customers and investigate this issue. The superficial claim of "third party integrations" does not hold water. Any integration has two sides. The side that OWNS the data has the power, and the side that consumes the data has to do everything they can to get, including adapting to any changes the owner makes. So while it may be that Withings changed something that made Fitbit's code no longer able to get the data, the onus is on Fitbit to either convince Withings to change it back, or on Fitbit to change it back.
12-11-2018 04:08
12-11-2018 04:08
I agree that the API change would indeed be Withings fault. The linkage and update would fall upon FitBit to keep up with the API change as they are the consumer of the data. I can understand that OAuth 2 was a security consideration, however if it’s simply API related APIs should be versioned. This way consumers of the old system are not impacted by a future release (eg. some.server.com/v1/api vs some.server.com/v2/api).
12-11-2018 06:31
12-11-2018 06:31
I'm also having issues, but slightly different error compared to the prior post.
12-11-2018 11:54
12-11-2018 11:54
All,
Withings replied and they are looking into the issue. Will let you know what I get back. Please see below:
Hello,
Thank you for your response. Our development team is currently working on an update to resolve this issue, Once the update is released I will notify you so we can get this issue resolved. I apologize for the inconvenience this may have caused you.
Let me know if you still have any other questions or concerns.
Have a great day!
Best regards,
James
12-12-2018 03:16
12-12-2018 03:16
Hello, Got the following response today...from Withings
Your case has been referred to our specialist team for additional review. We're committed to answering your questions and getting you a fast and effective resolution for any issue you may be experiencing. We will contact you again with an update about your case as soon as possible, usually within one business day of your previous reply to us. Customer Service | **Withings** |
12-12-2018 08:03
12-12-2018 08:03
Received the same yesterday after some back and forth and sending them a screenshot of the error.
12-12-2018 21:19
12-12-2018 21:19
Having the same issue, same error.
Frustrating, I replaced my ever faulty Aria scale with a Withings after researching that this worked and now it has stopped just after I get my new scale.
12-13-2018 07:33
12-13-2018 07:33
Hello everyone.
Thanks for sharing what you have been told by Whithings. Hopefully they will provide a resolution to the situation soon.
If there is anything else I can help you with, please let me know.
12-13-2018 09:31
12-13-2018 09:31
Hello everyone.
As I indicated in other thread, Whithings is aware of the situation. Other users have been getting in touch with them and they have mentioned that they are looking in to it so hopefully it will be resolved soon.
Feel free to reach out if you need any further questions.
12-16-2018 08:49
12-16-2018 08:49
As a customer of both FitBit and Withings, I would expect you both to be working on a solution and not putting it off on the others end of the problem. The problem is with both of you as stated over and over again by others.
12-16-2018 10:51
12-16-2018 10:51
Thanks, hopefully it will be resolved soon.
12-17-2018 01:06
12-17-2018 01:06
I tried it several times, without caps.
no success.
12-17-2018 11:18
12-17-2018 11:18
Welcome to the Forums @Friedl and @elise44.
Thanks for letting us know. Hopefully Withings will resolve this situation soon.
If you have the time, be sure to visit one of our Discussion boards. Maybe you will find a topic that interests you.
Let me know if you have any further questions.
12-22-2018 12:13
12-22-2018 12:13
Guess I will be taking back the Versa's I got for my wife and kids since this isnt working and not much from the face of the company on this discussion board other than its Withings not us...
This is why I left fitbit years ago, I come back due to the promise of the Versa and this is how it begins....
You would think with the amount of competition in their market they would do better.
12-24-2018 04:37
12-24-2018 04:37
Dont have a Fitbit right now but have anybody tried the IFTTT solution ?
https://ifttt.com/applets/229124p-withings-fitbit?term=fitbit
or
Can be that there is some other applets that work there. Should be nice if anybody have the time to test
12-24-2018 08:14
12-24-2018 08:14
Is there any updates on this, I still can not connect fitbit with Withings scale.