MQTT Broker connection failure

[doubledutch]

I can’t connect to my mqtt broker anymore. Seen various posts on this topic but none seem to be what I am experiencing so adding a new one. My log shows and I’ve re-installed the broker with no success. I’m using mqttexplorer to connect but other tools fail as wel.

My configuration is below and I’m using a standard HA user, specially configured for this purpose that used to work. Any thoughts would be greatly appreciated

[FloatingBoater (James Derrick)]

The best test is a manual MQTT client like https://mqtt-explorer.com/

A walk-through of Mosquitto MQTT server settings may help (note the use of a seperate user configured in the Mosquitto Add-On Configuration tab to avoid HASS credential issues which can fail):

Sonoff Tasmota fails to connect to MQTT

Hi, I’d start with a clean slate - re-flash the device (or Tasmota → Configuration → Reset Device), and delete the Mosquitto Add-on and reinstall. HASS Mosquitto broker Add-In, MQTT integration, Tasmota Integration Mosquitto broker Add-In The recommended way to configure uses is shown on the Add-On Documentation tab - e.g. create a HASS user. http://homeassistant.local:8123/hassio/addon/core_mosquitto/documentation I personally use additional Mosquitto users, BUT these are configured not b…

Could you be using IPv6?
I’ve seen disconnections for no obvious reason before as HASS used to only support IPv4 but that was a slightly different error:

Word of warning - Mosquitto add-in only supports IPv4, throws `Socket error on client` with IPv6

Hi, I thought it might help someone to flag a slightly obscure issue with Mosquitto running as an add-on. After several hours of debug, head-scratching and reading docs, forum posts, etc, I’ve reported an issue that the Mosquitto MQTT broker integration works with IPv4, fails with IPv6. If you are seeing lots of Socket error on client <unknown>, disconnecting. errors in the Mosquitto add-in log file, it may be worth checking if you are connecting via IPv4 or IPv6 (hint: set clients to use the…

If this helps, this post!

[doubledutch]

Thanks @FloatingBoater.

I use mqtt-explorer which fails in the same way the mqtt add-on does I also use a separate user and I don’t use IPv6 so I think I covered all your basis. But it still doesn’t work

[FloatingBoater (James Derrick)]

Best I can suggest is a web search for the Client <unknown> disconnected due to protocol error. text, but I bet that’s the first thing you tried!

My working broker shows lots of Client <unknown> disconnected type logs, so that’s not the issue.

Can you try a telnet -4 test to check the network layer?

Protocol error and Opening ipv6 listen socket still makes me wonder if your client has started to support IPv6, but that’s still a rather long shot (a Linux client switched to IPv6 DNS automatically, which caused my second linked issue - I changed nothing other than kernel patches).

[NavNav]

Remove port 1883 and 1884 in your setting and see if that will work. I see my settings are blank for that 2 ports.

[doubledutch]

I sorted it out - long story but the RPI had lan and wifi connections, the wifi IP address stopped working so I needed to move the MQTT settings to use the LAN IP address instead. Changed that and it all works.

So basically: it’s just me being stupid! Thanks for your help