Potential changes to Teslamate MQTT format...

[LelandSindt]

Have a look at teslamate-org/teslamate#3660 --- seems these changes could/would effect this project.

[LelandSindt]

... or maybe it's no big deal 😄

https://github.com/brchri/tesla-geogdo/blob/main/examples/config.circular.homeassistant.yml#L46-L47

[brchri]

Thanks for flagging this. As you discovered, Tesla-GeoGDO should be able to handle this change fine as long as they don't nest lat and lng values into json subkeys, but once teslamate has made these changes and users update to that version, Tesla-GeoGDO will break until users update their geogdo configurations to use the complex topic tracker type.

I'll keep an eye on that feature, and if they do decide to nest the lat and lng keys for some reason, I'll look into updating this project to be compatible, but otherwise it should be fine. I'll also probably update documentation as most of my simple mqtt topic examples use teslamate as the example, which won't make sense anymore.

Thanks again for the heads up so I'm not scrambling to figure out what happened when I (and other users) break on a teslamate update. 😄 This is actually a good change for teslamate to make, as I've had to deal with the exact problem described in the feature request where lat and lng can be received out of order and it's unclear whether each new value pairs with the preceeding or succeeding value of the other, and have had to write some workarounds in this code to account for that. This will make it cleaner and better. 🚀