Relationship to official Tesla Fleet integration

[IngmarStein]

With the introduction of https://www.home-assistant.io/integrations/tesla_fleet in HA 2024.08, choosing the "right" integration has become a bit more complex. Maybe it's a good idea to document the differences between the integrations any why one might want to choose this one over the Tesla Fleet integration (streaming data from TeslaMate over MQTT comes to mind).

[alandtse]

Probably makes sense to update the wiki with info. This may mean we can deprecate this component entirely.

[meow4agreencard]

From a battery site perspective, the Tesla Fleet integration doesn't have any way to control the site. Your integration allows to set settings like the operation mode etc.

[dannymorson]

With the introduction of https://www.home-assistant.io/integrations/tesla_fleet in HA 2024.08, choosing the "right" integration has become a bit more complex. Maybe it's a good idea to document the differences between the integrations any why one might want to choose this one over the Tesla Fleet integration (streaming data from teslaquery over MQTT comes to mind).

i don't understand it.

[jason-curtis]

It looks like the tesla_fleet integration is currently limited to sensors only (no controls), but updates are incoming to add switches, locks, etc.

Maintainer @Bre77 might have thoughts on whether tesla_fleet hopes to replace this.

[Bre77]

It looks like the tesla_fleet integration is currently limited to sensors only (no controls)

All platforms (controls) except update are in 2024.10 which has a beta available now. It still doesn't support command signing.

[jason-curtis]

Awesome, thanks for the info (and the work)!
A couple of outsider questions that it would be helpful to answer in the docs:

What does command signing enable exactly? Will controls not work on vehicles requiring the fleet API?

And is there a difference between this integration and tesla_fleet when it comes to rate limiting? Or would the rate limits be the same for a user using their own Tesla developer keys vs. the shared application that you've set up.

[Bre77]

What does command signing enable exactly? Will controls not work on vehicles requiring the fleet API?

This is difficult to answer because it's different for different vehicles and is even changing for some older vehicles. Almost all commands require signing if the vehicle was manufactured in 2024.

And is there a difference between this integration and tesla_fleet when it comes to rate limiting? Or would the rate limits be the same for a user using their own Tesla developer keys vs. the shared application that you've set up.

I believe the Owner API (this integration) has no rate limit or is very loose. The Fleet API discovery tier has very strict rate limits, which tesla_fleet will always have with its built in credential. Teslemetry and Tessie have much higher rate limits because they will pay Tesla for higher limits. If you also pay Tesla for higher limits directly in your own application registration, you will have higher limits.

Tesla has not made any of the information about the higher limit publicly available and those who have seen it signed an NDA. I am not one of those people unfortunately.

[jason-curtis]

OK so, as a summary, is this about right?

	Tesla Fleet Integration	Tesla Custom Integration (basic install)	Tesla Custom Integration (full install with fleet API)	Tesla Custom Integration (basic install + TeslaMate + MQTT)	Teslemetry
URL	link	link	link	link	link
Rate Limit (daily)	200 req/50cmds	200 req/50cmds	200 req/50cmds	50cmds	"More" than others
Sensors (all vehicles)	✅	✅	✅	✅	✅
Controls (old vehicles)	✅	✅	✅	✅	✅
Controls (new vehicles)	🚫	🚫	✅	🚫	✅
Annual Pricing (1 vehicle)	Free	Free	Free	Free	~$55 USD (varies with tax)
High-frequency updates	🚫	🚫	🚫	✅	?
Setup	👌Easy	👌Easy	😰Complex (instructions)	😰Complex	👌Easy

[Bre77]

I think that's pretty much correct.

Regarding High-frequency, Teslemetry and Tessie both have Fleet Telemetry which gives you limited realtime data. Its not as high frequency as the unsupported endpoint that TeslaMate uses. Neither are in Home Assistant core at this moment but it is in the Teslemetry HACS integration and I plan to add it to core soon.

Teslemetry doesnt currently charge the $30 vehicle charge, but $55 is right for the future of 1 vehicle (with 2 vehicles being $85).

From what I have been told, the rate limit for Teslemetry in the future will be approximately 2.5x the free tiers.

[segdy]

@Bre77 I asked this somewhere else already but still confused. Are these statements correct?

• Previously sending commands worked over Owner API but not any more. But reading is still possible via Owner API
• TeslaMate uses Owner API
• Commands only work via Fleet API
• Fleet API either requires your Tesla Fleet Integration or this integration+tesla proxy addon
• New cars (usually >2023) need "command signing" in addition to using the Fleet API.
• The Tesla Proxy Addon does command signing

Also, meanwhile your Fleet integration supports command signing as well, is that right? In other words, except for "high frequency updates", both should be identical functionality now?

@jason-curtis Could you add a column "Tesla Custom Integration (full install with fleet API + TeslaMate + MQTT)"? I think this would be the most powerful option, right?

[Bre77]

@segdy

Previously sending commands worked over Owner API but not any more. But reading is still possible via Owner API.

I haven't used it since 2023. Unsigned commands probably still work.

TeslaMate uses Owner API

Cool, I expect it will stop working at some point, I have no concrete information other than Tesla telling us not to use it.

Commands only work via Fleet API

Signed commands only work via Fleet API, Owner API probably still works for unsigned.

Fleet API either requires your Tesla Fleet Integration or this integration+tesla proxy addon

Or you can use a third party like Tessie or Teslemetry which are way better but cost you money instead of time.

New cars (usually >2023) need "command signing" in addition to using the Fleet API.

They need to use command signing with the Fleet API or else commands dont work.

The Tesla Proxy Addon does command signing

Yes, I believe it runs the Tesla vehicle command proxy. Tesla Fleet integration has this implemented in python.

both should be identical functionality now

I doubt it, I am sure there are some small differences. For the most part they should be the same. In the future Tesla Fleet might support more things that are Fleet API signed only, but no promises, as I am adding this to Teslemetry first.

To update my comment from October, Teslemetry now has as low as 1 second data intervals for streaming data, so we are probably pretty close to that unsupported endpoint TeslaMate uses.