@frog Ok sorry. When creating a withings app it is necessary to write something in the application website (127.0.0.1). In the Withings authentification process, do not fill the the ‘callback url’ field. Hope it helps.
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.
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:
error TypeError: Cannot read property ‘date’ of undefined
error TypeError: Cannot read property ‘body’ of undefined
data is null
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.
aluini last edited by
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