-
Notifications
You must be signed in to change notification settings - Fork 0
Feature Battery Health
The integration learns your EV battery's usable capacity from the same recorded charging sessions used for charging history — no REST quota, all derived from the stream.
A wide-range charge (say 20 → 80 %) that adds a known number of kWh implies the capacity of the whole pack: if 30 % of the battery took X kWh, the pack is roughly X / 0.30. Averaging across many such charges cancels the noise from temperature, charging speed and measurement error.
Surfaces as one Battery Health sensor per EV:
- State — usable capacity in kWh.
- Attributes — vs-new percentage, sample count, and a capacity-vs-mileage trend.
It reads Learning (n/10) until it has enough good samples and the
estimate agrees with BMW's own capacity figure. A suspicious number is
withheld rather than shown — a health figure that jumped around would be
worse than an honest "not sure yet."
To reach a confident number faster, do a few wide-range charges (a large SoC swing in one session) rather than many small top-ups.
Use the view: health card: a
gauge (percentage of the as-new pack) with the capacity-vs-mileage trend below.
BavarianData is an independent, community-built integration and is not affiliated with, endorsed by, or sponsored by BMW Group. "BMW", "Mini", "Rolls-Royce" and "CarData" are trademarks of their respective owners. Screenshots and documentation images of the MyBMW / BMW CarData portal are © BMW AG, shown here solely to document how to set up the service; personal data has been redacted. Released under the MIT License. · Issues · Discussions
Getting started
The card
Features
- Entities & devices
- Charging history & cost
- Battery health
- Trips
- Energy & statistics
- Export
- Events & blueprints
- API quota
Reference