So, I have no idea what happened, but now I’m spiraling down a rabbit hole again.
The Mosquitto MQTT Broker page has conflicting information, or it’s poorly written. The first section suggests we need to create a config such as is displayed, but immediately below that is something about ACL definitions, so I jump to that section.
…where I am reading that it is possible to restrict access to topics…etc. It’s possible? But at the beginning of the page the note says ACL is required? Is it required or not?
I don’t want to restrict anything as far as I know…so then it says to enable unrestricted access (I guess that’s what I want) follow the 3 steps. So I do that.
Then I see that
"This add-on is attached to the Home Assistant user system, so mqtt clients can make use of these credentials. Local users may also still be set independently within the configuration options for the add-on. For the internal Hass.io ecosystem we register homeassistant and addons, so these may not be used as user names."
So, which is it? Local users independently or…internal users??? Confusing.
Then I also see that I’m supposed to disable 1883 ports? Not sure why I would do that. If I do, none of my tasmota devices can connect to the broker.
In the section Using Mosquitto with Hass.io there are 3 steps followed by a yaml entry with a note that says yaml modifications are not required. Where is this yaml supposed to be now if it’s anywhere, even though it’s not needed… ???
At this point, none of my devices are auto-detecting anymore, the broker is intermittent in its ability to be reached by any client anywhere on my network, and … well, what in the world is going on?
Access is controlled by the ACL flie. to have unrestricted access for a particular client the ACL file need this info:
user [YOUR_MQTT_USER]
topic readwrite #
" topic readwrite # " means Read and Write to (#)all topics.
Don’t disable the port. If your are setting up a system that’s only accessible locally it’s fine (and necessary) to use a that port.
It means, No modifications of the configuration.yaml. as the MQTT broker is set via the integrations page in Hass. and in the brokers configuration files and ACL files.
Each of what you commented on makes sense, but the documentation isn’t clear. At this point, I’m trying to get any of my devices to auto-detect through discovery and it’s not happening like it did before I updated hass.io to .98.
So, I haven’t a clue how to get my devices that rely on MQTT to work with HA.
It is. I uninstalled every aspect of MQTT from the front end and am starting from scratch, documenting each step and observing anything out of the ordinary.
