BavarianData — User Manual
Connect Home Assistant directly to BMW CarData: a live MQTT stream plus a REST API, using your own personal BMW client ID. No third-party cloud in between, no MyBMW screen-scraping — Home Assistant is the only client. Read-only: CarData can show you everything, but cannot command the car.
This wiki is the full manual. For a one-page overview and install-at-a-glance, see the README.
Start here#
Used the old BMW Connected Drive integration? Read Coming from bimmer_connected first.
New install? Follow the five steps in order:
- BMW portal setup — client ID + scopes
- Install via HACS
- Add & authorize the integration
- Choose which data to stream — the cluster picker
- Add the card to a dashboard — nothing appears in the sidebar on its own
The dashboard card#
BavarianData ships a Lovelace card whose resource is registered automatically; you add the card to a dashboard yourself. It has several views:
Features#
- Entities & devices — what appears, and how it’s named
- Charging history & cost
- Battery health — how usable capacity is learned
- Efficiency & real range — measured consumption, and how far it reaches
- Trips / driving journal — and the Fahrtenbuch caveat
- evcc & wallbox bridge — hand your state of charge to a charge controller, at no API cost
- Energy dashboard & long-term statistics
- Export (CSV / HTML report)
- Events & automation blueprints
- API quota — the 50 requests / 24 h cap
- Multiple cars & accounts — one entry per account, and how to say which car you mean
Reference#
- Settings reference — every Configure screen
- Services reference — every service call
- Troubleshooting & FAQ
- Deep reference — descriptor/field catalogue
Status — actively developed. A spare-time project, verified against a limited number of vehicles and Home Assistant versions, so expect the odd rough edge on a model it hasn’t met yet. It is read-only by design — CarData cannot command the car — so treat what it reports as informational rather than as the trigger for a safety-critical automation.