Read the statement by Michael Teeuw here.
Withings
-
Ah, OK,
Now a different error.
When I get to Step 3, do I stop there or continue on (I’m getting a Bad Request on step 4)
Also it says in step 2 I should get a URL once I access the user - but I get Access Granted - and another token - no URL.
To be clear about the parameters for the config.js:
oath_consumer key is the key given in the partner app page. under My Keys and called APIKey
oauth_signature is listed right at the bottom in the black box in step 3.
clientID - no idea what that is
oauth_token is taken from the black box in step 3 and is highlighted. There are two copies of it.
Oh, One last request about functionality. It would be great if you could specify in Config.js which readings are actually shown. I only use the scales and so the other stuff is superfluous. I suspect the majority of people would not necessarily have the full set (steps and sleep).
-
Seems that you are not using correct parameters in the Withings authentification process:
-
Step1 : Use API keys and API secret generated during your Withings apps creation.
You get a result URL with oauth_token and oauth_token_secret. -
Step2: Use oath_token and oauth_token_secret generated at step1. This will generate a result URL. Click on it and look at the adress bar, you will get in the URL your userid (6 digits), ‘&userid=xxxxxxx’
-
Step3: use the userid got from step2. you will get an URL result with oauth_signature and oauth_token.
Hope it helps.
Selecting the data you want to display is the next step, that is why currently this is just a basic module and I did not yet published a official release.
-
-
@matt25 Hi,
Thanks, with your pointers, I got through to step 4 and the resultant URL does retrieve data so I know the credentials are working- but putting that into the config.js (all info it looks like you ask for is contained in that request URL), I still get zeros.
I suspect I’m close, but not sure what could be wrong.
-
@frog I’m getting the same results as you. I suspect the MM_Withings.js script needs to be tweaked a bit. I manually tested all the variables used in the config.js file, confirming that the API is setup correctly and returning data. My guess is that the output string of the MM_Withings.js script is different than what I’m testing.
-
-
Per the console, I do receive weight (poids=90.67;) and date (date=1481195497) information, but then see the following:
status=0
error TypeError: Cannot read property ‘date’ of undefined
error TypeError: Cannot read property ‘body’ of undefined
data=undefined
data is null -
@ih800a
ok thanks.
Do you only have a Withings scale, correct? or do you also have a watch or others?My guess is that as my module is just currently a proof of concept, I try to display all the related information (weight, sleep, activity ) but if you do not have the withings device related it crashes.
Also, could you tell me when:
“error TypeError: Cannot read property ‘date’ of undefined”
which line in the MM_Withings.js script is related. It should be written in the debug console. Thanks -
I have a few Withings devices (pulse, scale, BP monitor, etc), so your theory makes good sense. Kudos, by the way on this proof of concept - I like it and this will be one of my first Pi / Magic Mirror / module customizations, so I appreciate any insight you have.
The errors appear at MM_Withings.js:208, which I believe is the line that writes the error to the log.
-
I corrected some things on the module :
- correction of the @ih800a bug (I had the same)
- add external CSS
- add the loader
- add translation
I’ll review the design of the module
[card:aluini/MM_Withings]
-
Hi @aluini, is your module still working correctly? I’m only getting the weight. :)
I have an Body Cardio Scale, do I have to define this somewhere?Thanks!
-
-
I can not get it to work. I only have the scale.
-
I looked at the module and it just need to be updated however, I can find a way to be able to get the JSON data to be displayed. All I get is a {“status”:342,“error”:“The signature (using Oauth) is invalid”}
I tried almost everything already.
If anyone can give it a try and make that work, I can update the module and even create new features.
-
Hello,
I also try to make it work, but I didn’t succed. Probably I did some wrong behaviour during the oAuth process.
At the end I can see on my MagicMirror logs an error 283, that correspond according to Nokia API website to : “283 : Token is invalid or doesn’t exist”.
I considered it was OAuth version 1.0 because it look like it.
Also it is written on Nokia website :
“The Health Mate API is now fully functional with OAuth 2.0 authentication protocol.
Therefore, the OAuth 1.0 process will no longer be supported beginning:
November 30, 2018”Also I do not really want to fight to make it work if the service will be cut by Nokia/Withings on a few months.
Does someone have the knowledge to update this module with OAuth 2.0 ?
-
Anybody get this working with the new OAuth 2.0?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login