Devices can't connect to MQTT

Configuration
1

Hi all,

I’ve just migrated my HA server to a Pi. Everything but the MQTT works fine. I’m moving from a windows based MQTT broker to the MQTT addon in HA. It’s installed and running, but when any of my devices try to connect I get this error in the MQTT Addon logs:

1609134525: New connection from 192.168.1.13 on port 1883.
1609134525: Socket error on client , disconnecting.
1609134528: New connection from 192.168.1.19 on port 1883.
1609134528: Socket error on client , disconnecting.
1609134531: New connection from 192.168.1.17 on port 1883.
1609134531: Socket error on client , disconnecting.
1609134536: New connection from 192.168.1.13 on port 1883.
1609134536: Socket error on client , disconnecting.
… etc …

These devices are running Tasmota and connect just fine to my other existing MQTT broker. So I assusme the new Addon broker is the issue.

I can connect to the MQTT server with MQTT Explorer, but nothing is logged in there and even when I publish a test topic, it doesn’t get logged (but maybe because there are no subscribers to it?). There are no tops. Not even the $SYS topics:

image
image923×387 10.5 KB

Here’s my MQTT Config:

logins: []
anonymous: true
customize:
  active: false
  folder: mosquitto
certfile: fullchain.pem
keyfile: privkey.pem
quiet_logs: true
require_certificate: false

I’m happy with anonymous, non secure connections on my local network.

Any idea? I’m not sure what else to try…

2

Maybe try adding a homeassistant user with readwrite access to the ACL file?

3

Thanks, but I’m trying to set up anonymous connections.

I don’t even know what the users are as I have it set up with the Legacy API User. Even then, the Tasmota devices are set up with no user or password. So I can’t imagine what adding users will do…

4

Homeassistant user is the default user if you use MQTT discovery… they get reported to the Broker and HA as that user (in Tasmota anyway) I had issues with MQTT and config before I added that to the ACL. I’m not sure without checking the docs if you need to use ACL file with anonymous user… anyway what you are doing isn’t working…

5

Oh ok it makes a little more sense now. Thanks.

I’ll look it up arms give it a try. So you mean to just add it as an authorised user?

6

Yes exactly that

7

I followed the steps on the instructions and entered the HA user into the addon configuration, but it didn’t help. Still getting the same issue.

I tried installing the deprecated MQTT Server and Web Client addon from HACS and that works. But I don’t think I want to be running long term on a deprecated addon.