Keep sensor values during BLE disconnects (last known measurement)

- user measurement and derived sensors no longer gate availability on coordinator.connected; they stay available with the last known value so history graphs show no gap

- scale-level Connected binary sensor still reports link state; when a new measurement arrives entities update normally

- regression test: sensor.py must not reference BLE connection state

Release 0.8.1

Author: kapilmahawar

CHANGELOG.md

@@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.8.1] - 2026-09-08
+
+### Fixed
+- **Sensor state persistence across BLE disconnects**: user measurement and
+  derived sensors no longer gate availability on the BLE connection state.
+  Once a valid measurement exists, entities keep their last known value
+  (and stay `available`) while the scale sleeps/disconnects, so history
+  graphs keep a continuous line instead of showing a gap. The scale-level
+  `Connected` binary sensor still reports link state independently.
+
 ## [0.8.0] - 2026-09-08
 
 ### Changed (UI/UX polish only - no functionality/storage changes)

custom_components/realme_scale/manifest.json

@@ -8,7 +8,7 @@
   "issue_tracker": "https://github.com/kapilmahawar/realme-scale-ha/issues",
   "iot_class": "local_push",
   "integration_type": "device",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "bluetooth": [
     {
       "service_uuid": "0000a602-0000-1000-8000-00805f9b34fb"

custom_components/realme_scale/sensor.py

@@ -277,9 +277,13 @@ def _measurement(self):
 
     @property
     def available(self) -> bool:
-        """Only available while the scale link is up and we have a value."""
-        if not self.coordinator.connected:
-            return False
+        """Available whenever we have a (last known) measurement value.
+
+        Intentionally independent of the BLE link state: once a valid
+        measurement exists it stays available during disconnects so history
+        graphs keep the last known value instead of showing a gap.  Link
+        state is reported by the scale-level ``Connected`` binary sensor.
+        """
         measurement = self._measurement()
         if measurement is None:
             return False
@@ -403,9 +407,11 @@ def _computed(self) -> object | None:
 
     @property
     def available(self) -> bool:
-        """Available when the scale link is up and a value can be derived."""
-        if not self.coordinator.connected:
-            return False
+        """Available whenever a value can be derived from the last reading.
+
+        Independent of the BLE link state so derived metrics keep their last
+        known value across disconnects (see RealmeScaleUserSensor).
+        """
         return self._computed() is not None
 
     @property

tests/test_ui_metadata.py

@@ -84,3 +84,16 @@ def test_select_hides_internal_user_ids() -> None:
     # The plain (non-duplicate) option never embeds the stable user id.
     assert 'return f"{name} ({user.user_id[-6:]})"' in select
     assert 'return name' in select
+
+
+def test_sensor_availability_does_not_depend_on_ble_connection() -> None:
+    """Measurement sensors stay available with last-known data when the
+    scale disconnects; only the Connected binary sensor reports link state.
+    """
+    sensor = SENSOR.read_text(encoding="utf-8")
+    assert "coordinator.connected" not in sensor, (
+        "measurement sensors must not gate availability on BLE link state"
+    )
+    assert "Available whenever we have a (last known) measurement value." in sensor
+    binary = BINARY.read_text(encoding="utf-8")
+    assert "coordinator.connected" in binary