Closed nebriv closed 1 year ago
Hey there @vangorra, mind taking a look at this issue as it has been labeled with an integration (withings
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
withings documentation withings source (message by IssueLinks)
Hi there, I'm running into this issue, trying to setup Withings, is there any workaround?
I actually almost feel like this might be an issue in the async_generate_url function in the home assistant webhook module here:
It defaults to allow_cloud=False, though I really have no idea what the implications of this are yet...
@gloaysa are you using Nabu Casa cloud?
Aha!
Looks like this might be resolved in this pull request: https://github.com/home-assistant/core/pull/73228
Another issue I had was that my callback urls in Withings Dev portal had to reflect the same values configured on Configuration.yml
The external_url and internal_url values in the configuration file need to match whatever you used in the Withings page as well as when configuring the Withings integration, the URL you are using to connect to Home Assistant need to match also the external_url or internal_url values.
For example:
Assuming you have Home Assistant running on 10.0.0.20:8123 and you access it using that in the browser, I believe that the internal_url needs to have that url as well as the Withings Dev. Also, just provide the base URL and Port in the configuration.yml file. There is no need to provide ouath authentication path as this will be added automatically.
Lastly, it seems that you need to have a valid domain pointing to your Home Assistant instance for the webhooks to work.
Withings tries to Connect to those to deliver the information on sensor changes.
Hope that helps!
On Tue, Jun 14, 2022 at 5:55 PM Ben Virgilio @.***> wrote:
Aha!
Looks like this might be resolved in this pull request:
73228 https://github.com/home-assistant/core/pull/73228
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/73200#issuecomment-1155860016, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMDXJ3OUOFVV6PVVFFWEHDVPESZFANCNFSM5YFA5B4A . You are receiving this because you are subscribed to this thread.Message ID: @.***>
@nebriv thanks for coming back to me. I was able to fix it following this workaround. I can live with it until https://github.com/home-assistant/core/pull/73228 is merged and deployed.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
The current Withings integration is using the incorrect webhook URL (it is using the internal webhook endpoint, instead of the external endpoint). This appears to be an issue that was repeatedly opened in 2020/2021, however the issues have been closed and locked.
What version of Home Assistant Core has the issue?
Core-2022.6.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Withings
Link to integration documentation on our website
https://www.home-assistant.io/integrations/withings/
Diagnostics information
Editing /usr/local/lib/python3.9/site-packages/withings_api/init.py on line ~345 to override the callbackurl to the correct webhook url instead of using the internal IP address works. I'm not sure where the current webhook url is picked up from.
Webhook configuration:
Network Configuration:
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
Other relevant issues: https://github.com/home-assistant/core/issues/46425