I migrated my HASS from a bespoke VM to a Hass.io one. I managed to configure everything rapidly except your add-on, as it had an issue communicating with the MQTT server. The documentation was a bit misleading, implying "Configuration Not needed when using HA Add-On". Only after I while I realized that this pertains to not having to create a settings.local.json file explicitly, as the configuration is being done in the UI. I suppose you could clarify this a bit more.
The reason it was extra confusing is because the settings in the UI come pre-populated, including the MQTT host/credentials. And I assumed these defaults were fine, since all the other add-ons I used so far indeed did not require additional configuration when installed in Hass.io, by resorting to its built-in addons mqtt credentials.
So my point is that it would make sense to have docs mention that an additional account is needed in HA and its credentials when installing in Hass.io via addons repo.
And since we're at it, why can't you use the default addons credentials like others do?
Hi there,
I migrated my HASS from a bespoke VM to a Hass.io one. I managed to configure everything rapidly except your add-on, as it had an issue communicating with the MQTT server. The documentation was a bit misleading, implying "Configuration Not needed when using HA Add-On". Only after I while I realized that this pertains to not having to create a settings.local.json file explicitly, as the configuration is being done in the UI. I suppose you could clarify this a bit more.
The reason it was extra confusing is because the settings in the UI come pre-populated, including the MQTT host/credentials. And I assumed these defaults were fine, since all the other add-ons I used so far indeed did not require additional configuration when installed in Hass.io, by resorting to its built-in
addonsmqtt credentials.So my point is that it would make sense to have docs mention that an additional account is needed in HA and its credentials when installing in Hass.io via addons repo.
And since we're at it, why can't you use the default
addonscredentials like others do?