Entity status incorrect - takes ages to update

[jkerekes99]

Hi all,
I have just started using the custom integration with Home Assistant and I built a automation to notify my wife when I am leaving work and coming home.

The trigger is when the state of the destination location tracker changes to "Home",

However, when testing this, the destination location doesn't change to "Home" until 5-7 minutes into driving home.
Why doesn't the status of that entity change immediately after me pressing Home in the Tesla?

I did some reading in the Polling policy section on the wiki, it states:

Polling interval is set to 660 seconds (default)
Every minute, Teslas servers are scanned to check the online status of all cars.
If any cars are online (awake) we check what time we last did a full poll of that car.
If this was at least polling_interval (default 660) seconds ago, we will do a new, full poll of the car.
This will update the car status (locks, charge status etc) of all online (awake) cars every 11 minutes. Sleeping cars are never polled, and driving cars are polled every 60 seconds (not configureable) or polling_interval depending which one is smallest but not more often than every 10 seconds.

It states that driving cars will be polled every 60 seconds.
I started driving when leaving the office, why is it not polling every 60 seconds?

Any help would be appreciated.

[skipishere]

The problem here is that until the 660 second poll occurs and knows that the car is now driving it won't start the polling every 60 seconds, so you can end up in a situation where if timed just right it can take 11 minutes until it updates and then will update on the 12th minute (and every minute there after until you stop)

[jkerekes99]

Ah ok, that makes sense.

What is the recommendation to have my automation work as intended?

Is there any negative impacts to decreasing polling time to stay 120 seconds?
Will it cause the car not to sleep?

[skipishere]

You could potentially have an automation that triggers when the phone connects to the car that forces a data refresh which would allow for the default long poll? Depending if you're still using the unofficial API or the Fleet one changing the polling time could have bigger impacts (if on Fleet API you could burn through the 'free' credits quite quickly, and yeah it could stop the car being able to sleep)

[jkerekes99]

Thank you for the idea @skipishere .
I used an apple shortcut to automatically trigger when my iPhone connects to the Tesla bluetooth.

The shortcut action is to trigger a home assistant action to press the "Force data update" button on the Tesla integration after a 60 second delay (this gives me enough time to put the car in Drive).

When the car is in Drive and the manual update is triggered, it guess it detects the car is in drive and changes to poll every minute (because the car is in Drive).