I’ve configured the Withings integration, but the bed sensor isn’t working. All of the others are working. Any ideas?
Sorry for being uninformed. I’ve tried unregistering and reregistering, and I can access the web interface.
The bed sensor reports “unavailable” until you sit on it the first time. If you’ve just installed it but haven’t gotten into bed yet, this is normal. It will also go “unavailable” after every Home Assistant restart too.
I believe the reasoning for this is that it can’t accurately determine state upon Home Assistant restart. So rather than default to “off” (which is the behavior it used to have, and was sometimes incorrect) it now just defaults to “unavailable” until it’s 100% sure of the state.
Huh. Can’t it keep the state or something from previous restarts? Other components do that.
Yeah I had the exact same thought as you, don’t really know how the integration works on the backend though.
Just found the issue which explains this better (in the replies):
2 Likes
My in bed sensor still tell me unavailable.
But for example systolic_blood_pressure_mmhg from withings show me value. So integration is configured correctly.
What can be problem?
This is my config and state of in_bed sensor is unavailavle even after 24h
withings:
client_id: be9b*********6779
client_secret: 424f7****34a
use_webhook: true
Same here, it is never available for me. Sleep data is coming in. I’ve double checked the callback url with Withings, made sure it is my external nabu casa one and checked it with the documentation. Checked that the external URL was set to cloud in the Config UI. Checked that webhooks is set to true in the config. Removed the entire Withings integration, rebooted. The webhook configs were gone in the cloud settings. Then reconnected all 4 users again, went to the cloud settings and enabled all 4 webhooks again. Rebooted again. Then went to lie in bed for more than 15 minutes, but alas. Still nothing.
1 Like
Same here. Did you managed to solve it?
Most important is that the configuration.yaml contains the externally path of your instance as specified in the documentation when you set up the integration. Just saying you use nabu casa in the settings won’t do. The external url must be the same as the beginning of the url that you specified to Withings when creating your app. I set up the integration in a browser using the external url to be sure, I’m not sure if that is required but that seems logical to me.
Also turn on the webhook in the cloud configuration if it doesn’t do so automatically when the integration has added it. And then, go to bed because the sensor is unavailable until the first call comes in.
If that does not work, there is the option of using ifttt as a workaround, but with the above I finally got it to work.
I’m experiencing an issue with the Withings integration in Home Assistant after updating to Core 2024.11.3, as the Bed Occupancy sensor has disappeared from the available entities. I’ve tried removing and re-adding the integration, but that didn’t help, and after waiting overnight for the sensor to reappear, it still hasn’t shown up. Has anyone else encountered this problem or have any suggestions for troubleshooting?