-
Notifications
You must be signed in to change notification settings - Fork 765
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customize intervals between vehicle_data calls #3940
Conversation
@brianmay @JakobLichterfeld let me know what you think about this PR. The current intervals are kept by default. I added some environment variables to be able to modify the intervals. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general looks good.
Have mixed feelings about this. We don't want people to think they have to configure these values and end up with incorrect values that are loading up Tesla's servers.
Suggestion - add somewhere a note that it is strongly recommended that you do not set that values unless you really know what you are doing.
I will add a bold note about this in the env vars description. |
A question... when the vehicle is woken up, eg. for driving or charging, will Teslamate notice this in real time via streaming API, regardless of this interval? Or will we run the risk of losing the first few minutes of each drive with a sufficiently large interval? 300 polls in 24h is just once per 5 minutes ... |
Yes, the data retrieved from the streaming API is independent of these intervals and Tesla continues to get it in real time. Obviously with long intervals, the data is much less precise... but streaming helps limit losses. Note that for the "future": the new Telemetry only sends this information every minute while the "owner" streaming API sends every second during drives. |
Not that the streaming parameters supported is very restricted. Anything not supported in streaming will be affected, e.g. state of doors being opened/closed. State of vehicle being plugged in, etc. |
Thank you ! |
As discussed here, the
vehicule_data
endpoint is limited for Tesla Fleet API users (300 hits per vehicle per day).With the current hard-coded polling values, this limit is quickly exceeded.
I want to let the Tesla Telemetry send the real time events via web streaming API and be able to customize polling intervals to try to not exceed this limit on
vehicle_data
.