Indigo Domotics

Just started receiving this error today:

Tesla EV Control Fetching vehicles...
Tesla EV Control Debug Token expired - renewing oauth token for 44 days...
Tesla EV Control Debug Pre-JSON: {"response":"endpoint_deprecated:_please_update_your_app."}
Tesla EV Control Error 'created_at'
Tesla EV Control Error Error creating connection
Tesla EV Control Error Plugin version: 1.0.19

It then fails to get any information obviously because it no longer has the vehicle name to search.

Has the Tesla API been deprecated?

FYI: Just found this on another Tesla API author's site:

https://tesla-api.timdorr.com/api-basics/authentication

It appears that Tesla has deprecated user/password token in favor of their OAuth2 implementation only that was rolled out late last year. They supported both forms until this morning.

more info here:
https://github.com/mlowijs/tesla_api/pull/38

I've filed an issue on the Plugin's Github page:
https://github.com/howartp84/TeslaControl/issues/2

Hi both.

Until Indigo brings out OAuth support, i'm not aware we can integrate plugins with any OAuth services so there's nothing I can do about this at the moment.

Peter

Homebridge has the same issue as of today.

JP

The Smarthings Hubitat app and device is also reporting the same

howartp wrote:

Hi both.

Until Indigo brings out OAuth support, i'm not aware we can integrate plugins with any OAuth services so there's nothing I can do about this at the moment.

Peter

@Matt @Jay

Am I correct in this general belief, ie we can't integrate with OAuth without Indigo doing something or me hosting a web endpoint somewhere that takes users credentials?

Web services that have a published API will usually have a developer portal that can be used to obtain OAuth tokens. That's what the Slack and Twilio plugins use. Or a PIN-based mechanism like Ecobee uses. But if neither of those are available, then you'll need a webserver that can catch the callback.

I experimented briefly with using ngrok to implement something that would work, but never completed it.

howartp wrote:

howartp wrote:

Hi both.

Until Indigo brings out OAuth support, i'm not aware we can integrate plugins with any OAuth services so there's nothing I can do about this at the moment.

Peter

@Matt @Jay

Am I correct in this general belief, ie we can't integrate with OAuth without Indigo doing something or me hosting a web endpoint somewhere that takes users credentials?

That's actually a complex question. OAuth has two sides: the client side and the server side. One OAuth client flow (a client, in this case the plugin asks a service to authenticate, in this case Tesla, which then would provide tokens back via HTTP redirects to use with their API) is tricky because Indigo Plugins can't do the necessary redirection like a web-based client can. I'm a bit surprised that Tesla doesn't allow you to generate tokens from their UI that can be used with their API in circumstances where this is the case because the standard flow is heavily dependent on several HTTP redirects. This is something that we want to look at in the future but it's not part of the work we're doing for the next feature release.

What we are implementing for the next feature release is the OAuth server side, to support integration FROM other services like Alexa and Google Home using customers Indigo Accounts to authenticate access to their Indigo Server. Users will also be able to generate tokens for use with the REST API for services that don't/can't do the http redirect dance required for that kind of authentication. But this is the server side OAuth implementation, not a client side implementation.

Now that 2021.1 is out, any hope of getting this plugin to work again?

JP

Again, I don't know any specifics about the Tesla API.

However, I believe with the addition of the ability for a plugin to handle HTTP requests, it may be possible for a plugin to implement a full OAuth client API since the necessary redirects should be possible. I'll leave it up to @howartp to look into it though I will provide as much assistance as I can with his investigation if he should choose to do so.

Thank you, Jay. Will keep my fingers crossed.

JP

I’ll certainly be looking at it.

Jay, I’ll be in touch.


Sent from my iPhone using Tapatalk Pro

Hi

I use the same api code for my Tesla battery plugin. Accesses the same info and has been doing so for a while - successfully!

Tesla been annoyingly changing API access/login, left and right. But is currently working. They removed headers, then added them back in and then added a captcha code (which will stuff up everyone) - that’s subsequently been removed.

Have a look at my implementation; which is basically the website you linked to above using Oauth, getting token and reusing etc.

Glenn


Sent from my iPad using Tapatalk

Any update?