Search results

Forgotten by Google unfortunately. Actions sunset announcement Given that Google is removing Conversational Actions in a few months, it doesn't make sense to put in development time to fix this right now.

Since last summer? Wow thats a long time :) So the update on this front is that I had started working on this again. Google has changed things completely in the last few months so it was practically like writing this from scratch. I did get it to work for me personally but getting it get past...

Tesla has changed the way authentication works so the old workflow doesn't work anymore. As a workaround for now try using : https://eviecar.io/auth/authorization.ws . Use the Tesla Authentication link to generate Access Token and then copy and paste that into the EV Car skill linking page. It...

Hi. Yes making some progress on it. The Tesla authentication API has changed and doesn't work transparently anymore so that's another change to deal with. In addition, I am changing the way the app is hosted as well as the backend database. I'm hoping to get it done by the early January.

I would have searched for "Tesla Token Generator" ;) This is one that has worked for me: Tesla API Token

Regular users would have figured this out already but Tesla has changed authentication mechanism so when linking, the username and password won't currently work. You have to supply an authentication token. The token can be generated using web based tools (use a google search to find your...

Also technically use the actual token not refresh token.

My day job has taken all my time in the last few months. I do plan to get this going during my extended thanksgiving break.

I just re-linked with my Model X and it is working fine. "error communicating" usually happens when the car is asleep and the app is unable to wake before Alexa's timeout. To confirm if that could be the issue, try this: use the Tesla App perform some operation on the car. Right after that use...

It is working fine on Alexa. On Google devices there is an issue - the details are on the Google specific thread: Integration with Google Home / Google Assistant - Now available for general use

So this app will come back but the features that Google wants changed will take a while to implement. Its not just about enabling the PIN but also changing the backend infrastructure to enable saving of individual account information (including PIN). I can't commit on when this will be done...

What whatever its worth, I sent off this rant to Google which was met with an expected "That's how things work" response.

Unfortunately Google took it down yesterday. First because they wanted to do a random "test" apparently didn't have a Tesla to test with :rolleyes: Then I provided a temporary token so they could test with my car and this time they rejected it because they have moved goal-posts - they now...

That sounds correct. If the Tesla App works, then this app should work too.

Hmm... Your requests might have been going to a older endpoint. If that was the case, it would be fixed now. There were some other infra issues too that are now resolved. Please try and let me know. Thanks.

There were some infra issues. It should work with generated token and/or email-password now. Thanks for pointing it out.

I went ahead and created a proxy to bounce Tesla API requests off a non-Amazon server. Authentication should work correctly now.

Looks like Tesla is again blocking all requests coming from Amazon AWS. With the intricacies of the new authentication workflow, I don't currently have a way to bounce the requests off a non-AWS server. Hopefully the limitation is short-lived. If not, I'll figure out a way to work though a proxy.

Yes, they all start the climate system. I can't edit the first page anymore but here is a FAQ page: http://eviecar.io/falcon_web.ws/faq

It wasn't just MFA. Tesla had changed the way the (undocumented) APIs used by this skill to authenticate users works. So people were not able to login at all using the skill. The change was to support the new authentication workflow. Currently you can use this skill either if MFA is disabled...

Thanks for the detailed message. Sorry I overlooked specifying that it does not yet work when MFA is enabled.

Hmm... I can't reproduce this. I unlinked and re-linked both skills - E.V.Car and My Tesla. Both went though fine. Are you still seeing this?

Authentication for this skill should work now. Tesla's new authentication mechanism has been incorporated. If anyone is still seeing issues using this skill, please post here.

Finally some good news ... In addition to Tesla's changes to the APIs, there were also some changes to Amazon AWS. All of those issue have been resolved now. You should be able to login with the app now. MFA is not yet supported so you will not be bale to use this to login with email/password...

Yes, the Authentication method that Tesla employs for the APIs has been changed. Implementing the new mechanism will take a while. I did find new documentation updated at Tim Dorr's excellent resource: Authentication however that has not worked for me yet. For now, if you have an existing token...

The Authentication method that Tesla employs has been updated. Implementing the new mechanism will take a while. I did find new documentation updated at Tim Dorr's excellent resource: Authentication however that has not worked for me yet. For now, if you have an existing token generated before...

I'm also seeing a HTTP 444 error. It might be an related to MFA authentication changes on Tesla side. I'm trying to find more information. FYI I was able to use a recently generated token to enable this app though.

I'm also seeing a HTTP 444 error. It might be an related to MFA authentication changes on Tesla side. I'm trying to find more information. FYI I was able to use a recently generated token to enable this app though.

They are valid options and should work. In fact I just retried and they work as expected. For frunk, you might to say "open front trunk" since Alexa doesn't usually get "frunk".

Please try again. It should work now.

One of the endpoints was down. It should not be related to the software update. Please try again and let me know if you still see issues.

Hi, do you have any reference to a website that explains how token handling has changed? Currently the tokens expire after 30 to 45 days. (Not 15 minutes).

I'm not sure about the first part of the question. It might have invalidated old tokens when I turned on 2FA. I just assumed the old token had expired and got new one. Asking for a new token doesn't seem to trigger 2FA though.

Tesla had again blocked requests from services such as AWS. Might be related to that.

I enable 2FA on my account and the APIs continued working as before. Doesn't seem like there is any change on that front right now.

I just tried it out and there it works as is. If Tesla does make a change to the APIs in the future, I hope they introduce long-lived tokens so re-linking is no longer required.

Sorry I had been away and did not realize this was down. I've put the proxy back in place. Should work now.

Sorry I had been away and did not realize this was down. I've put the proxy back in place. Should work now.

This should be working now. I've put proxy server in place that bounces connections off a server outside of Amazon AWS.

This should be working now. I've put proxy server in place that bounces connections off a server outside of Amazon AWS.

No that does not help. Tesla is still blocking all calls from Amazon, which is where this is hosted. I am working on a workaround.

FYI: Seems like Tesla is once again blocking requests from Amazon AWS so this skill is not working right now. If this is not a short term issue we'll have to figure out a workaround.

I see that with my app too, and echo your sentiments. API requests form AWS fail but they do work from other networks.

Looks like calls from Amazon AWS are failing. They seem to be working from other endpoints. This had happened before a couple of years ago. Hope it temporary else we'll have to put a workaround in place.

The action has been re-instated. Let me know if you still see issues.

The Google Assistant version should be up now.

Thanks. I posted about this in the Google specific thread Integration with Google Home / Google Assistant - Now available for general use . Google has temporarily taken the "Action" down because the Privacy Link wasn't accessible :rolleyes: It's been re-submitted for review, hopefully should be...

Thanks for the offer. It's been submitted for review so its just wait-and-watch right now. Hopefully they don't come up with "new" reasons for rejecting.

"takedown" because a privacy link was invalid. :rolleyes: I guess it'll have to go though the whole approval cycle again before it is restored.

... and the Google Home did start the action. For good measure I did Unlink and try also.