[APP][PRO] Tesla - Zero emissions. Zero compromises

Apps
,
854

hi @RonnyW I was getting alot of pings (180+) on location after addign the car and tried removing it from homey and the cars virtual profile/key. But when re-adding the car I only get an error.
My idea was to re-add the car but without location sharing as I don’t really need it for my flow. :slight_smile:

I’ve compiled a diagnostic report below to share if that helps.
cf4a970d-046f-49df-bfa2-c6145ef848c5

Thanx for a great app! Kudos

855

Location requests are done if a location device is added.
Without a location device in Homey, the data request doesn’t request location details.
But it can be that Tesla changed something…

And location data is only transferred on data requests. That’s independent of adding a car key (only needed for commands).

Your report:

  • error is, that you try to use the (Homey)domain for another client_id. That’s not possible if the domain was/is registered for an app at Tesla.
    Use your ‘old’ client_id.
    Clear your browser cache and repair your car device (or remove/add). Then the oAuth popup should be shown again and you can deselect location scope.
    If the oAuth popup is not shown, the browser has still a cookie active with your login session. Clear cookies for tesla.com and pair/repair again.
1 Like
856

It is already activated… that’s why I’m curious if he could either fix it or add it…

857

Do you get an error message in your flow/device?

858

Am getting the error: REST command commandTrunk not supported yet for direct CommandProtocol

859

Ah, then it’s not implemented yet for commandAPI
I will check it soon and give you a feedback.

860

As addition: Location reading can be configured on several places:

  • Tesla dev account: remove scope in your app definition
    You won’t be able to set this scope in pair view
  • Pairing (auth popup): don’t set scope for location
    You can remove app permissions here. But the app doesn’t check scopes. If something is not allowed (commands), the flow actions will error.
  • Remove or don’t add location device. Location details are read if a location device is added. The other way around you will need location permission for location device to get data.
861

Thanks!

862

I managed to brick the Tesla app on my homey :expressionless_face:

I had created a new developers account (on a different email address), instead of logging in with my existing Tesla account. After realizing my mistake, I deleted the wrong account and tried again with the correct account. However, it seems that my old account is still stored somewhere within the app.

After the step where I enter my (correct) Client ID and Secret I should go to the login page. However I get an error.

422 Unprocessable Entity: {"response":null,"error":"Validation failed: Domain has already been taken","error_description":"","txid":"9fa2dfdb217a73dd9a02c1d3bd25cc27"}
  • Tried again several times
  • App reinstalled
  • Homey restarted
  • Version 12.3.1, Model Early 2019)
863

If you add a client_id from your Tesla account i to the pair view, the public key and your domain (Homey specific URL) is bound to the Tesla app.
If this registration is done, it’s fixed. You can’t remove the binding of your URL and your app id. I think, also Tesla can’t do it. They also suggest to create a new app id in this case :grinning_face_with_smiling_eyes:

So better use your app id you added first (the other account).
It doesn’t make a difference.
You only have to clear browser cookies for tesla.com if you logged in first with your developer account to get a new login popup to login with your car account.

1 Like
864

New test version 2.3.0:

  • Added security commands: lock/unlock doors, open/close trunk, open front trunk.

Hint: The old flow card “actuate trunk” is deprecated now. If you are using Command-API, please remove and use the new one where you can now select open/close trunk. The front trunk has an own flow card now to open it.

@Mads_Kvols_Hansen FYI and test :slight_smile:

865

Hmm I can’t see a flow card for open/close the frunk. Only the trunk?

866

There is a card to open/close the trunk.
And a second one to open the front trunk.

The message itself allows to open and close, but the car only opens (or does a MX/MS also close the frunk?)

867

IMG_7885
IMG_78851320×2868 323 KB

There’s this one. But it doesn’t say trunk. It says open trunk (in danish). Maybe it’s wrong and meant to be frunk instead of trunk?

868

Yes, it’s KI translation :slight_smile:
Another try says: Åbn frontbagagerummet
Is that a better translation?

869

I will test it when I come home later and give you feedback! :smiling_face:

870

Tested it and works perfectly!

1 Like
871

Hi @RonnyW

I’ve did some testing and the missing commands are now in place and working.

Maybe the vikings in here would like to provide correct translations - let us know.

I agree with @Mads_Kvols_Hansen , the frunk/trunk is mixed up.
I guess a qualified name could be: “Åbn frontbagagerummet”

I’ve just googled and the ones that is in doubt, used the phrase: frunk :smiley:

1 Like
872

Yeah, the translation was not correct for the new trunk card. I hope it’s ok now with
new test version 2.3.1 :slight_smile:

And even Tesla uses “Front Trunk” instead of “Frunk”, which is just colloquial.

873

We are now 12 days in, and I’m already getting the “Tesla API limit exceeded” alert. How can I change this? I don’t understand any of this. I only use this app to open my garage door and turn on my air conditioning, so it doesn’t need to constantly request data