Manual / Getting started
Which cars work
BavarianData has no model list and no model-specific code. It works with whatever BMW CarData delivers for your car, so the question is really whether your car has CarData, and how much it sends.
The quick check
Open your car in the BMW or MINI portal (My Vehicles → Vehicle overview, see step 1). If there is a BMW CarData or Mini CarData tile, BavarianData works with that car.
The one exception is BMW Motorrad: motorcycles are listed in CarData, but BMW streams no data for them (more).
What you get, by drivetrain
The integration works out the drivetrain from what the car reports and adapts the dashboard card and the derived sensors to it.
| Drivetrain | What works |
|---|---|
| Electric | Everything: live state of charge and range, charging history and cost, battery health, efficiency and real range, the evcc bridge, trips. |
| Plug-in hybrid | All of the above except consumption, real range and charging cost per 100 km, which the odometer can’t support on a car that also drives on fuel (why); BMW’s own lifetime consumption figures take their place where the car sends them. Adds tank level, combined range and the Fuel view. |
| Petrol / diesel | Tank level, range, odometer, doors, windows and locks, tire pressure, service and Check Control messages, location and trips, and the Fuel view: refuels and consumption read off the tank. |
Cars owners have confirmed
These are the models people have reported running, in issues and discussions. Any car with CarData should work; this list is only what has been seen.
| Car | Drivetrain | Worth knowing |
|---|---|---|
| BMW i5 eDrive40 | Electric | The maintainer’s car. Every feature is developed and tested on it. |
| BMW i4 M60 xDrive, i4 eDrive35 | Electric | Versions before 0.9.15 could mistake an i4 for a hybrid (#53). |
| BMW iX3 (new generation) | Electric | BMW streams a repeating 100 % charge target on top of the real setting (#52). |
| BMW i3s 120 Ah | Electric | — |
| BMW X3 30e xDrive | Plug-in hybrid | Doesn’t stream the state of charge; it arrives with the daily REST refresh. |
| BMW X3 M40d (G01) | Diesel | — |
| BMW M240i xDrive (G42) | Petrol | Tire pressure drifted after restarts before 0.9.7 (#7). |
| BMW 530d Touring (G31, iDrive 6) | Diesel | Sends mileage, fuel and position only when a trip ends. Set Trip detection to End-of-trip reports for a trip journal (since 0.9.17; more). No tire diagnosis: BMW doesn’t offer it on iDrive 6 (#174). |
| MINI (petrol), incl. Countryman JCW (U25) | Petrol | Set up through the MINI portal. Sends fewer fields than a BMW: no lifetime fuel-consumption counters, and the cars seen so far send no tank level either (#23, #100). Ticking it in Data Selection doesn’t change that. |
| MINI Cooper SE (F56) | Electric | Set up through the MINI portal. Sleeps while charging: it sends the state of charge only when a charge starts and again when it ends. Before 0.9.22 that recorded each charge at about 2 % of the pack; it is now recorded in full (#180). The one seen so far sent no tire pressure, although its sensors are fitted. |
What differs from car to car
- Which fields arrive. BMW’s catalogue has hundreds of descriptors,
and no car sends them all. Run
get_coverage_reportto see which of the ones you selected your car actually delivers, and why a listed field may never arrive. - How often. Some cars send a value only when it changes, others repeat everything every half minute while awake. A parked car can be quiet for hours; that is normal.
- During a drive. Most cars stream position and mileage while driving, which is what the trip journal is built from. Some older ones only report at the end.
Your car isn’t listed?
It almost certainly works anyway. Once it runs, say so in Discussions with the model and drivetrain, so the next owner of that car finds it here. If something looks wrong, open an issue and attach a diagnostics download: it shows what your car sends.