[Feature Request] Improve Home Assistant device metadata (model name & sw_version) in native discovery

[papinist]

Is there an existing issue for this?

• I have checked the existing issues and discussions, and I can confirm that there are no duplicates.

What happened?

With the introduction of native HA discovery in v4.1.1, I noticed that the Device Info panel in Home Assistant appears quite bare compared to the output previously generated by the legacy teslamate-discovery container.

Currently, the native discovery publishes:

• Model: 3 (instead of Model 3 or the full designation like Model 3 74D)
• Firmware / Software Version: Not set on the MQTT device payload (so the "Firmware" row is missing in HA Device Info).

Describe alternatives you've considered

Manual overrides in Home Assistant customization, but having it natively populated from TeslaMate would provide a much cleaner out-of-the-box experience for all users migrating from teslamate-discovery.

Expected Behavior

It would be great to enrich the MQTT device metadata payload published during discovery:

1. Model Name: Map the internal model code to a human-readable model string (e.g. Model 3 or include the trim details if available) instead of just the raw number/letter (3).
2. Software Version: Include "sw_version" in the device dictionary payload (referencing the current vehicle version topic/data), so Home Assistant displays the installed firmware directly in the device summary card.

Can the issue reliably be reproduced?

Yes

Steps To Reproduce the issue

Just look at the info panel in device page

Relevant log output

.

Screenshots

Here is a side-by-side comparison of the Device Info card in Home Assistant:

• Legacy teslamate-discovery: Displays full Model info (Model 3 74D) and Firmware: 2026.26.1.
• Native v4.1.1 discovery: Displays only 3 under the car name and lacks firmware metadata.

Additional data

No response

Type of installation

Docker (https://docs.teslamate.org/docs/installation/docker/)

Version

v4.1.1

PostgreSQL version

No response

Are you running latest major supported PostgreSQL version?

• I run the latest major supported PostgreSQL version

Are you using a reverse Proxy for TeslaMate?

No

Details about your reverse Proxy if applicable

No response

[nebhale]

For reference the way those strings were created can be found here.

I'd recently been playing with an even more sophisticated version of that here.

[papinist]

BTW, @nebhale thank you for your teslamate-discovery, I've used it for a while until now and it worked great!