Populate MQTT Device Attributes from State

[FloatingBoater (James Derrick)]

I can think of a hack to build a HASS Discovery block of JSON from the version sensor, then publish to MQTT from HASS, which then injests the auto-discovery config and configures the main Tesla entity replacing the local YAML config.

Here’s a mosquitto_pub example to get you started hacking together a proof of concept:

PSA: MQTT Name changes in 2023.8

Note to developers - Whilst you’re re-factoring your MQTT Discovery code, can I suggest adding additional values to improve how users can interact with your hardware? Here’s an example from my own test code (with some light changes) which adds: The example Device is configured with optional extra information such as manufacturer, version, and the ‘suggested_location’ which can be used to set the Area. The example Entity adds optional extra values such as an icon, the device class and unit of …

HASS changes immediately on receiving the publish.

Another example:

MQTT Discovery pending

Hi, After writing a Python device using HASS Discovery, I found HASS changes configuration state almost immediately after I published the discovery topics to the broker. This made manual testing of the structure straightforward as the debug cycle was basically: Delete the previous retained topics using MQTT Explorer Publish new discovery data with mosquitto_pub on the command line See what happened in HASS immediately Cross-check what the broker actually published using https://mqtt-explorer…

I’ve published data to MQTT from HASS automations but not discovery - should work as all are just MQTT payloads.

Don’t know if a more Python-esque API-based solution exists though.

If this helps, this post!