emqx / mqttx Goto Github PK

Many constrained devices which use MQTT, use a binary message format. It would be great if it is possible to display the received content as hex values.

I have installed MQTTX 1.1.1 by snap file, but when i try to run it i get:

"The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /snap/mqttx/x1/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)"

And, after try to:

sudo chmod 4755 /snap/mqttx/x1/chrome-sandbox

i get these same message. Can you help-me?

"To run MQTT Broker locally, EMQ X is recommended. EMQ X is a fully open source, highly scalable, highly available distributed MQTT 5.0 messaging broker for IoT, M2M and mobile applications."

For example:

EMQ X, HiveMQ, Mosquitto and more, or you can input null.

To display the status of your Broker.

It would be nice if I could delete a connection just by right click on the connection name listed in the Connections bar, and select delete button in the pop-up menu.

Or is it better also allow the user to delete a connection by left slide the connection name? (for Mac OSX only)

Connect Timeout (ms) -> Connect Timeout (s)

The default timeout should be 10 or 15 seconds

Connecting to m20.cloudmqtt.com:22703 over TLS the client reports

Error: certificate has expired

How can I verify that? How can I load the certificate to verify the chain? I would like to see for myself before reporting this to the cloud provider.

Need to be able to adjust the height of the send payload input box by yourself. The current height can display too little text. And it seems that it is not possible to send a message using Ctrl + Enter, which is inconvenient.

IP Address -> Host
IP 地址 -> 服务器地址

Now if the payload is JSON, it still displays plaintext. I hope it can support JSON display. It is better if it can support more types, such as base64, msgpack, protobuf, etc.

With MQTTX V3.1, SSL server certificate authentication is turned on.If the CA certificate is not valid, it can be successfully connected by importing any certificate.It is the same as the emqx server, and the CA certificate can be normally certified under MQTT.fx

1、It's very slow on Windows 7
2、The subscription option is turned off without reason

To connect to a broker that is configured with a self-signed server certificate, client cert and key are not mandatory. MQTTX is assuming that the SSL connection is mutual. The broker could be configured for only one-sided (client-side) SSL and use username and password based authentication instead of cert based authentication.

It seems there's no way to send an empty publish always in plaintext mode.
Can be removed the check that require at least a char to publish on a topic?

Topic can be copied quickly

• left bar
• right content

The message list view is divided according to the subscription relationship. Now all the messages of the subscription are in the same view. If there are multiple subscriptions, it will be very inconvenient to view. You can consider putting the messages of different subscriptions in different message views.

I've deployed EMQ server behind Nginx, and use 80 for WS connection and 443 for WSS. I can connect to server in web pages using Javascript client, but can not connect with MQTTX, no matter via 80 or 443. As the port is required, I can't leave it blank neither. So is it possible to make it optional? Thanks.