Skip to content

Releases

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 16:33

Added

  • Support for Body Comp (WBS12) (#5, thanks @tinkerden for testing). It's discovered from its Bluetooth advertisement and reads over Withings' newer Bluetooth service. Pairing uses the 6-digit code after a short button press. Sensors: weight, body composition and heart rate per user, guest weigh-ins, battery and last sync. It never sends the sync acknowledgement (SYNC_OK): the scale doesn't need it, and readings stay on the scale for the Withings app.
  • tools/fetch_kl.py --model 18 fetches a Body Comp's key, and tools/read_measurements.py reads the model saved by fetch_kl.py.

Changed

  • The README says that accounts that sign in with an emailed code need a password to fetch the key.

v0.5.0b1

v0.5.0b1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 05 Nov 00:46

This is a beta: HACS offers it only if you turn on the integration's Pre-release switch.

Added

  • Experimental support for Body Comp (WBS12) (#5). It's discovered from its Bluetooth advertisement and reads over Withings' newer Bluetooth service. Pairing uses the 6-digit code after a short button press. It's based on one community report and hasn't been tested with Home Assistant yet; it never sends the sync acknowledgement (SYNC_OK), whose effect on this model is unknown.
  • tools/fetch_kl.py --model 18 fetches a Body Comp's key, and tools/read_measurements.py reads the model saved by fetch_kl.py.

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 29 Oct 17:36

Added

  • Support for Body (WBS06), also sold as Nokia Body (#3, thanks @lientry). It sends its readings over Bluetooth Classic rather than Bluetooth Low Energy, so Home Assistant listens for the scale's connection after a weigh-in instead of polling it. Setup pairs without a code. It needs a local Bluetooth adapter on Linux (BlueZ); ESPHome Bluetooth proxies can't do it. Sensors: weight and last weigh-in per user, plus battery and last sync. See docs/wbs06.md.

Changed

  • Fetching the key with your Withings login now picks the scale that matches the one being set up, by model and Bluetooth address. When an account has several scales of the same model and none matches, setup says so instead of taking the first one; enter the key yourself in that case.
  • tools/fetch_kl.py takes --model 7 for the Body, and stops instead of guessing when the account has several scales of that model.

v0.4.0b1

v0.4.0b1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Oct 18:08

This is a beta: HACS offers it only if you turn on the integration's Pre-release switch.

Added

  • Withings BeamO (beta). Discovery, setup and a body temperature sensor per person, read-only: nothing is ever deleted or acknowledged on the BeamO. Built from a community report (#1) and not yet tested with Home Assistant. See the README for what's known and what isn't.
  • Diagnostics show the device model and the flags in its FD77 advertisement data.

Changed

  • Setup and messages say "device" where they no longer mean only the scale. Existing scale setups are unchanged.

Fixed

  • The CLI continues reading stored measurements if the optional connection-reason query times out, matching the library's behavior.

v0.3.3

Choose a tag to compare

@github-actions github-actions released this 24 Oct 12:22

Changed

  • A device that fails to prove it knows the key gets no further commands: nothing is read from it and no sync acknowledgement is sent to it. Before, its readings were read and then ignored.

Fixed

  • Messages a device sends on its own, or that are left over from an earlier request, are no longer mistaken for the answer to a request. Some Withings devices send several right after connecting.
  • A stored measurement record that can't be decoded is skipped instead of failing the whole sync, and values that follow it are no longer attached to the previous weigh-in.

v0.3.2

Choose a tag to compare

@github-actions github-actions released this 17 Oct 19:32

Added

  • Discovery logs other Withings devices it doesn't support (name and model ID, not the address) at debug level, and the README explains how to share that to help add a device.

Changed

  • New integration icon: a white scale with a Bluetooth display.
  • The README and description now say the integration supports the Withings Body Smart.

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 16 Oct 21:45

Changed

  • Readings are ignored when the device fails to prove it knows the key (mutual authentication). Before, they were recorded with a warning. A real scale always passes this check; a device impersonating the scale's advertisement can't.

Fixed

  • An unexpected error during pairing (for example when the system D-Bus can't be reached) shows the "Pairing failed" step with the error and a retry, instead of "Unknown error".

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 20:12

Added

  • Pairing during setup. The scale only shares measurements over a Bluetooth connection paired with the 6-digit code on its display. Setup now asks you to hold the scale's button, waits for its setup-mode signal, and asks for the code. Home Assistant registers a temporary BlueZ pairing agent for this, and the pairing is stored on the host. Tested on a Raspberry Pi 4 with Home Assistant OS.
  • Reauthentication when pairing is lost. If the scale refuses a connection because it isn't paired (for example after a battery change), Home Assistant raises "Reauthentication required" and walks you through pairing again. You can also re-pair at any time with Reconfigure.

Fixed

  • When the scale drops the Bluetooth link mid-session, the sync fails at once and retries on the next advertisement, instead of waiting for a timeout. Linux (BlueZ) leaves the pending call hanging in this case.
  • Per-user devices link to the scale with via_device_id. The old via_device form is deprecated and stops working in Home Assistant 2027.8.

Changed

  • Connection retries use the newest Bluetooth device data, and "can't connect" warnings include Home Assistant's reachability diagnostics.
  • "Enable debug logging" also shows the connection retry library's attempts (bleak_retry_connector).

Known limitations

  • Pairing works with Bluetooth adapters attached to the Home Assistant host on Linux. ESPHome Bluetooth proxies can't pair with a code, and a proxy without the pairing can't read the scale (upstream habluetooth issue #628).
  • After pairing, the scale may display "Setup failed". This is harmless.

v0.2.2

Choose a tag to compare

@github-actions github-actions released this 16 Oct 16:59

Fixed

  • A Bluetooth session that hangs, seen on a Raspberry Pi adapter after connecting, no longer blocks every later sync until a restart. Subscribing, each write and the whole session now have timeouts.

Changed

  • Debug logs show each session step (subscribing, subscribed, every message) and when the scale disconnects.

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 16 Oct 16:44

Fixed

  • After a failed connection, retry on the scale's next advertisement instead of waiting 30 seconds. The advertising window is short, so a weak signal used to mean a missed weigh-in.
  • Scales discovered without a name (common with passive or distant adapters) are titled "Body Smart" instead of their Bluetooth address. Existing entries are renamed.

Changed

  • Every failed sync logs a warning with the step, elapsed time, adapter and signal strength, not just the first failure.