Feature Trips

Trips / driving journal

Every drive is reconstructed from the stream and kept: distance, duration, start/end places, SoC used, and BMW's own per-trip consumption, recuperation and driving-style figures. No REST quota.

Not a tax-office-compliant logbook (kein Finanzamt-konformes Fahrtenbuch). This is a trip journal and expense helper; it has no legal tamper-resistance.

How trips are detected

Trips are reconstructed from live GPS in the stream (the integration tracks distance along the GPS track), so no configuration is needed. Make sure the Electric vehicle and location descriptors are enabled in step 4.

Privacy by default

Endpoints are stored as place names, never coordinates:

• A point inside a Home Assistant zone shows that zone's name.
• A point outside any zone is stored as an address only if you enable reverse geocoding under Configure → Trips (trip_geocode). That sends the endpoint coordinates to OpenStreetMap's Nominatim; the resulting address string is stored, and the coordinates themselves are never persisted.

Classification

Drives auto-classify as business, private or commute:

• Set a work zone under Configure → Trips (trip_work_zone) so home↔work drives are recognised as commutes.
• Correct any guess with bavariandata.set_trip_class or the tap-to-edit control on the trips card.

The monthly sensor and summaries

• One Driving Distance (This Month) sensor per vehicle carries the monthly total and the business/private/commute split.
• The detail lives in the services (and the card), not a flood of entities:
  • bavariandata.get_trips — recorded trips as response data.
  • bavariandata.get_driving_summary — the "month in review": distance (vs last month), the split, consumption, recuperation, a driving-style score, top destinations, and (with a tariff) an estimated driving cost.

Viewing & exporting

• The view: trips card.
• Export to CSV or a printable report.