Mosquitto 5.1.1add-on is broken

Third party integrations
21

I think I have a path to overcome the problem. I used the following procedure to get 5.1.1 working for me.

  1. Take a snapshot (complete) from your current home assistant instance
  2. go to the mosquitto add-on page and copy your configuration into an text editor for later use.
  3. deinstall the mosquitto add-on
  4. install mosquitto 5.1.1 and copy the configuration back from the editor
  5. start the add-on

This solved the problem in my installation

22

Could you please post that on the github issue too?

23

already done. Infact I posted it first on github

1 Like
24

I can’t feel it helped me - the 5.1.1 version is still much slower than 5.1 for me. Reverted back to 5.1.

I just cannot understand that could possible be the problem…

25

I experienced the same with 5.1.1 installed from scratch. No disconnections but everything seemed slower and got a lot of log messages “No ACK from MQTT server in 10”. Went back to 5.1 and working fine since.

27

Yeah this works! thank you

28

What works? You didn’t say who you were replying to.

30

@nickrout is there anything we can do to help track this problem? I have updated to latest home assistant version 2021.04.3 and thought about upgrading mosquitto add-on to 5.1.1. As soon as I did the “No ACK from MQTT server” messages came back.

1 Like
31

Post to the github issue, with logs and full details of what system you are running.

32

I noticed MQTT is now on 6.0.1.I figure I would update from 5.1 and see if there would be no issue. While HA seems to be working as it should. I noticed in t he supervisor log of this warning. Anyone knows how to fix it?

2021-05-25_8-44-57
2021-05-25_8-44-571267×433 271 KB

MQTT config:

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

The warning is caused by the update to the mosquitto addon, it no longer supports anonymous, and you should remove that option.

1 Like
34

ok. Thanks for the heads up.

35

I changed my post as I though you were talking about another error. Remove anonymous: false