Scheduled polling for Tesla

I have configured to poll my Tesla car and I have automations to start/stop the car charging based on my solar panel output. This means I only ever use 100% home-grown solar juice in the car.
I have a polling interval of 300 and all is working well.
Is there a way to set a schedule for the polling so that I only poll the car between certain times of the day? The polling all day and night stops the car from sleeping and so causes significant energy consumption at times when the poling has zero value (eg: at night).

1 Like

Were you able to figure something out on this?

Nope. You are the first to respond and I’ve not worked out a way myself either.
Do you have any ideas?

sorry to revive an old thread, but I’m having the same issue. I would love to only poll when it is out of the garage (you know… when there is real value…)
I have a reeeeally janky fix and it is to block homeassistant at the OS level from being able to hit the tesla API by putting in a fake entry in /etc/hosts for
i accomplish this with an automation that removes the entry when i leave the house, and puts it back in when i arrive home. It may not work for, but i figured i would mention it in here anyway. the downside to my stupid fix is that the log is full of failures for the tesla component when im blocking the api calls. and if you want to trigger something, you have to unblock it first (which i made a cli switch for)
Ideally, we would be able to dynamically update the polling frequency through an automation.


I just started with HA and am using hassio and Node-RED for my automations. There is a packaged Node-RED component that you can import, node-red-contrib-teslams , and it gives basic control and status. There are a ton of other components such as time of day controls (bigtimer) that should make it possible to do what you want to do. You could also wire in a sensor that detects when your car shows up on WiFi or some other way of sensing that it is in the garage.

You can copy the example at the bottom of and paste it into a tab (flow) to get started.

Example data:

Just wanted to +1 on this. This component causes some serious vampire drain. Setting polling to 60min right now, because I don’t use it in any automations yet. But being able to schedule the polling would be great!

Edit: submitted an issue on GitHub for this


Exactly the same here. The default polling interval of 300 seconds cause a huge amount of vampire / phantom drain. (~6-7% per day).
I set it at 60’, so 3600 second for now, but I am not even sure I will keep the component in it’s current state.
A example where it’s done right is the TezLab app, which tells you the car went into deep sleep, and warns you that you’ll wake it if you poll it right now.
OTOH, it would be nice it if Tesla API would allow the poll the “most recent values” without waking the car.

1 Like