feat: bundle MQTT data in one json blob about teslamate HOT 8 OPEN

I would like to make sure I understand the intent here. The idea is to group similar topics into a single topic with a json payload.

for example

/teslamate/cars/1/latitude = 1234

and

/teslamate/cars/1/longitude = 1234

would be made available as

/teslamate/cars/1/location = {"latitude":123,"longitude":1234}

but not to group all topics into a single json payload...

/teslamate/cars/1 = { <all of the keys and values....> }

While I can see the value in grouping lat and long into location as they will be consumed together... grouping too many topics together negates the flexibility and scalability that MQTT provides by design.

from teslamate.

Also in regards to the other discussion #3657 It would be nice to have the distance and minutes to destination into MQTT so that I could automate things for my Home Assistant instance.

That's already merged and will be included in the next release.

Just confirming that my PR did not include distance and minutes in the MQTT output, I only added it to the state parser

from teslamate.

Tagging @tobiasehlert and @brchri as their projects consume Teslamate MQTT payloads.

from teslamate.

Continued discussion from #3657, focussed on active drive navigation data:

I fully agree, for "same time define data" such as latlong and initial navigation state. For the other travel ETA's not so much, these update throughout the journey, which will require to update the complete blob. It is likely that the latlong will be set (data will be pushed/updated) and the route will still be calculating, resulting in two messages anyway, not solving the issue. This can be tested

Also adding more stuff to a big json requires the processing client (often HA) to parse this json, where normally an mqtt topic can be read easily.

I think both ways can be done and advocated for, zigbee2mqtt is more json based too, but i'd suggest to not wait for a possible complete revamp of the mqtt structure for this awesome change already.

from teslamate.

Also in regards to the other discussion #3657 It would be nice to have the distance and minutes to destination into MQTT so that I could automate things for my Home Assistant instance.

from teslamate.

Also in regards to the other discussion #3657 It would be nice to have the distance and minutes to destination into MQTT so that I could automate things for my Home Assistant instance.

That's already merged and will be included in the next release.

from teslamate.

Correct, the idea is to bundle the data which belongs together, like position data in one Json blob, time and distance to destination.

from teslamate.

Just confirming that my PR did not include distance and minutes in the MQTT output, I only added it to the state parser

Thanks for clarification, absolutely right.

from teslamate.