Data while driving is updated much less frequently than before

[roughwood]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

I've noticed recently that when looking at drive data, the data points (particularly on the map) are updated much less frequently than before. It appears that my car location is only updated every 10-15 seconds, resulting in jagged lines across the map instead of lines that follow the true path of the vehicle. When I go back to older drives, the more precise data points are there. Has something changed with the API?

Expected Behavior

No response

Steps To Reproduce

No response

Relevant log output

N/A

Screenshots

No response

Additional data

No response

Type of installation

Docker

Version

1.28.5

[roughwood]

[cwanja]

Are all of your new drives like this or a subset of drives?

Has something changed with the API?

No, but I have seen even back to back drives have different polling rates. There was a discussion or issue where we were chatting about the intermittent nature of this and not sure if it is TeslaMate or Tesla's API doing the limiting. But nothing fundamental has changed from TeslaMate.

[roughwood]

It does appear to be a subset. Some drives appear normally. I would say about 75% of my recent drives display this behavior though.

[cwanja]

It does appear to be a subset. Some drives appear normally. I would say about 75% of my recent drives display this behavior though.

What does the TeslaMate logs say during the drives where they show jagged position data?

[JakobLichterfeld]

I assume this is the Tesla API rate limit

[brianmay]

Everything here would seem to suggest that streaming was not working for some reason.

Another possibility that I have seen myself is that the car is an an area with poor mobile coverage.

[mikec-design]

I'm also seeing this recently. My visited map is much more "jagged" than it used to be. This is in 1.28.2.

[woyteck1]

Hi, I investigated such behaviour before.

In my case, this was rate limiting by Tesla prior to launch of Giga Berlin.
I think they do it on some occasions, with timing significant to Tesla, as to limit the API access, so their servers are not overwhelmed by potential malicious traffic.