## [0.1.4] - 2026-02-17

### Added
- Added `battery_percent_rechargeable` sensor to provide a more realistic
  battery level estimation for rechargeable batteries (e.g. NiMH).
- The new sensor derives remaining charge from pack voltage and is intended
  for monitoring and automations when using rechargeable cells.
- Existing `battery_percent` sensor continues to reflect the vendor/device
  battery percentage logic.

### Changed
- Clarified separation between vendor-reported battery percentage and
  voltage-based rechargeable battery estimation.

Author: fwmone

CHANGELOG.md

@@ -5,6 +5,20 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/).
 
+## [0.1.4] - 2026-02-17
+
+### Added
+- Added `battery_percent_rechargeable` sensor to provide a more realistic
+  battery level estimation for rechargeable batteries (e.g. NiMH).
+- The new sensor derives remaining charge from pack voltage and is intended
+  for monitoring and automations when using rechargeable cells.
+- Existing `battery_percent` sensor continues to reflect the vendor/device
+  battery percentage logic.
+
+### Changed
+- Clarified separation between vendor-reported battery percentage and
+  voltage-based rechargeable battery estimation.
+
 ## [0.1.3] - 2026-02-15
 
 ### Changed

README.md

@@ -257,6 +257,7 @@ When device_id is configured, the following sensors are created:
 - Battery
   - sensor.paperlesspaper_push_battery_voltage (V)
   - sensor.paperlesspaper_push_battery (%)
+  - sensor.paperlesspaper_push_battery_rechargeable (%)
 
 - Timestamps
   - sensor.paperlesspaper_push_last_reachable
@@ -276,11 +277,15 @@ You can trigger an immediate telemetry refresh via the service:
 
 Battery percentage is derived from the reported raw battery voltage (`batLevel`).
 
-Default mapping (4×AAA in series):
+Default mapping (4×AAA in series) for sensor.paperlesspaper_push_battery:
 - 6.2 V → 100%
 - 4.0 V → 0%
 
-Values are clamped to the range and mapped linearly in between. So, yes, when using rechargeable NiMH batteries, the mapping is likely to show never 100%. Haven't tested it yet.
+Default mapping (4×AAA NiMH in series) for sensor.paperlesspaper_push_battery_rechargeable:
+- 5.3 V → 100%
+- 4.0 V → 0%
+
+Values are clamped to the range and mapped linearly in between. 
 
 ## Example for a Home Assistant dashboard integration
 

custom_components/paperlesspaper_push/device_sensors.py

@@ -41,6 +41,22 @@ def _battery_percent_from_mv(mv: int | None) -> Optional[int]:
 
     return round((v - V_MIN) / (V_MAX - V_MIN) * 100)
 
+def _battery_percent_nimh(mv: int | None) -> Optional[int]:
+    if mv is None:
+        return None
+
+    v = mv / 1000.0
+
+    # NiMH 4xAAA
+    V_MIN = 4.0
+    V_MAX = 5.3
+
+    if v >= V_MAX:
+        return 100
+    if v <= V_MIN:
+        return 0
+
+    return round((v - V_MIN) / (V_MAX - V_MIN) * 100)
 
 def _battery_voltage_v(mv: int | None) -> Optional[float]:
     if mv is None:
@@ -87,6 +103,13 @@ class _SensorDef:
         unit=PERCENTAGE,
         value_fn=lambda d: _battery_percent_from_mv(_get_bat_mv(d)),
     ),
+    _SensorDef(
+        key="battery_percent_rechargeable",
+        name="Battery (Rechargeable)",
+        device_class=SensorDeviceClass.BATTERY,
+        unit=PERCENTAGE,
+        value_fn=lambda d: _battery_percent_nimh(_get_bat_mv(d)),
+    ),
     _SensorDef(
         key="last_reachable",
         name="Last Reachable",

custom_components/paperlesspaper_push/manifest.json

@@ -1,7 +1,7 @@
 {
   "domain": "paperlesspaper_push",
   "name": "paperlesspaper Push",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "documentation": "https://github.com/fwmone/paperlesspaper_push",
   "issue_tracker": "https://github.com/fwmone/paperlesspaper_push/issues",  
   "requirements": [],