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 ?

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.

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]

Nice. I want to test it.
My data from my withings steel also showable?

Thanks!

• 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]

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.

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

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

Hi, sorry, was out last few weeks. Just tried the module on another raspberry card with from scratch installation and I cannot reproduce the issue you describe. When you launch the mirror, do you have any issue in the logs? (use “npm start dev” command). Thanks

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.

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.

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).

Just upload first version of my module. This is more a proof of concept than a complete functional module, but it works fairly well on my mirror.

MM_Withings

Will update and improve it (especially design, if someone could provide me nice icons) and create new post in module section forum.
Module is based on Netatmo module from Christopher Fenner.

Now it’s a case of trying to code it up into a module!

I’m struggling with a few issues at the moment though - I’ve git clone’d and npm install’d, created a test.py file as indicated by the readme and in it I’ve put in it my Withings API key and secret values.

I had to sudo pip install requests_oauthlib as that was a requirement which wasn’t installed.

I’m SO nearly there I think! when my test.py file runs, it generates a Withings URL to authorise the app, I authorise on the website and am given an oauth response verification code, but when I paste it back into the script response, I get an error which i think is at the point the script tries to parse them through auth.get_credentials (after this point, the script gets my last measured weight):

 File "test.py", line 8, in <module>
 creds = auth.get_credentials(oauth_verifier)
 File "/home/pi/MagicMirror/modules/python-withings/withings/__init__.py", line 107, in get_credentials
tokens = oauth.fetch_access_token('%s/access_token' % self.URL)
File "/usr/local/lib/python2.7/dist-packages/requests_oauthlib/oauth1_session.py", line 304, in fetch_access_token
token = self._fetch_token(url, **request_kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests_oauthlib/oauth1_session.py", line 361, in _fetch_token
raise ValueError(error)
ValueError: Unable to decode token from token response. This is commonly caused by an unsuccessful request where a non urlencoded error message is returned. The decoding error was No JSON object could be decoded.

Oh well. It’s progress I suppose.

It’s next on my list to take a look at, but I suspect progress is likely to be slow as my skills are very basic :)