Docs: move from mqtt.yaml to packages

[KrzysztofHajdamowicz]

In relation to docs: https://docs.teslamate.org/docs/integrations/home_assistant/
Packaging docs: https://www.home-assistant.io/docs/configuration/packages/

In my opinion, packaging mechanism of Home Assistant allows for clean separation of Teslamate-related entities from other manually-configured MQTT entities.
That way, when user have multiple entities manually-configured and teslamate-related entries change, user does not need to scroll through multiple screens of file and just copy-pastes config from Teslamate website.

[brianmay]

The best solution would be if somebody were to implement home-assistant auto-discovery. That way no manual configuration of home-assistant would be required - at least that is the theory.

https://www.home-assistant.io/integrations/mqtt/#mqtt-discovery

I think I had a bug report open on this, but can't find it right now.

If for some reason auto-discovery is insufficient for our purposes, then maybe packages would be a good fallback.

[KrzysztofHajdamowicz]

Discovery would be great, here's the discussion for that: #1599

So far no GH Issues were open on that topic.

[brianmay]

My memory lies, I probably was thinking of this post: #4472 (comment)

Which is in a issue, just not an issue dedicated to this problem.

[brianmay]

I might be able to have a look at putting code in to send the required MQTT messages. But setting and testing the required json blobs, I think that is going to be the challenging part.

[KrzysztofHajdamowicz]

https://community.home-assistant.io/t/manually-add-mqtt-entities/264695/7
You can test setting necessary JSON messages via script.example executing mqtt.publish action

[nebhale]

Now implemented: https://github.com/teslamate-org/teslamate/releases#release-v4.1.0

I'd hope that after a soak period, the HA documentation eliminates all that YAML and talks about the env-var only. That seems like the right time for a move.