Hi

This is a heads up - Tesla is planning to charge for access to the API.  

We are working on an option for streaming changes to the car (vs. polling) and this should be lower cost, but is still work in progress.  Note this only works for newer cars + 2021 

Suggest to lower the update rate to the case and only wake it if it makes sense

When developing the streaming option - are there fields of interest that should be added (I'll see if it is available) - there is a lot more data available 

 

 

 

what would you suggest I change the polling numbers to?  

I think the most important data points, at least for me, are:  battery charge percentage, if homelink is nearby, and the interior / exterior temperatures.  

We are working on a streaming option where data is only updated when data changes so polling becomes less of an issue. 

Edited February 24Feb 24 by Panda88

On the polling issue - If you are automating maybe poll once a day and then perform an update as first step in your program used for your automation.  I assume you are making decision in programs, so when these program execute you can update the data before making the decision.   I assume it is a few times a day keeping the data calls to a minimum. 

Naturally, if you look at the AC and want data updated polling would be needed