Addons: Anonymous login not working in MQTT addon v3

Created on 6 Nov 2018 · 9Comments · Source: home-assistant/addons

After upgrade MQTT addon to v3 and Hassio to 0.81.6, the anonymous login is not working even if I change the "anonymous" : false to true.

wontfix

Source

wroadd

Most helpful comment

Hi, seems "anonymous": true, works, if you see: ACL denying access to client with dangerous client id "mosqsub/13224-subsonic" it is complainig about client id, where should be no slash.

pacaj2am on 28 Nov 2018

👍2

All 9 comments

There is some error report in HA forum:
https://community.home-assistant.io/t/mosquito-mqtt-update-v3-broke-my-hassio/76991/51

wroadd on 6 Nov 2018

👍1

Same issue here.

I have numerous MQTT devices, all on a segregated internal network. I do not want to have the MQTT server be password protected or governed by an access control list of any kind.

After this update, setting "anonymous" : true has no effect, and devices seem to REQUIRE a username/pass to be in the ACL before it allows access to the broker.

SiliconAvatar on 8 Nov 2018

ACL are currently by pass. I have no issue here with anonymous. Do you have save the config and press restart after the change on the add-on?

pvizeli on 9 Nov 2018

ACL are currently by pass. I have no issue here with anonymous. Do you have save the config and press restart after the change on the add-on?

Yes.
My configuration is:

"logins": [],
"anonymous": true,

I've restarted the add-on plenty of times and also have since upgraded to v4.
And still I get these errors:

1541828382: New connection from 192.168.1.220 on port 1883.
[ERROR] Auth error with DVES_USER
1541828382: Socket error on client , disconnecting.

I'm sure the client might be trying to say it has a user, but I don't care, and neither should the broker. In version 2 this was simply not an issue. I did not have any ACL defined, and anonymous was set to true and it "just worked". This is all in an internal segregated network, I do not want any type of authentication.

V3 and V4 appear have a much more strict definition of what "anonymous" means, so how do I make this new version functionally equivalent to V2?

SiliconAvatar on 10 Nov 2018

Hi, seems "anonymous": true, works, if you see: ACL denying access to client with dangerous client id "mosqsub/13224-subsonic" it is complainig about client id, where should be no slash.

pacaj2am on 28 Nov 2018

👍2

Yes changing "anonymous": true works, but what would be a proper fix to change the client id naming schema?

riston on 16 Feb 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.