TeslaMate [megathread]

[Sti-g]

Did you go for a drive after setting up Teslamate? It may just need some data to process.

Yes that was one of the first things I tried, but it didn't help.

 

[Sti-g]

First hit from Google :

How to pull application logs · teslamate-org teslamate · Discussion #1087

I'm having an issue signing in where I get "Error: unknown" in red at the top at initial sign-in on a completely new docker install. I looked around but could not find how to pull application logs ...

github.com

Yeah I know.. sorry, I was frustrated at the time. I had some other road blocks getting the RPI running, so at that point I was done.

 

[Sti-g]

I think it’s been covered earlier in the thread but Tesla have retired the API request which returns the list of vehicles. There is a request to return a list of products including vehicles, power walls, charges etc.

Teslamate uses the former and so get nothing, there’s a version floating around that uses the second option which seems to work

Whether these things keep working for long is another matter as the API is changing in general

Yes I believe this is the issue. Last night I was able to find someone with the same issue in r/TeslaMate. That person fixed it by using preview. I need to go figure that now.

 

[Sti-g]

Yeah looks like the API update is the issue:

[36mteslamate_1 |[0m 2024-01-27 21:48:07.628 [info] GET https://owner-api.teslamotors.com/api/1/vehicles -> 412 (105.261 ms)
[36mteslamate_1 |[0m 2024-01-27 21:48:07.629 [warning] TeslaApi.Error / %{"error" => "Endpoint is only available on fleetapi. Visit Getting Started With Third-Party Apps | Tesla for more info", "error_description" => "", "response" => nil}
[36mteslamate_1 |[0m 2024-01-27 21:48:07.629 [warning] Could not get vehicles: :unknown

 

[Sti-g]

Yes, docker image

ghcr.io/teslamate-org/teslamate:pr-3630

Oh I got it now.

I needed to change the configuration file docker-compose.yml to tell which version of teslamate to use.

Now I can see my car in the teslamate. Thank you for the help!

 

[bodosom]

I'm looking for a replacement for TESLAMATE (TM) since I think the old API will stop working any time now. I'd like to import my data (from TM or TeslaFi) but so far I've only found (partial) data import in Tessie.

Of course neither TeslaFi or Tessie are particularly good replacements for Teslamate

 

[DeltaOne]

I'm looking for a replacement for TESLAMATE (TM) since I think the old API will stop working any time now. I'd like to import my data (from TM or TeslaFi) but so far I've only found (partial) data import in Tessie.

Of course neither TeslaFi or Tessie are particularly good replacements for Teslamate

I went with Tessie. Import was good enough for me. I've been very happy with Tessie so far.

 

[bodosom]

... Import was good enough for me. ...

Not that I want to be that guy but I had two years of data to import and quite a few Home>Someplace>Park>Home trips turned into Home>Home. The mileage is correct but ...

 

[Alan_F]

I went with Tessie. Import was good enough for me. I've been very happy with Tessie so far.

I also went with Tessie, although I intend to keep Teslamate running too for as long as that remains an option.

 

[cwanja]

I’ll drop it here. I have asked TeslaScope to have a TeslaMate import option. No response on that feature.

 

[bodosom]

.. I have asked TeslaScope to have a TeslaMate import option. ...

Postgres can export as CSV so CSV import is sufficient.

 

[cwanja]

Postgres can export as CSV so CSV import is sufficient.

Interesting. I will have to look into it. I figure TeslaScope still has to plan and map the data. The call out TeslaFi on the details page, but not TeslaMate.

Might take a spin at it with a trial account and see.

 

[bodosom]

There a Postgres one-liner export command at the Tessie site. Schema names for Teslamate and TeslaFi attached.

 

[cwanja]

There a Postgres one-liner export command at the Tessie site. Schema names for Teslamate and TeslaFi attached.

Thanks for these. Seeing these, definitely a data mapping exercise. Will look into it. Thank you again.

 

[Durzel]

Why would there need to be a replacement for TeslaMate? Are we anticipating it not being updated, or is there something about the new API that makes it incompatible (e.g. it's chargeable?)

 

[bodosom]

Thanks for these. Seeing these, definitely a data mapping exercise. Will look into it. Thank you again.

I also noticed that TeslaScope expects date/time as UTC.

 

[cwanja]

Why would there need to be a replacement for TeslaMate? Are we anticipating it not being updated, or is there something about the new API that makes it incompatible (e.g. it's chargeable?)

Purely speculative on my part, but believe the new API will be rate limiting self-installations like TeslaMate. Would require additional setup and developer registration which might be fine for some, but not all.

 

[bodosom]

Why would there need to be a replacement for TeslaMate? Are we anticipating it not being updated, or is there something about the new API that makes it incompatible (e.g. it's chargeable?)

Have you reviewed the the Github comments and the Tesla developer documents?
E.g. fix: use product api endpoint to fetch vehicles by JakobLichterfeld · Pull Request #3630 · teslamate-org/teslamate which fixes the change in the legacy API for existing users but not for new/changed vehicles.

It looks like on-going free access (if there is any) will require:

A point to point on-boarding with Tesla to put cryptographic keys in place.​

A greatly restricted transaction rate (which doesn't matter for some things).​

​

Everyone that talks to the Tesla servers will (probably) eventually be required to be a "registered with Tesla 'developer'".

 

[init6]

Perhaps @Medved_77 might look again at Teslamate as a Service.

 

[MP3Mike]

Perhaps @Medved_77 might look again at Teslamate as a Service.

You mean like MyTeslaMate or https://www.teslamatecloud.com/ (I assume they could register as a Tesla developer and use that to host multiple clients.)