**“MQTT 4.1 for DUMMIES”** Needed badly!

Configuration
21

and where do I put those instructions

22

Into the terminal commandline on any machine on your lan (after installing mosquitt_pub and _sub of course)

23

You may want to go straight for MQTT v5.0:

https://mqtt.org/

24

Yes well hassio restricts you to using the version that the addon author provides. Or write your own addon I guess.

25

Although if you aren’t sitting at a linux machine that could be tricky. mqtt.fx is a good windows mqtt client.

26

That’s not what I meant.

You have no local user defined in the broker. That means the MQTT auth is done with a Home Assistant User. So that user has to exist, has to be in the ACL file and has to be used in every devices mqtt username and password.

27

Is that the username that I use to login to Tasmota on each sonoff???

28

no… that’s just the web interface. It’s on the MQTT settings page

29

This one User (DVES_USER)

30

ok so how is that supposed to authorise with the broker?

31

“User (DVES_USER)” is the line where I add the username(123mqtt) that the sonoff uses to connect to MQTT

32

and a password I hope and that matches the HA username and password?
What settings do you have in the broker?

33 
{
  "logins": [],
  "anonymous": false,
  "quiet_logs": true,
  "customize": {
    "active": true,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}
34

I also removed the MQTT section in configuration.yaml

35

ok that looks ok to me. Are you using MQTT discovery? Do you have an MQTT Integration?

36

yes for integrations, and no for discovery.

37

so you are manually configuring the switches/devices? And I presume still not working?

38

yes, and they all worked fine, under MQTT 4.0

39

Have you checked with mosquitto_sub or mqtt.fx or some other client that you can access the server?

40

@nickrout working on getting the tools setup on my linux box…