The remote server returned an error: (400) Bad Request. (The remote server returned an error: (400) Bad Request.)

[phuongpham]

Hi
Seems like Tesla have change the authentication for Tesla API.
This is already been discussed here:

https://tesla-api.timdorr.com/api-basics/authentication#get-https-auth-tesla-com-oauth-2-v-3-authorize
Tesla has deprecated the /oauth/token endpoint in favor of using auth.tesla.com

[JonnMsft]

Thanks Phuong! I admit I haven't been maintaining this project, mostly because it didn't seem to generate much interest. I could try to update it but it would probably be a while before I get to that. If you or someone else want to propose changes via pull request, I could review and incorporate these into the project, and maybe republish to PowerShell Gallery.

[phuongpham]

Thanks Phuong! I admit I haven't been maintaining this project, mostly because it didn't seem to generate much interest. I could try to update it but it would probably be a while before I get to that. If you or someone else want to propose changes via pull request, I could review and incorporate these into the project, and maybe republish to PowerShell Gallery.

Hi @JonnMsft.
I have tried to look into this. But it seems like it very complicated to rewrite the connect function.
It required multiple invoke-RestMethod to establish the connection and to get the token.
It also seems it has been changed the way to refresh the access token.
I have tried to look at have this has been implemented with ruby here: https://github.com/timdorr/tesla-api/blob/master/lib/tesla_api/client.rb
Maybe someone with better knowledge on powershell can help us to implement this in powershell?