Tibber

← Vehicles

Reads vehicle data (state of charge, range) via the official Tibber Data API. Requires an OAuth2 client (client id and secret) created at https://data-api.tibber.com/clients/manage. Register the redirect URI shown below when creating the client. A Tibber energy contract is not required, the vehicle must be connected in the Tibber account.

Parameters

Name	Description	Level
`clientid`	Client ID	optional
`clientsecret`	Client Secret	optional
`redirecturi`	Redirect URI Redirect URI of the evcc instance. Must match the redirect URI set in the Tibber Data API client. Example: `https://evcc.example.org/providerauth/callback`	optional
`title`	Title Will be displayed in the user interface	optional
`capacity` [kWh]	Battery capacity Example: `50`	optional
`vin`	Vehicle Identification Number Optional, selects the vehicle when the account has more than one. Example: `WVW...`	optional
`icon`	Icon Will be displayed in the user interface Default: `car`	advanced
`phases`	Maximum number of phases Used to determine the minimum solar surplus and plan duration.	advanced
`mode`	Default charging mode Applied when a vehicle is connected. Leave empty to keep the current mode.	advanced
`minCurrent` [A]	Minimum current The minimum current per connected phase that can be used Example: `6`	advanced
`maxCurrent` [A]	Maximum current The maximum current per connected phase that can be used Example: `16`	advanced
`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. Example: `10000`	advanced
`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.	advanced
`priority`	Priority Priority of the loadpoint or vehicle in relation to other loadpoints or vehicles for allocating surplus energy (higher values, higher priority).	advanced
`cache`	Cache Time interval for data refresh Default: `15m` Example: `5m`	advanced

Configuration example for evcc.yaml

If you don't want to configure via the UI, you can alternatively use this YAML block.

vehicles:
    - name: my_car
      type: template
      template: tibber
      clientid: # Client ID
      clientsecret: # Client Secret
      redirecturi: https://evcc.example.org/providerauth/callback # Redirect URI, Redirect URI of the evcc instance. Must match the redirect URI set in the Tibber Data API client.
      title: # Title, Will be displayed in the user interface (optional)
      capacity: 50 # Battery capacity (kWh), optional
      vin: WVW... # Vehicle Identification Number, Optional, selects the vehicle when the account has more than one. (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)
      mode: # Default charging mode, Applied when a vehicle is connected. Leave empty to keep the current mode. (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)
      cache: 15m # Cache, Time interval for data refresh (optional)

View nightly version