Configurable polling interval for Tessie integration

The polling interval for the Tessie integration is currently fixed at 10 seconds, which matches the maximum data change rate in Tessie. In many use cases however, polling this aggressively is not needed, and can be backed off quite a bit. I’d like to suggest that this interval be made configurable, perhaps with a minimum value of 10 seconds.

I’m not allowed to make this configurable. You can disable polling and use your own automation to manually trigger refresh based on whatever logic you like.

The integration will be using cache in 2024.2 and will only pull state when the vehicle is awake, as it was keeping old Model S/X vehicles awake.

Pardon my ignorance, but I’m not sure I understand. Is this is prohibited by HA? Is it a new restriction? There are other integrations (in core) that have configurable scan/update intervals.

Can you give some examples. See the note at the top of Entity integration platform options - Home Assistant about being able to set scan interval.

Pentair Screen logic is one that I actively use. I’ve seen others, but I’ve removed a bunch of integrations that I wasn’t actively using for automation.

Edit: Note that this is configuration of the default polling interval. To me, that’s a bit different than performing polling based on triggers, conditions and such.

Edit 2: Control4, NUT, Xiaomi are some other examples.

Confirmed on Discord, no longer allowed.

Okay, thank you for checking. Appreciate it.

Okay, here’s an interesting question… Since homeassistant.update_entity requires an entity as a target (not a device or integration), how will this interact when there are multiple vehicles? Is it sufficient to just update one? If you call update_entity on the status each vehicle, does it mean that the poll will happen multiple times?

The vehicles have a coordinator each, so you need to hit 1 entity for each vehicle.

Its a really good question and I have no idea how you would know this unless you tested or read the source code. The very first implementation of this integration grabbed all vehicles at once, but that had the issue of never knowing when a vehicle was asleep.

1 Like