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
Withings Sleep Data for Multiple Users Doesn't Load #116365
Comments
Hey there @joostlek, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) withings documentation |
I've heard this before but this is probably the most coherent story yet. So let's look into this. Note: I am currently in the crunch of my thesis so I won't have the best response times these days. Can you turn on debug logging and reload all entries? |
That's definitely understandable, and I remember thesis crunch time. Good luck! home-assistant_withings_2024-05-01T13-51-59.635Z.log I've tried to collapse the logs down to just Withings-related events |
following along, I'm experiencing this also. |
The problem
My wife and I both have Withings Sleep Tracking Mats, hooked up to one account. My wife, my daughter, and I have users that are tied to a Withings scale. Around the time of the big Withings rewrite, the second user stopped working. All three users can log in to Withings and be authenticated, but only I (as the primary user) seem to have webhooks working. Only my wife sees this (webhooks_connected == false), while my daughter and I do not:
What version of Home Assistant Core has the issue?
core-2024.4.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Withings
Link to integration documentation on our website
https://www.home-assistant.io/integrations/withings/
Diagnostics information
config_entry-withings-3e59cb909d9535cb097c7224c9ab2911.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: