Can't authorise Withings

[quantummobile]

Home Assistant release with the issue:

0.99.0

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io Component/platform:

https://www.home-assistant.io/components/withings/

Description of problem:

Can't authorise the app, get error:

500 Internal Server Error Server got itself in trouble

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[vangorra]

You should have to change nothing as the new ha code will overwrite any changes. If you're using a custom component, then you'll probably have to remove it.

[carlostico]

You should have to change nothing as the new ha code will overwrite any changes. If you're using a custom component, then you'll probably have to remove it.

Just used the "Custom deps deployment" and fixed the auth problem...

[northpower25]

With HA Version 0.100.1 and 0.100.2 after i click on "allow this app" i got the error "call to the webservice failed" . Has anyone else the same problem by activate the witings connection to Home Assistant? (API URI URL and HA URL are reachable from the web)

[philipp-schottkowsky]

With HA Version 0.100.1 and 0.100.2 after i click on "allow this app" i got the error "call to the webservice failed" . Has anyone else the same problem by activate the witings connection to Home Assistant? (API URI URL and HA URL are reachable from the web)

Yes, I also get the message "call to the webservice failed" with HA Version 0.100.2. With version before 0.100 I got the message "500 Internal Server Error".

[northpower25]

@philipp-schottowsky Follow the following bug i‘ve report to that issue https://github.com/home-assistant/home-assistant/issues/27619

[velijv]

The workaround works. However I ran into this issue:

• in Withings OAuth page, you can't add a port (https://xxx.duckdns.org:8123) This is not a valid URL. It redirects back to my DuckDNS url, and I can add the port number manually in the address bar, and it syncs. However this wont work for its automatic polling...

[northpower25]

With HA Version 0.100.1 and 0.100.2 after i click on "allow this app" i got the error "call to the webservice failed" . Has anyone else the same problem by activate the witings connection to Home Assistant? (API URI URL and HA URL are reachable from the web)

Yes, I also get the message "call to the webservice failed" with HA Version 0.100.2. With version before 0.100 I got the message "500 Internal Server Error".

after i wrote to Withings SDK Support now if works it should be for me an withings problem and not an integration problem.

[roitto]

I have same issue as the @velijv

I switched to port 430 and i was able to connect to the api. I would rather still use different port than 430.

But i think that the home assistant is not currently polling data from the api. I get lot of these "No measure groups found, setting state to None" or "Sleep data has no series, setting state to None" to my logs.

[momab]

Is there any news regarding this Problem? Do I HAVE to make Home Assistant publicly available for the Withings Integration to work?

[vangorra]

This is the only supported method of connecting. Withings requires the URL you provide must be https running in port 443 and is accessible. Their servers check when you set the callback URL for the developer account.

For development purposes, your can work around this very easily if you understand how oauth2 works. This method is unsupported, hence it does not exist in the documentation as it gets complicated. When setting up you withings dev account, the callback URL can be anything that withings can check is online when you setup your developer account, like https://myblackhole.somedomain.com/auth/external/callback. So long as that has a valid certificate and responds at all, the withings server is satisfied. You can even shut off the http server after setting up the dev account. Withings doesn't recheck, as far as I can tell. On the HA side, your base URL needs to be https://myblackhole.somedomain.com. When you setup then integration, the withings server will require you to authorize this app and redirect you to https://myblackhole.somedomain.com/auth/external/callback with a lot of data on the path. Just replace https://myblackhole.somedomain.com in the URL with the internal address of the HA instance that started the setup. Something like http://10.10.0 22:8123

[chriswood1001]

Hi @vangorra — Now that home assistant has migrated from base_url to external/internal_url, is there another workaround? I've successfully paired in the past, (always with difficulty and several attempts), but now I'm completely blocked. This is what I've tried:

1) Remove base_url from the http section of configuration.yaml (restart) 2) Navigate to home assistant, /config/core and set external_url to "https://xxxx.duckdns.org" and internal_url to "http://192.168.7.xxx:8123" (restart) 3) Navigate to /config/integrations, select Withings, new tab opens. 4) The URL (https://account.withings.com/oauth2_user/....) has "redirect_uri=http%3A%2F%2F192.168.7.xxx%3A8123%2Fauth%2Fexternal%2Fcallback", so I change that to "redirect_uri=https%3A%2F%2Fxxxx.duckdns.org%2Fauth%2Fexternal%2Fcallback" and hit enter (navigate there). 5) I select my user, select "Allow this app" 6) Withings refreshes back to step 4. I change the URL (again), select my user (again), Allow this app (again) 7) I'm directed to: "https://xxxx.duckdns.org/auth/external/callback?code=abc&state=xyz" with the message: "500 Internal Server Error. Server got itself in trouble"

I've tried making the request when signed into home assistant using my internal (192.168.7.xxx:8123) URL, and when signed in to external (https://xxxx.duckdns.org), and from outside my network (mobile data). I've also double checked that my Withings developer account has the callback URL: "https://xxxx.duckdns.org/auth/external/callback"

Thoughts? I appreciate all the help.

[wills106]

@chriswood1001 Try setting your "internal url" to your duckdns one. That's how I got it to work on my setup

[chriswood1001]

@wills106 — perfect! that worked. It's not intuitive to set the internal_url for an external service, but what matters is that it worked.

[matteos1]

@wills106 work