Withings - Showing as Unknown and/or Showing Detected even when not in bed

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.

https://www.home-assistant.io

Apache License 2.0

70.97k stars 29.63k forks source link

Withings - Showing as Unknown and/or Showing Detected even when not in bed #102359

Closed oneseventhree closed 8 months ago

oneseventhree commented 10 months ago

The problem

Sensor shows as unavailable intermittently:

The old Withings integration I never had issues with (apart from installation) but after it was installed it worked perfetly for years. This new integration is a bit more buggy.

I've turned on loggings so hopefully something shows up

What version of Home Assistant Core has the issue?

core-2023.10.3

What was the last working version of Home Assistant Core?

Pre core-2023.10.x

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

joostlek commented 8 months ago

Made another update, if you could run the code again it will use the new update

GWorswick commented 8 months ago

I've run the curl, rebooted and turned logging back on :)

dcmeglio commented 8 months ago

No issues today but I'll keep monitoring

joostlek commented 8 months ago

I made a final update today and it seems the final one, now need to figure out how to test it so it can't be regressed

dcmeglio commented 8 months ago

Just installed that version of the PR. I'll see how it goes

naschine commented 8 months ago

Not fixed for me with the latest patch. Here are the debug logs (I redacted webhook urls and nabucasa urls, but did a find and replace to keep them consistent. Seems the problem is it's unsubscribing multiple times? FYI I do have 2 bed sensors. I saw at least one other person reporting he has 2 bed sensors too. Maybe that's part of the problem?

Just some bits of information to add to the case:

My internet connection disconnects every 24 hours for a brief moment (to control the time of it I use a cronjob to kill the pppoed from my router)
I've seen the exception with the CLOUD_CONNECTION_STATE occur around that time
I have two bed sensors as well, so two accounts. One for each device.
Sometimes one of the Withings "devices" wants re-configuration. It prompts me to re-configure device X, I login with the Withings account for X and then it asks me if I want to allow the connection with app Y. So it seems it uses the wrong credentials/Client Id/Secret?

GWorswick commented 8 months ago

I think with the latest test version I ran last night it looks like its fixed and working well! :) @joostlek Thanks man! great work! :)

naschine commented 8 months ago

A little heads up: Since this fix is implemented, all my problems are gone it seems!

So thanks for that @joostlek :)

joostlek commented 8 months ago

Good to hear :)

oneseventhree commented 8 months ago

A little heads up: Since this fix is implemented, all my problems are gone it seems!

So thanks for that @joostlek :)

Mine too! Thank you for sticking through with us :)

sjd17 commented 8 months ago

Same here, thanks @joostlek!

joostlek commented 8 months ago

If you want to support the work I do, please checkout https://github.com/sponsors/joostlek. But don't feel pressured to do so as I do this for love for the platform ❤️