Enforcing the streaming allowance

Since Teslemetry launched, it has offered nearly unlimited Fleet Telemetry. Most of you stream a modest amount, but some customers consume far more than their fair share, and Teslemetry pays for every telemetry value a vehicle sends. So the goal is reasonable but flexible limits: an allowance that covers what most users need, and functionally unlimited Fleet Telemetry for power users, at a price that reflects what it costs.
That's the streaming allowance. Every vehicle plan now includes one, and Pro and Max give a vehicle more of it (and more command credits). Until now it has only been informational: the console shows how much of it you use, and nothing happens if you go over. That changes in two steps, on December 1 and January 1. The Vehicle Access allowance is enough for most users, so most of you won't notice either one.
No artificial minimum intervals
Before this change, the only way Teslemetry could control streaming costs was artificially increasing the minimum interval on costly fields. Alongside the allowance change, field minimum intervals have been lowered to the lowest values Tesla allows. Most fields now accept an interval of 1 second, and the few that don't are held only at the longer minimum the vehicle itself enforces. The allowance limits how much a vehicle streams in total, not how you spend it, so you can choose what suits your use case: a few fields every second, or many fields at longer intervals.
Free, regular, and expensive fields
Not every field costs the same, but I wanted a config's cost to be predictable upfront. So in the console, each field is categorised by how often it typically sends, because that's what Teslemetry pays for.
- Free fields only change when an infrequent event happens, like a door opening or a charge starting. They send only when their value changes, so they don't count towards your allowance at all.
- Regular fields, the ones with no label, send mostly while the vehicle is in use, so they cost a moderate amount.
- Expensive fields send constantly, even when you're not driving. A vehicle sitting idle in the garage can still use a lot of its allowance on these alone, especially at short intervals.
So if you want to stream more, go crazy with Free fields, and be careful with the interval you choose for anything Expensive.
December 1: no new streaming over your allowance
From December 1, if a config change would raise a vehicle's usage and leave it above its allowance, the change is refused. The API answers with a 402 and the error streaming_allowance_exceeded, and nothing changes on the vehicle.
Streaming that already runs keeps working. If a vehicle is over its allowance on December 1, nothing stops and no field is switched off. You just can't take it higher. You can still:
- Send the same config again
- Remove fields or lengthen intervals
- Swap to a config that uses the same amount or less
- Add Free fields, which send only when their value changes and use none of the allowance
To add any other field to a vehicle that's over its allowance, you'll need to free up the same amount first, or move the vehicle to a higher plan.
January 1: vehicles still over are reconfigured
From January 1, Teslemetry will reconfigure any vehicle still over its allowance. No field is removed. Everything you stream keeps streaming, but some fields will send less often. The changes happen in this order:
- Expensive fields are raised to their default interval.
- Regular fields are raised to their default interval.
- If the vehicle is still over, Expensive fields are raised beyond their default interval.
We stop as soon as the vehicle is back within its allowance, so a vehicle that's only slightly over may never get past the first step. Customers with a vehicle over its allowance will also hear from us by email.
If you'd rather choose which fields slow down, make the change yourself before January 1.
How to see your usage
In the console, open a vehicle and choose Telemetry Configuration. Streaming allowance used shows the percent of that vehicle's plan allowance your config uses, where 100% is the whole allowance. Above 100%, the bar turns red and the page tells you the config is above your plan's allowance.
Above 80%, a Use less of your allowance card also appears. It names the fields using the most, suggests a longer interval for each, and when you're over the allowance it tells you which plan the config would fit.
If you'd rather check from code, the same number is in streaming_allowance_percent when you read a vehicle's config:
curl 'https://api.teslemetry.com/api/config/{vin}' \
--header 'Authorization: Bearer ACCESS_TOKEN'
It's also returned after a successful POST or PATCH to the same path. It only counts your own fields, not those another customer or a connected business streams from the same vehicle.
How to get under your allowance
You have two options, and you can choose differently for each vehicle.
Lower your config. Remove the fields you don't use, or lengthen their intervals, starting with anything labelled Expensive. A field's usage scales with its interval, so doubling the interval halves what that field uses.
Move the vehicle to a higher plan. Plans are per vehicle, so only the vehicles that need it have to move. Pro gives 5x and Max gives 20x the Vehicle Access allowance, which is more than any real configuration can use, and the percent you see is always against the vehicle's current plan. A config at 300% on Vehicle Access is 60% on Pro. You can compare plans on the pricing page, and change a vehicle's plan under Modify on your subscription page.
Teslemetry for Business isn't part of this change: business config changes aren't limited by the allowance.
If you have any questions, please contact support or find me on Discord.
TLDR
- Field minimum intervals are lowered to the lowest values Tesla allows, 1 second for most fields
- Free fields don't count towards your allowance. Expensive fields send constantly, even when idle, so they cost the most.
- December 1: a config change that raises a vehicle's usage and leaves it over its allowance is refused with a
402. Streaming that already runs keeps working. - January 1: vehicles still over are reconfigured until they fit. Expensive fields go to their default interval, then regular fields, then Expensive fields go higher if needed. No field is removed.
- See your usage under Telemetry Configuration in the console, or in
streaming_allowance_percentfrom the API - To fix it, lower that vehicle's config or move it to a higher plan. See the pricing page
Force charge and force discharge your Powerwall
For the first time, Powerwall owners can tell their battery to charge or discharge on command, and Teslemetry is bringing it to Home Assistant core.
Full control of your Powerwall and Tesla, wherever you automate
Island mode, battery dispatch, Charge on Solar and every API command, local first where it can be, now across Home Assistant, Homey, Node-RED and n8n.