Location data not updating in HA via MQTT (or at least that's what it seems to be) about tesla HOT 14 CLOSED

My polling interval is set at a very high interval - 1 month: 2592000

from tesla.

@bdraco I believe #954 may have broken updates coming from MQTT (primarily via teslamate). If you have time to take a quick look I'd appreciate it. No worries if you don't have this setup. Thanks!

from tesla.

Thanks a lot, with 3.22.1, getting data via MQTT works as well as with 3.21.

from tesla.

I can observe the same issue. Reverting one version back to .21 fixed it.

from tesla.

I see the same behavior in .22. The sensors (location, for example) update every minute or so instead of instantaneously.
Version .21 doesn't show this behavior.

from tesla.

Glad to know that I wasn’t the only one! I thought I broke something when I migrated teslamate and couldn’t figure out what I did wrong.

FWIW, I can confirm as well that downgrading to .21 fixed everything for me as well.

from tesla.

I wonder if it has anything to do with 954

from tesla.

What do people have the polling interval set to when they are using teslamate? I can't tell if it is polling twice... or if the direct poll is disabled when the data is coming from mqtt. Thanks

from tesla.

I believe there are two issues with .22:

• Retrieving location data from the car, not via MQTT
• MQTT data is only imported at long intervals, not instant when it's published via MQTT. With .21, data updates immediately once Teslamate gets new states via the streaming API. It seems that MQTT data is imported at the same interval that would be used for the Tesla API.

Both issues are gone after a downgrade to .21. In .21, I can set my polling interval to high numbers like 3600s, and any change like different charging power propagates to Home Assistant within seconds.

from tesla.

@alandtse it seems this is a legit issue if you can perhaps take a look...

from tesla.

Yeah I also have a super high poll time and use MQTT to push data from TeslaMate and it appears to just get stuck on the latest version, reverting back to .21 is fine.

from tesla.

I don't use the mqtt/teslamate code, but I'll take a look and see if there is anything obvious

from tesla.

I think #989 should solve it, but I don't have a way to test it

from tesla.

There are also some tasks being created that could be simple callbacks

#990

from tesla.