Teslemetry

The Teslemetry integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] exposes various commands and sensors from the Tesla vehicles and energy sites connected to a Teslemetry subscription.

Prerequisites

You must have a Teslemetry account with active subscription.

The virtual key is Teslemetry’s public key, installed in your vehicle through the Tesla app. It is required for fleet telemetry (live streaming) and signed vehicle commands. Since nearly all vehicles support both, nearly all customers need it: if your vehicle supports the virtual key, install it as a standard setup step. Vehicles without virtual-key support are the exception. They still work with Teslemetry at reduced capability—data by polling instead of streaming, and commands unsigned where Tesla permits.

Configuration

To add the Teslemetry hub to your Home Assistant instance, use this My button:

Entities

These are the entities available in the Teslemetry integration. Not all entities are enabled by default, and not all values are always available. Entities in the device tracker platform specifically require the Vehicle location scope, and will appear unavailable otherwise.

Vehicles

Energy sites

Wall connector

Metadata

List of actions

The Teslemetry integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] provides the following actions. Each link below opens a dedicated page with examples, parameters, and a step-by-step UI walkthrough.

• Add charge schedule (teslemetry.add_charge_schedule) Adds or modifies a charging schedule for the vehicle.

• Add precondition schedule (teslemetry.add_precondition_schedule) Adds or modifies a preconditioning schedule for the vehicle.

• Navigate to coordinates (teslemetry.navigation_gps_request) Sets the vehicle’s navigation to a specific latitude and longitude.

• Remove charge schedule (teslemetry.remove_charge_schedule) Removes a charging schedule from the vehicle.

• Remove precondition schedule (teslemetry.remove_precondition_schedule) Removes a preconditioning schedule from the vehicle.

• Set scheduled charging (teslemetry.set_scheduled_charging) Sets a time at which the vehicle should start charging.

• Set scheduled departure (teslemetry.set_scheduled_departure) Sets a departure time so the vehicle schedules charging and preconditioning.

• Set speed limit (teslemetry.speed_limit) Turns the vehicle’s speed limit on or off.

• Time of use settings (teslemetry.time_of_use) Updates the time of use settings for a Tesla energy site.

• Set valet mode (teslemetry.valet_mode) Turns valet mode on or off for the vehicle.

For an overview of every action across all integrations, see the actions reference.

Energy dashboard

The Tesla Fleet API only provides power data for Powerwall and Solar products. This means they cannot be used on the energy dashboard directly.

Energy flows can be calculated from Battery power and Grid power sensors using a Template Sensor to separate the positive and negative values into positive import and export values. The Load power, Solar power, and the templated sensors can then use a Riemann Sum to convert their instant power (kW) values into cumulative energy values (kWh), which then can be used within the energy dashboard.

Data updates

Teslemetry delivers data by streaming or polling, depending on the product. The Data column in the entity tables above shows how each entity is updated:

• Streaming: the value arrives over the live stream in real time.
• Polling: the value comes from Teslemetry’s cached vehicle data.
• Both: the value can arrive by streaming or polling, depending on the vehicle and its configuration.
• — (em dash): the entity does not report data. Buttons send commands, so they have no data source.

Vehicle data

Most vehicles stream their data to Home Assistant in real time over Server-Sent Events (SSE), with no per-update cost. The integration sets up and manages this streaming configuration for you.

Pre-2021 Model S and Model X vehicles cannot stream. For these vehicles, Teslemetry automatically refreshes their data on its own servers at no cost to you. A non-streaming vehicle is refreshed roughly every 15 minutes, and a vehicle that Tesla marks as discounted is refreshed much more often, roughly every 90 seconds. Both are free.

Credits are only spent on an on-demand fresh full-vehicle-data fetch, which costs 2 credits, or 0.1 credit for a discounted vehicle.

On a streaming vehicle, Polling entities read from Teslemetry’s cached vehicle data instead of the live stream. Their values are not streamed and do not refresh on their own, which is why many of them are disabled by default. Enabling one is not a switch for Teslemetry’s free automatic polling, and Home Assistant never bypasses the cache or forces a refresh on its own.

