-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Can't authorise Withings #26716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same here for docker. |
As per ticket #26613 I can't Authorise Withings. I couldn't get this to work on 0.99b1 - 0.99b3 In my configuration.yaml I have the following:
When I go to the integrations page and select Withings and then choose my profile/user I am redirected to the authorization API website.
I am running HASSIO as a native package on a Synology NAS, also using the built in reverse proxy. This is the log I get:
|
I have the same issue - first it failed with invalid call back ID - fixed by adding the nabu casa base URL to config and the Withings API, then a failure to redirect from the auth screen to HA - fixed by not having a space in the profile Now I am hitting the same wall - first attempt to link bounces you back to the integrations screen, second the 500 server error.
|
Same here. Continue running the Withings component as a custom component and everythings works. The problems appear when switching to the merged component in 0.99. |
Same issue for me with the following error log: |
I have this message error for me
|
Are you accessing HA locally? Ie 192.168.xxx.xxx
Then access it through your external address. |
Yes I acces to HA locally or with my nabu account
In the configuration.yaml ? at the beginning ? Thnaks for help |
Hello again I put
at the beginning of my Configuration Yaml
|
I think we just need to sit and wait for now. |
When i put my nabu adress on base_url and in withings callback url
|
Yea, that's correct. |
I had the same problem ( Server got itself in trouble/Missing token). I'm running HA on a raspberry in docker ( homeassistant/home-assistant:0.99.0 ). To be able to successfully finish the config flow, I had to change a line in the nokia lib ( https://github.com/orcasgit/python-nokia/blob/1.2.0/nokia/__init__.py#L86 ). I've added to the fetch_token() call. |
Hi @vangorra, any chance to have this fixed soon? |
My understanding of this issue is due to a change in withings API and a request as been made for the lib: orcasgit/python-nokia#38 |
Same issue here, it loops then 500 error |
Can confirm this fix worked for me! |
I'm afraid it is a bit too complicated for me. |
As mentioned and referenced above, this is an issue with the python-nokia library, not Home Assistant. It will need to be resolved there in order that the changes propagate through to HA. |
Yeah, and what exactly needs to be done and by whom to resolve this issue? What's expected resolution time? |
@quantummobile check the link i posted above. |
I'm sorry, but that doesn't make things any clearer to me :) |
Can I find this location somewhere in a hass.io install to and change it manually or do I need to wait for a patch |
The maintainer of the Python script needs to release a New version that
contains this fix for HA to reflect the fix. In the mean time you can
change your local files as described above.
|
I changed it in my hassio setup today and had the same path as described.
|
Hmm, I'm missing the nokia folder |
Same here, hassio on a VM, no nokia folder |
We are waiting on the Nokia python library being updated, which is out off the hands of the HomeAssistant people. |
@wills106 Is there an ongoing PR and/or issue to link to? So we home assistant users can go and try to influence the importance of this update 😄 |
Try to look at |
i did the workaround and im still getting the same 500 internal server error |
the maintainer confirmed the Project is dead. I'll fork and fix this weekend |
Fix is ready to be merged. |
If we did any of the workarounds here do we need to change something back once it's in the release? |
I am really sorry but I don't get what I have to do to get my Withings devices to work with HA. Is the workaround as mentioned by @Skeletorjus still needed after the fix of @vangorra? |
Anyone ? |
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... |
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". |
@philipp-schottowsky |
The workaround works. However I ran into this issue:
|
after i wrote to Withings SDK Support now if works it should be for me an withings problem and not an integration problem. |
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 |
Is there any news regarding this Problem? |
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. |
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:
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? |
@chriswood1001 Try setting your "internal url" to your duckdns one. |
@wills106 — perfect! that worked. |
@wills106 work |
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:
The text was updated successfully, but these errors were encountered: