Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

TeslaMate [megathread]

This site may earn commission on affiliate links.
Good to know. Is the request for location coming from Teslamate or Tesla itself?
My understanding is the notification only is coming because of a third party app of some sort is accessing the car's GPS location. I have seen no indication of a notification in my car if the GPS is being requested by Tesla's app.

My guess is if you turn off the streaming API interface in your TeslaMate setup you will find that the notification will go away.
 
My understanding is the notification only is coming because of a third party app of some sort is accessing the car's GPS location. I have seen no indication of a notification in my car if the GPS is being requested by Tesla's app.

My guess is if you turn off the streaming API interface in your TeslaMate setup you will find that the notification will go away.
From the release notes from 2023.44:

"When this setting is on, your vehicle communicates directly with the Tesla app and other apps, but Tesla doesn’t track your location (see tesla.com/privacy)."

The only way to turn it off that I am aware of is to turn off sharing at Controls > Safety > Allow Mobile Access. This also turns off Tesla app access.
 
Does anyone know what going to happen with Teslamate?

My understanding it's going to stop working at the end of the month when the old API is turned off. I'd read the original developer said he wasn't going to further develop it but that some others had taken it over. I've not seen anything since.
 
Does anyone know what going to happen with Teslamate?

My understanding it's going to stop working at the end of the month when the old API is turned off. I'd read the original developer said he wasn't going to further develop it but that some others had taken it over. I've not seen anything since.
AFAIK, it is only the command API that is being shut down. Teslamate shouldn't be impacted.
 
  • Like
Reactions: PR-UK and cwanja
Rumor was that Tesla was going to delay the API shut down, which was scheduled for the end of 2023, while they come up with a better way to support people that are self-hosting solutions like TeslaMate. But I haven't heard anything further.
AFAIK, it is only the command API that is being shut down. Teslamate shouldn't be impacted.
Both of these things seem to be true. And there was discussion that the owners API would go the same route as the command API and be shut down. But as MP3Mike mentioned, that conversation has died down and it is not clear.

Ultimately - to be determined.
 
  • Like
Reactions: PR-UK
Both of these things seem to be true. And there was discussion that the owners API would go the same route as the command API and be shut down. But as MP3Mike mentioned, that conversation has died down and it is not clear.

Ultimately - to be determined.
The owner's API is now officially documented. They might change API limits or something, but I can't imagine they would shut it down.
 
  • Like
Reactions: PR-UK and cwanja
The owner's API is now officially documented. They might change API limits or something, but I can't imagine they would shut it down.
When you say owner's API is now officially documented, is this something different than the Fleet API? If so, would you be able to provide a link to where they have that documentation? I've been running my own logger written in python, and I'm concerned I'm about to look the basic capability to pull data before too long.
 
When you say owner's API is now officially documented, is this something different than the Fleet API? If so, would you be able to provide a link to where they have that documentation? I've been running my own logger written in python, and I'm concerned I'm about to look the basic capability to pull data before too long.
Sorry, I meant the "Fleet API". It is documented here: Tesla Fleet API
 
Sorry, I meant the "Fleet API". It is documented here: Tesla Fleet API
Thanks. I'm aware of where the Fleet API being documented. Problem with that is requires me to register a website, etc., which doesn't currently work for me as my current setup is all run locally on my home computer, not hosted in cloud or server. That's where if there was a separate Owner API that's been announced, I definitely wanted to be working on using it.
 
  • Like
Reactions: cwanja and jsight
Thanks. I'm aware of where the Fleet API being documented. Problem with that is requires me to register a website, etc., which doesn't currently work for me as my current setup is all run locally on my home computer, not hosted in cloud or server. That's where if there was a separate Owner API that's been announced, I definitely wanted to be working on using it.
I do wonder if they are going to keep the owners API around, but stop supporting it / enhancing it. And all efforts go towards the Fleet API. Such that eventually, if you want the "latest and greatest", the Fleet API is your only option.
 
This morning I drove 11.8 miles from home to the office. Tessie reported the drive correctly as 11.8 miles long. Yet, TeslaMate reported the drive as 7.3 miles long.
TeslaMate began tracking the drive while I was driving on the freeway. The final destination was appropriately identified as work by TeslaMate..
 
What do the logs say?
stderr
1/20/2024 13:43​
2024-01-20 21:43:30.421 UTC [28] LOG: checkpoint starting: time
stderr
1/20/2024 13:43​
2024-01-20 21:43:31.774 UTC [28] LOG: checkpoint complete: wrote 14 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.321 s, sync=0.019 s, total=1.353 s; sync files=11, longest=0.016 s, average=0.002 s; distance=46 kB, estimate=309 kB
stderr
1/20/2024 14:08​
2024-01-20 22:08:31.184 UTC [28] LOG: checkpoint starting: time
stderr
1/20/2024 14:08​
2024-01-20 22:08:35.744 UTC [28] LOG: checkpoint complete: wrote 46 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.518 s, sync=0.022 s, total=4.560 s; sync files=19, longest=0.007 s, average=0.002 s; distance=386 kB, estimate=386 kB
stderr
1/20/2024 14:13​
2024-01-20 22:13:31.772 UTC [28] LOG: checkpoint starting: time
stderr
1/20/2024 14:13​
2024-01-20 22:13:39.676 UTC [28] LOG: checkpoint complete: wrote 80 buffers (0.5%); 0 WAL file(s) added, 0 removed, 0 recycled; write=7.871 s, sync=0.012 s, total=7.904 s; sync files=16, longest=0.006 s, average=0.001 s; distance=684 kB, estimate=684 kB
stderr
1/20/2024 14:18​
2024-01-20 22:18:31.685 UTC [28] LOG: checkpoint starting: time
stderr
1/20/2024 14:18​
2024-01-20 22:18:37.774 UTC [28] LOG: checkpoint complete: wrote 61 buffers (0.4%); 0 WAL file(s) added, 0 removed, 0 recycled; write=6.032 s, sync=0.021 s, total=6.090 s; sync files=30, longest=0.005 s, average=0.001 s; distance=202 kB, estimate=636 kB
stderr
1/20/2024 14:23​
2024-01-20 22:23:31.798 UTC [28] LOG: checkpoint starting: time

I started the drive at 13:58 and ended at 14:12.
 
This morning I drove 11.8 miles from home to the office. Tessie reported the drive correctly as 11.8 miles long. Yet, TeslaMate reported the drive as 7.3 miles long.
TeslaMate began tracking the drive while I was driving on the freeway. The final destination was appropriately identified as work by TeslaMate..
My gut tells me that teslamate might have been ‘trying to sleep’. Those logs do not provide any details, you sure those are for TeslaMate?
 
  • Like
Reactions: jsight
stderr
1/20/2024 13:43​
2024-01-20 21:43:30.421 UTC [28] LOG: checkpoint starting: time
stderr
1/20/2024 13:43​
2024-01-20 21:43:31.774 UTC [28] LOG: checkpoint complete: wrote 14 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.321 s, sync=0.019 s, total=1.353 s; sync files=11, longest=0.016 s, average=0.002 s; distance=46 kB, estimate=309 kB
stderr
1/20/2024 14:08​
2024-01-20 22:08:31.184 UTC [28] LOG: checkpoint starting: time
stderr
1/20/2024 14:08​
2024-01-20 22:08:35.744 UTC [28] LOG: checkpoint complete: wrote 46 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.518 s, sync=0.022 s, total=4.560 s; sync files=19, longest=0.007 s, average=0.002 s; distance=386 kB, estimate=386 kB
stderr
1/20/2024 14:13​
2024-01-20 22:13:31.772 UTC [28] LOG: checkpoint starting: time
stderr
1/20/2024 14:13​
2024-01-20 22:13:39.676 UTC [28] LOG: checkpoint complete: wrote 80 buffers (0.5%); 0 WAL file(s) added, 0 removed, 0 recycled; write=7.871 s, sync=0.012 s, total=7.904 s; sync files=16, longest=0.006 s, average=0.001 s; distance=684 kB, estimate=684 kB
stderr
1/20/2024 14:18​
2024-01-20 22:18:31.685 UTC [28] LOG: checkpoint starting: time
stderr
1/20/2024 14:18​
2024-01-20 22:18:37.774 UTC [28] LOG: checkpoint complete: wrote 61 buffers (0.4%); 0 WAL file(s) added, 0 removed, 0 recycled; write=6.032 s, sync=0.021 s, total=6.090 s; sync files=30, longest=0.005 s, average=0.001 s; distance=202 kB, estimate=636 kB
stderr
1/20/2024 14:23​
2024-01-20 22:23:31.798 UTC [28] LOG: checkpoint starting: time

I started the drive at 13:58 and ended at 14:12.
Are you sure those are for Teslamate and not the db container?
 
Sorry, I posted results from a different container previously.
Here is the right one, except lat and lng have been changed for privacy.

2024-01-20 13:47:28 2024-01-20 13:47:28.227 [warning] WebSocket disconnected. Reconnecting …
2024-01-20 13:58:19 2024-01-20 13:58:19.652 [error] Vehicle Error: Vehicle is offline
2024-01-20 13:59:56 2024-01-20 13:59:56.875 car_id=1 [info] Fetching vehicle state ...
2024-01-20 14:05:00 2024-01-20 14:05:00.181 car_id=1 [info] Fetching vehicle state ...
2024-01-20 14:05:31 2024-01-20 14:05:31.834 [info] Start of drive initiated by: %TeslaApi.Stream.Data{time: ~U[2024-01-20 22:05:30.273Z], speed: 72, odometer: 24501.5, soc: 49, elevation: 290, est_heading: 62, est_lat: 74.155025, est_lng: -218.6489225, power: -4, shift_state: "D", range: 154, est_range: 157, heading: 62}
2024-01-20 14:05:31 2024-01-20 14:05:31.834 car_id=1 [info] Driving / Start
2024-01-20 14:13:46 2024-01-20 14:13:46.086 car_id=1 [info] Fetch already in progress ...
2024-01-20 14:13:46 2024-01-20 14:13:46.609 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (454.556 ms)
2024-01-20 14:13:47 2024-01-20 14:13:47.129 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (517.482 ms)
2024-01-20 14:13:47 2024-01-20 14:13:47.136 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of: 1705788825, heading: 90, latitude: 94.179041, longitude: -318.521456, native_latitude: 44.179041, native_location_supported: 1, native_longitude: -318.535687, native_type: "wgs", power: 1, shift_state: "P", speed: 0, timestamp: 1705788825366}
2024-01-20 14:13:47 2024-01-20 14:13:47.136 car_id=1 [info] Driving / Ended / 12 km – 8 min
2024-01-20 14:13:47 2024-01-20 14:13:47.136 car_id=1 [info] Start / :eek:nline
2024-01-20 14:15:02 2024-01-20 14:15:02.657 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/3744502389193844/vehicle_data -> 408 (140.384 ms)
2024-01-20 14:15:12 2024-01-20 14:15:12.950 car_id=1 [info] Start / :eek:ffline
2024-01-20 14:15:12 2024-01-20 14:15:12.970 car_id=1 [info] Disconnecting ...