If your vehicle is unpaired and streams through the safety screen, an enabled polling entity reads the cached vehicle data every 60 seconds while the vehicle is online. Most of those reads are free cache hits. Each time the cached data passes 20 minutes old, the next read becomes a charged fresh fetch at that cost, so it recurs for as long as the vehicle stays online. Streaming updates do not reset this 20-minute window.

The integration does not wake a sleeping vehicle to fetch data. Updates pause until the vehicle wakes up on its own or you interact with it.

Energy site data

Energy sites are cloud-polled: live status and site information every 30 seconds, and energy history every 60 seconds.

Known limitations

• Vehicle Sleep: The integration will not actively wake a vehicle to fetch data. However, sending commands (such as locking, unlocking, or climate control) will wake the vehicle.
• Rate Limits: While Teslemetry handles upstream rate limiting with Tesla, excessive polling or command usage from aggressive automations may encounter temporary API limits.
• Virtual Key: See Prerequisites for when a virtual key is needed. To set one up, follow the instructions on the Teslemetry Console.

Troubleshooting

Invalid tokens

If your Teslemetry authentication token becomes invalid or expires, Home Assistant will prompt you to re-authenticate. This typically involves signing in again via the integration’s configuration flow.

Timeouts

Timeouts can occur due to connection issues between Home Assistant, Teslemetry, Tesla, or the vehicle itself (e.g., the vehicle is in an area with poor cellular reception). These are often temporary. If timeouts persist, please contact support@teslemetry.com.

Examples

Common use cases

• Solar Charging: Automate your vehicle’s charging current or state based on excess solar production to maximize renewable energy usage.
• Smart Preconditioning: Use calendar events or time-based triggers to precondition your vehicle’s cabin temperature before you depart.
• Automatic Garage Door: Automatically open your garage door when you approach your home while navigating.

Automations

Automate charging based on solar production

automation:
  - alias: "Charge Tesla from Solar"
    trigger:
      - platform: numeric_state
        entity_id: sensor.home_solar_power
        above: 3000
    actions:
      - action: switch.turn_on
        target:
          entity_id: switch.my_tesla_charge
      - action: number.set_value
        target:
          entity_id: number.my_tesla_charge_current
        data:
          value: 16

Precondition vehicle before calendar events

automation:
  - alias: "Precondition for Work"
    trigger:
      - platform: calendar
        event: start
        offset: "-00:15:00"
        entity_id: calendar.work
    actions:
      - action: climate.turn_on
        target:
          entity_id: climate.my_tesla_climate

Blueprints

Open Garage Door based on Navigation

Uses the distance to arrival sensor to accurately know when you’re close to a specific location (such as your home), and open a garage door, or other cover entity. Requires you to be navigating to your intended destination, even if you don’t need the directions.

blueprint:
  name: Teslemetry Garage Door Opener
  author: Brett Adams
  description: Opens a garage door when your Tesla is approaching
  domain: automation
  input:
    distance_to_arrival_entity:
      name: Distance to arrival entity
      selector:
        entity:
          filter:
            - integration: teslemetry
              domain: sensor
              device_class: distance
    distance_to_arrival:
      name: Distance to arrival value to trigger open
      selector:
        number:
          min: 0
          max: 100
          step: any
          mode: box
    route_entity:
      name: Route entity
      selector:
        entity:
          filter:
            - integration: teslemetry
              domain: device_tracker
    route_zone:
      name: Route destination
      selector:
        entity:
          filter:
            - domain: zone
    cover_entity:
      name: Garage door entity
      selector:
        entity:
          filter:
            - domain: cover
trigger:
  - platform: numeric_state
    entity_id:
      - !input distance_to_arrival_entity
    below: !input distance_to_arrival
    above: 0
condition:
  - condition: zone
    entity_id: !input route_entity
    zone: !input route_zone
actions:
  - action: cover.open_cover
    target:
      entity_id: !input cover_entity
mode: restart