Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anonymous login not working in MQTT addon v3 #446

Closed
wroadd opened this issue Nov 6, 2018 · 9 comments
Closed

Anonymous login not working in MQTT addon v3 #446

wroadd opened this issue Nov 6, 2018 · 9 comments
Labels

Comments

@wroadd
Copy link

wroadd commented Nov 6, 2018

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.

@wroadd
Copy link
Author

wroadd commented Nov 6, 2018

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

@SiliconAvatar
Copy link
Contributor

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.

@pvizeli
Copy link
Member

pvizeli commented Nov 9, 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?

@SiliconAvatar
Copy link
Contributor

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?

@pacaj2am
Copy link

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.

@riston
Copy link

riston commented Feb 16, 2019

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

@stale
Copy link

stale bot commented Apr 17, 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.

@stale stale bot added the wontfix label Apr 17, 2019
@stale stale bot closed this as completed Apr 24, 2019
@marc-gist
Copy link

Anonymous still looks to be non-functioning :(

@joekob
Copy link

joekob commented Dec 29, 2020

Hi marc-gist,
I have the same issue, that my anonymous logins to mosquitto server are not working. Did you find some solution for you issue?
BR, Joe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants