MQTT broker addon (Error message...disconnected, not authorized); Logs attached. How do I fix?

Configuration
,
1

Hello everyone,

Could someone help me figure out how to get these errors to stop in the mosquitto broker logs. I noticed that one of my falcon pi player lights wasn’t working properly and when I went to its internal url. There was an error message saying it was disconnected from mqtt. Below are the error messages I found in the mosquitto broker addon logs.

Looking at my broker, it looks like I haven’t created any users, which based on my reading is proper for home assistant. (so I have nothing in the “logins” section of mosquitto broker.)

When I’m looking in mqtt integration. It looks like I have used “mqtt” as user and it looks like I never changed the original password. I don’t know if this ok or not.

The thing that has me most confused about all of this is this setup worked for years and stopped probably within 6 months of now.

Also, I have a zwave device (zwave outlet that I use to help with knowing when laundry is ready to be moved to dryer) that is still properly communicating with mqtt properly through some of my manual yaml setup.–> I think this is much different than my issues being talked about here though because it looks like the things showing up in the logs below are actual physical devices (fpp device and wled device) that aren’t being allowed to talk to the broker.

How do I go about making the broker happy and allow the connections below to occur.

EDIT:
I’m reading the external ip shown below is something about “watchdog” so I guess I don’t worry about that one?

025-02-14 10:08:04: Client FPP_4172 disconnected, not authorised.
2025-02-14 10:08:07: New connection from 192.168.1.250:44760 on port 1883.

2025-02-14 10:09:53: New connection from 192.168.1.54:56902 on port 1883.
2025-02-14 10:09:53: Client WLED-6b7e24 disconnected, not authorised.

2025-02-14 10:06:01: New connection from 172.30.32.1:58718 on port 1883.
error: received null username or password for unpwd check

2025-02-14 10:06:06: New connection from 192.168.1.112:55724 on port 1883.
error: received null username or password for unpwd check
______________
2025-02-14 10:06:16: Client 6cac2c46 disconnected, not authorised.
2025-02-14 10:06:17: New connection from 172.30.32.2:46124 on port 1883.
2025-02-14 10:06:17: Client <unknown> closed its connection.
2

That is the watchdog

3

Thank you. I was thinking so.

Do you have any ideas on the issue with the other devices being shown? I don’t really even know what to look for/ at.

4

Hello Weston,

Here’s what I do… I add logins in the Add-on for MQTT. I use !secrets because I youtube and want to prevent leaks, but you can put clear text there if you like.

image
image466×280 22.2 KB

Then if I have another Add-on that needs to sign into MQTT like Z2M, I use the same !secrets.

5

Thank you for this information.

I ended up finding out that I apparently had changed my Mqtt password at some point so all of the client Mqtt devices were using the wrong password. Luckily, for once. An easy fix after racking my brain :upside_down_face: