Mini CarData

← Køretøjer

Requires CarData activation in BMW/Mini portal. The following data points need to be configured for streaming access (the availability of data points may vary depending on the vehicle model):

vehicle.body.chargingPort.status
vehicle.cabin.infotainment.navigation.currentLocation.latitude
vehicle.cabin.infotainment.navigation.currentLocation.longitude
vehicle.cabin.hvac.preconditioning.status.comfortState
vehicle.drivetrain.batteryManagement.header
vehicle.drivetrain.electricEngine.charging.hvStatus
vehicle.drivetrain.electricEngine.charging.status
vehicle.drivetrain.electricEngine.charging.timeRemaining
vehicle.drivetrain.electricEngine.kombiRemainingElectricRange
vehicle.drivetrain.lastRemainingRange
vehicle.powertrain.electric.battery.stateOfCharge.target
vehicle.powertrain.electric.battery.stateOfCharge.displayed
vehicle.vehicle.preConditioning.activity
vehicle.vehicle.travelledDistance

Data will be updated on restart and when received using streaming. This only happens when the vehicle actively creates new updates.

In case the vehicle detection does not work reliably, welcomecharge (charge on connection) should be enabled.

BMW allows only one streaming connection per account. If another tool already uses it, the streaming data can optionally be read from a local MQTT broker. The tool must publish the unmodified CarData messages, e.g. bmw-mqtt-bridge with its default settings. Only this tool should be allowed to publish to the topic, e.g. using broker ACLs. Login with clientid is still required for REST requests.

Parametre

Navn	Beskrivelse	Niveau
`vin`	Vehicle Identification Number If you own multiple vehicles from the same manufacturer Eksempel: `WBMW...`	valgfri
`clientid`	Client ID	valgfri
`title`	Title Will be displayed in the user interface	valgfri
`capacity` [kWh]	Battery capacity Eksempel: `50`	valgfri
`icon`	Icon Will be displayed in the user interface Standard: `car`	avanceret
`phases`	Maximum number of phases Used to determine the minimum solar surplus and plan duration.	avanceret
`minCurrent` [A]	Minimum current The minimum current per connected phase that can be used Eksempel: `6`	avanceret
`maxCurrent` [A]	Maximum current The maximum current per connected phase that can be used Eksempel: `16`	avanceret
`maxPower` [W]	Maximum charging power hint Defines the maximum charging power of the vehicle. Helps improve charge plan accuracy when the vehicle typically uses less than the offered current or supports higher single-phase current compared to three-phase. The offered current of the loadpoint is not affected. Eksempel: `10000`	avanceret
`identifiers`	RFID identification Used to assign the vehicle to a loadpoint via RFID card. The identifier is shown on the loadpoint. Copy the value from there. Learn more.	avanceret
`priority`	Priority Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating surplus energy (higher values, higher priority).	avanceret
`coarsecurrent`	1A current control Vehicle supports 1A current steps only	avanceret
`streaming`	Supports streaming Enable if vehicle sends streaming updates during charging.	avanceret
`welcomecharge`	Charge on connection Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting.	avanceret
`climaterdisabled`	Disable climater detection Ignore the vehicle's climater state for charge control, so charging stops at the SoC or energy limit even when the vehicle signals an active climater request.	avanceret
`autodetectdisabled`	Exclude from auto detection Ignore the vehicle for auto detection of connected vehicles	avanceret
`wakeupdisabled`	Disable wake-up calls Do not send wake-up calls to the vehicle or charger, useful for vehicles that refuse to charge after repeated wake-ups.	avanceret
`broker`	MQTT broker Read the streaming data from this local MQTT broker instead of BMW. Leave empty to connect to BMW directly. Eksempel: `192.168.1.10:1883`	avanceret
`user`	Username MQTT broker username	avanceret
`password`	Password MQTT broker password	avanceret
`topic`	Topic Topic on the MQTT broker carrying the unmodified CarData messages Standard: `bmw/raw/+`	avanceret
`cache`	Cache Time interval for REST data refresh. Default 15m, 30m with streaming. BMW allows 50 requests per day per account, raise it if other tools also use REST requests on the same account. Eksempel: `30m`	avanceret

Konfigurationseksempel til evcc.yaml

Hvis du ikke vil konfigurere via webgrænsefladen, kan du i stedet bruge denne YAML-blok.

vehicles:
    - name: my_car
      type: template
      template: cardata
      vin: WBMW... # Vehicle Identification Number, If you own multiple vehicles from the same manufacturer
      clientid: # Client ID
      title: # Title, Will be displayed in the user interface (optional)
      capacity: 50 # Battery capacity (kWh), optional
      icon: car # Icon, Will be displayed in the user interface [car, bike, bus, moped, motorcycle, rocket, scooter, taxi, tractor, rickshaw, shuttle, van, airpurifier, battery, bulb, climate, coffeemaker, compute, cooking, cooler, desktop, device, dishwasher, dryer, floorlamp, generic, heater, heatexchange, heatpump, kettle, laundry, laundry2, machine, meter, microwave, pump, smartconsumer, tool, waterheater] (optional)
      phases: # Maximum number of phases, Used to determine the minimum solar surplus and plan duration. [1, 2, 3] (optional)
      minCurrent: 6 # Minimum current (A), The minimum current per connected phase that can be used (optional)
      maxCurrent: 16 # Maximum current (A), The maximum current per connected phase that can be used (optional)
      maxPower: 10000 # Maximum charging power hint (W), Defines the maximum charging power of the vehicle. Helps improve charge plan accuracy when the vehicle typically uses less than the offered current or supports higher single-phase current compared to three-phase. _The offered current of the loadpoint is not affected._ (optional)
      identifiers: # RFID identification, Used to assign the vehicle to a loadpoint via RFID card. The identifier is shown on the loadpoint. Copy the value from there. [Learn more.](https://docs.evcc.io/en/docs/features/vehicle) (optional)
      priority: # Priority, Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating surplus energy (higher values, higher priority). (optional)
      coarsecurrent: # 1A current control, Vehicle supports 1A current steps only (optional)
      streaming: # Supports streaming, Enable if vehicle sends streaming updates during charging. (optional)
      welcomecharge: # Charge on connection, Charger will enable charging for short time when vehicle is connected, irrespective of configured charge mode. This is useful for vehicles that require power supply when connecting. (optional)
      climaterdisabled: # Disable climater detection, Ignore the vehicle's climater state for charge control, so charging stops at the SoC or energy limit even when the vehicle signals an active climater request. (optional)
      autodetectdisabled: # Exclude from auto detection, Ignore the vehicle for auto detection of connected vehicles (optional)
      wakeupdisabled: # Disable wake-up calls, Do not send wake-up calls to the vehicle or charger, useful for vehicles that refuse to charge after repeated wake-ups. (optional)
      broker: 192.168.1.10:1883 # MQTT broker, Read the streaming data from this local MQTT broker instead of BMW. Leave empty to connect to BMW directly. (optional)
      user: # Username, MQTT broker username (optional)
      password: # Password, MQTT broker password (optional)
      topic: bmw/raw/+ # Topic, Topic on the MQTT broker carrying the unmodified CarData messages (optional)
      cache: 30m # Cache, Time interval for REST data refresh. Default 15m, 30m with streaming. BMW allows 50 requests per day per account, raise it if other tools also use REST requests on the same account. (optional)