Tesla Fleet - Key pairing issue

[fluid sparrow]

I have been setting up a clean Tesla Fleet integration as per documentation.
My public key is hosted on a local webserver behind a Nginx Proxy Manager where I copied the file in /.well-known/appspecific/com.tesla.3p.public-key.pem and https://subdomain.mydomain.ext is accessible from outside world (just a plain index.html page in the folder)
Setup worked fine, my two cars are in the home assistant and sensors are correctly updated.

But sending commands doesn't work despite a succesful installation of the keys through https://tesla.com/_ak/subdomain.mydomain.ext on my Android app. (notification of key addition received, key on subdomain.mydomain.ext is displayed among the keys in vehicle).

I get two error messages:

• Command failed: Vehicle did not recognize the key used to authorize command. Make sure your key is paired with the vehicle after restarting home assistant
• Failure of button/press action. 'Session' object has no attribute 'epoch' when I try again afterwards.

Anyone has any idea of what I am doing wrong?

[fluid pumice]

I have the same issue, not sure what to do no

i see the public key "key" in my tesla when i goto locks/keys

[sinful crane]

I am also experiencing this. I was super stoked to get the integration working again at all so I could see attributes about our vehicles again. That said I am also bummed because I thought it was going to be able to replace MyQ completely. Unfortunately I can't find a way to build an automation that triggers fast enough for my liking.

I was in the car with the HomeAssistant browser pulled up to see what commands it would respond to, and almost everything I was willing to try gave me the Command Failed: ... errors