-
-
Notifications
You must be signed in to change notification settings - Fork 284
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
constantly and repeatedly disonnecting from emqx broker #180
Comments
This may happen when you use the same MQTT client ID twice on the same broker. (or connect two MQTT Explorer instances at once). I'll check out the compatibility with emqx in the meantime. Thank you for the bug-report. |
I had no trouble conencting to an emqx instance However to see all the traffic you would most likely need to update your ACLs: |
hi, had the same issue, by changing the client ID i could get rid of the message, is the cliend ID is generated randomly ? |
I recently switched from mosquitto to emqx and have been running into this. I think it's because of default configuration on emqx that restricts how many updates a client can receive. I have Home Assistant and a bunch of other software, some of which are using the retain flag on messages or QoS >0. MQTT Explorer seems to have a default subscription of |
First off. I have been using mqtt box for some time and it works just fine with latest emqx broker docker version.
Just saw and decided to give mqtt ex a spin. Running on a linux mint box 19+, 18.04.
The client keeps popping up the
disconnected from server
notification. Not all the topics are showing or are being updated.Seems something amiss with handshaking/keep alive
connection set to mqtt protocol, valid cert off, tls off, no credentials, same as for mqttbox
Let me know how to provide you some logs
There is nothing in the dev tools console.
The text was updated successfully, but these errors were encountered: