search

bassmaster187 / TeslaLogger

TeslaLogger is a self hosted data logger for your Tesla Model S/3/X/Y. Actually it supports RaspberryPi 3B, 3B+, 4B, Docker and Synology NAS.
https://www.teslalogger.de
GNU General Public License v3.0
518 stars 171 forks source link

Scrambled location data #1331

Closed ostorezio closed 4 months ago

ostorezio commented 4 months ago

Append Logfile Nothing relevant apparently, mostly a number of entry like this one: 09.07.2024 12:59:06 : #1[Thread Pool Worker:3575]: FT: Telemetry Server Data 09.07.2024 12:59:06 : #1[Thread Pool Worker:3575]: FT: Speed: 22.991 09.07.2024 12:59:06 : #1[Thread Pool Worker:3575]: *** FT: Insert Location 09.07.2024 12:59:19 : #1[StreamAPIThread_1:3381]: shift_state: D Power: 8 Datetime: 09.07.2024 12:59:19 09.07.2024 12:59:22 : #1[Thread Pool Worker:3552]: Command: vehicle_data?endpoints=drive_state%3Blocation_data%3Bclimate_state%3Bvehicle_state%3Bcharge_state%3Bvehicle_config&let_sleep=true [367]

Describe the bug Geolocation (lat, lon) data during trip gets scrambled, i.e on the map the trip is shown with jumps or overlaps, as in this screenshot, the trip was a one-way, from right to left.

Screen Shot 2024-07-09 at 2 09 18 PM

To Reproduce Go to the baker, and look at the trip on the map

Expected behavior The trip shown on map should be continuous and derivable function, no jumps, no overlaps, no back&forth.

Screenshots I did a database analysis for the same trip, here's the lat/lon vs time:

lat_lon_vs_time

In the real trip, latitude should go north all the time whereas longitude should be mainly east to west, as you can see in the graph, both lat and lon has spikes

Here is the georefences graph: lat_lon

The trip has been one way, but from the graph it looks more or less like a round trip with overlapped legs, back & forth

Teslalogger Type Raspberry Pi 4 Model B Rev 1.4 Linux raspberry 4.19.118-v7l+ Teslalogger: 1.58.9.0

Do you use Tasker or iBeacon No

Additional context Is that a Tesla telemetry issue? GPS scrambling?

bassmaster187 commented 4 months ago

could you please send me an email with your VIN and the date / time of your problem. I can just check it next week, because I'm in vacation right now

ostorezio commented 4 months ago

Sure, your email is? As for the time, it happens all the time, since a few releases back. See also Issue #1300, I have a lot of missing/incorrect data, I don't know if the two problems are related

ostorezio commented 4 months ago

The lon/lat errors show a strange pattern, periodic-like, look at this:

lat_lon_vs_time_1

misiu11 commented 4 months ago

I have a similar problem. The position data is very inaccurate. The recording is also very late and sometimes even stops completely. The web display is also not correct. It still shows that my vehicle is open although it is definitely locked.

Teslalogger runs as a VM with Debian 12 in a Docker container. Scan my tesla is also included. I use the Fleet API

KapUttyy commented 4 months ago

Seems to be solved for me this morning.

ostorezio commented 4 months ago

Yep! 1.59.1 does the trick