Withings has changed the terms of its public API, and Home Assistant's Withings integration runs on that API. Since 12 October 2026, an account created after the cutoff needs an active Withings+ membership to share health data with any app on the free "Start for Free" plan, according to Withings' API plans page. That includes apps that are already live, and the private developer app every Home Assistant user registers to get a client ID and secret is exactly that kind of app.
Accounts created before the cutoff are not affected and keep sharing data without a membership. Withings+ costs €9.95 a month or €99.50 a year, with the same figures in dollars, according to Withings support. If the membership lapses, sharing pauses; Withings says the history is kept and sharing resumes once the membership is active again. The detour through Apple Health or Google's health platform is closed as well, because the requirement covers those routes too.
Three dates for one cutoff
The plans page says 12 October. A Withings support FAQ, which ties the change to the launch of the Withings AI Connector, an MCP server that links AI assistants to Withings data, gives 00:00 UTC on 13 October. Home Assistant's documentation, updated on 12 October, says accounts created after 11 October. If you set up an account around those days, assume you will need Withings+.
A new plan, and setup that stops halfway
Withings has also split its API into plans. Start for Free covers the core data groups (activity, sleep, body and heart) for up to 10 users, or more after a review by Withings. ECG, AFib, SpO2, vascular age and AHI are listed only for the paid Advanced Biomarkers plan.
The split already shows up in Home Assistant. On 12 October a user reported in issue #186020 that Home Assistant 2026.10.1 could not finish adding Withings with a newly created Start for Free app. The OAuth flow went through, then the config entry failed to authenticate with Withings' message: "One of the data type requested in this API request is not available in your API plan." The user had a Body Comp scale and a BPM Connect, both syncing in the Withings app. As of 18 October the issue is still open and no fix has been merged.
Who is affected
If the integration already works on an older account, nothing changes for now. Someone setting up a first Withings scale today pays for Withings+ on top of the hardware to get readings into Home Assistant, and a newly registered developer app may still hit the plan error until the integration is adapted. The integration was never local either: it gets data from Withings' cloud, and for instant updates through webhooks Home Assistant has to be reachable from the internet over HTTPS on port 443.