Tesla Fleet Integration - Key pairing issue?

Configuration
22

For me it was the same as @grant.reid and @sumya – go into the Home Assistant configuration folder and check that the tesla_fleet.key matches the original private key that was generated. If it does not, update the key in the configuration folder and then reload the Tesla Fleet integration. Everything worked after that.

2 Likes
23

Had the same issue. Using MyTeslaMate App.
My problem was solved by: renaming key from tesla-fleet.key to tesla_fleet.key.
The integration does this by itself, but didnt fix the issue, even by deleting the wrong named key and reloading integration. By uploading the renamed key, without having the integration renaming it, it fixed everything!

1 Like
24

Thanks for the hints and tips here, I was able to get the first error solved.

However, I’m still facing the following one:

'Session' object has no attribute 'epoch'

any idea how to get it fixed? I’m running 2025.3.2

25

Registered in this forum just to thank you. Finally it’s working!

26

This resolved my problems. For some reason, home-assistant copied another tesla_fleet.key file into the root folder, which did NOT match the file in the config folder. After removing this file, everything worked fine.

27

Livid! I had placed my private key tesla_fleet.key in homeassistant/config folder as instructed.

Upon starting or reloading the Tesla fleet integration, I found out it ‘copies’ this file to homeassistant/tesla_fleet.key but completely makes up another key (does it convert it into the public one? didn’t check)! I overwrote this file to be the correct one and now its working. crazy!

Previously, I could only “fart”, I guess elon wants unsuccesful hackers to have some fun!

28

I just configured the Tesla Fleet integration and thought I defeated the final boss when both our vehicles populated in HA.

Working

  • 2020 Model X (Driver permissions) Initially commands did not work and I was missing all Sensors and Diagnostics. A restart of HA cleaned all of that up and commands now seem to work after sampling honk, climate changes, and a fart. :rofl:

Not Working

  • 2018 Model 3 (Owner permissions) When trying to honk or climate change Command failed: Vehicle did not recognize the key used to authorize command. Make sure your key is paired with the vehicle and when trying to send a fart Command failed: Access to this resource is not authorized, developers should check required Scope.

What I’ve tried

Since the Model X seems to be working well despite a more restrictive profile, it seems I’ve configured everything properly on Tesla’s side, the public key is being served as needed, and the private key is in the right place. What could I still be missing to get commands to work on my Model 3?

29

Very same issue with a Model 3. Could you solve it?

30

Unfortunately, no, it still does not work. I don’t know what to try. :man_shrugging:t3:

31

This was my issue. It overwrote the actual Private key I generated. Just moved the correct Private Key back and restarted.

32

This fixed the issue for me. Big thanks!!
Context:

  • HA: 2025.08.0
  • Tesla Model Y 2025 (Juniper)
33

Is the virtual key pairing still working? Mine keeps saying third party not authorized. HA can read the status, just cannot send command.

1 Like
34

I have the same problem, indeed.

35

I have read only, no sensor are showing values, only Unknown.

Command failed: Vehicle did not recognize the key used to authorize command. Make sure your key is paired with the vehicle

using https://fleetkey.cc/

36

This! Have been trying for days to set everything up and followed the new Tesla requirements step by step, but for some reason the HA integration kept complaining about the pubkey not being correct, although it most certainly was/is. No idea how the tesla-fleet.key (private key) ended up being wrong there, but this certainly fixed the issue!

37

Thanks for the useful info, indeed the private key has changed.
Does anybody know what sensor to use to know if the vehicle is awake?
I tried to press wake button but the status always shows disconnected, and sending command gives the error:
Command failed: The vehicle is not ‘online’.

Edit: ok some more tests show that the wake up worked in app the car is waken up however the status is still disconnected, even after:
- action: homeassistant.update_entity
data:
entity_id:
- binary_sensor.model3_status

Not sure what to do…