"Hosting a Public/Private Key Pair" instructions are unclear.

[klaw81]

Feedback

Step 1 says "Open a new terminal on your computer" - On which computer? On which OS? I don't know if it matters, but it certainly isn't recognised by a command prompt in Windows.

Sorry if that's an unrealistic expectation, but the instructions don't give details.

URL

https://www.home-assistant.io/integrations/tesla_fleet/

Version

2025.1.4

Additional information

No response

[home-assistant]

Hey there @Bre77, mind taking a look at this feedback as it has been labeled with an integration (tesla_fleet) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tesla_fleet can trigger bot actions by commenting:

• @home-assistant close Closes the feedback.
• @home-assistant rename Awesome new title Renames the feedback.
• @home-assistant reopen Reopen the feedback.
• @home-assistant unassign tesla_fleet Removes the current integration label and assignees on the feedback, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

[dtpazz]

It is a generic statement on purpose.

If you only have access to a Windows OS, command prompt will work but you will need to install OpenSSL. Alternatively install Git for Windows which includes OpenSSL already.

[BarBaar44]

Agree instructions are limited and require a fair bit of background knowledge. Adding to the above:

1. You need to create a public/private key pair. However, it's unclear what the private key is used for. The integration creates a private key, but that cannot be used as it doesn't match the public key just created.
2. Instructions for Command Signing are very limited. As I own a MX, I apparently need to use this. Tesla documentation is limited. I currently cannot get it to work. Tesla doesn't see my domain as a registered third party. This may be a result of failure in 1. But I do not know, and do not know how to check.

[Bre77]

I am considering having the integration also write its public key to disk to make it easier for people to just use those without having to worry about openssl at all. I am also considering doing the Fleet API registration for people. This should simply the documentation steps required.

[thejoker82]

I used the private key generated by the integration, from the file "tesla_fleet.key file". I uploaded the public key to AWS S3, but I get the error "Command failed: Vehicle did not recognize the key used to authorize command. Make sure your key is paired with the vehicle"