Command Credits System and Usage
Command credits are Teslemetry's pay-per-use system for vehicle commands. Since Tesla charges Teslemetry for every command sent through the Fleet API, command credits allow Teslemetry to pass these costs directly to users based on their actual usage.
Understanding Command Credits
Command Credit Costs
Action | Credit Cost | Notes |
|---|---|---|
Standard vehicle command | 1 credit | Includes lock, unlock, climate, flash lights, etc. |
Vehicle data refresh | 2 credits | Forces a server-side data refresh |
Vehicle wake up | 20 credits | Most expensive due to Tesla's pricing |
Pricing: 2000 command credits = USD $2.50 ($0.00125 per credit)
Credits Do NOT Reset Monthly
Important: Command credits do not expire and do not reset with your subscription renewal. Once purchased, they remain in your account until used or until you delete your account.
Frequently Asked Questions
Why am I getting "Account has insufficient command credits" errors?
This error occurs when you attempt to run a command but your account does not have enough credits. This can happen because:
- You have run out of credits - Check your balance at teslemetry.com/console
- Auto top-up is disabled - Enable auto top-up to automatically purchase more credits when you run low
- High automation usage - Frequent automations can consume credits quickly
Solution: Purchase additional command credits through the Teslemetry console, or enable auto top-up to prevent running out.
I thought I had a subscription - why do I need to buy credits?
Your Teslemetry subscription and vehicle/energy site subscriptions cover access to the Teslemetry service and data streaming. However, Tesla charges separately for every command sent through the Fleet API. Command credits are how Teslemetry accounts for these per-command costs.
Think of it this way:
- Subscriptions = Access to the service and data
- Command credits = Pay-per-use for sending commands to your vehicle
Do command credits reset monthly with my subscription?
No. Command credits never reset or expire. They are a separate pool of credits that you purchase and use as needed. When you run out, you need to purchase more or enable auto top-up.
Why are my command credits being consumed so quickly?
Several factors can cause rapid credit consumption:
- Solar charging automations - Adjusting charge amps based on solar production can send 150-400+ commands per day
- Frequent charge limit changes - Automations that change charge limits repeatedly
- Vehicle waking up frequently - Each wake costs 20 credits
- Third-party apps polling vehicle_data - Some apps may poll vehicle data frequently, consuming 2 credits per request
- Failed commands when vehicle is asleep - If a command is sent to a sleeping vehicle, you may be charged even if it fails
Tips to identify the cause:
- Review your command history at teslemetry.com/console/history
- Check your Home Assistant automations for frequent command calls
Tips for Reducing Credit Usage
1. Use Bluetooth for Frequent Commands
For use cases like solar charging that require frequent commands, consider using Bluetooth instead of the Fleet API. The ESPHome Tesla BLE project allows ESP32 microcontrollers to control your Tesla over Bluetooth Low Energy without consuming command credits.
2. Check Vehicle Status Before Sending Commands
Wake-up commands cost 20 credits. If your vehicle is asleep and you send a command, Teslemetry will automatically wake it first (costing 21+ credits total). To minimize wake costs:
- Use the vehicle status sensor in Home Assistant to check if the vehicle is awake before sending commands
- Group commands together when the vehicle is already awake
3. Use Fleet Telemetry for Data
Fleet Telemetry provides real-time streaming data included in your vehicle subscription without consuming credits. Use this for monitoring rather than polling vehicle_data.
Related Resources
- Teslemetry Console - Manage credits and view usage
- Command History - View detailed command usage
- Bluetooth Control Documentation - Alternative for frequent commands
Updated on: 01/02/2026
Thank you!