You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately with the Fleet API limits of only 300 API queries a day this quickly exhausts the allowed limit and further polling then fails and the integration can't be used to view up-to-date information.
This is doubly problematic when using TeslaMate as Tesla seems to disable the streaming telemety updates at the same time.
Describe the solution you'd like
When electing to update sensor values from MQTT when using TeslaMate OR when using the Fleet API, I would like to be able to disable the automatic changes to polling frequency - and for the polling frequency entered during configuration to be adhered to.
Describe alternatives you've considered
I've had to disable polling by the integration entirely now, and only use the integration for updates, however, since not all sensor values update from MQTT this leads to issues, e.g., last updated sensor.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
According to https://github.com/alandtse/tesla/wiki/Polling-policy when the car is driving the polling is changed to every 60 seconds.
Unfortunately with the Fleet API limits of only 300 API queries a day this quickly exhausts the allowed limit and further polling then fails and the integration can't be used to view up-to-date information.
This is doubly problematic when using TeslaMate as Tesla seems to disable the streaming telemety updates at the same time.
Describe the solution you'd like
When electing to update sensor values from MQTT when using TeslaMate OR when using the Fleet API, I would like to be able to disable the automatic changes to polling frequency - and for the polling frequency entered during configuration to be adhered to.
Describe alternatives you've considered
I've had to disable polling by the integration entirely now, and only use the integration for updates, however, since not all sensor values update from MQTT this leads to issues, e.g., last updated sensor.
The text was updated successfully, but these errors were encountered: