chkr1011 / mqttmultimeter Goto Github PK

When connecting to AWS Iot Core, the selected pfx certificate seems to not be used in the TLS options. When I made the following changes to set the cert and applicationProtocols, it started working:
MqttClientService.cs:

        clientOptionsBuilder.WithTls(o =>
        {
            o.SslProtocol = item.ServerOptions.SelectedTlsVersion.Value;
            o.IgnoreCertificateChainErrors = item.ServerOptions.IgnoreCertificateErrors;
            o.IgnoreCertificateRevocationErrors = item.ServerOptions.IgnoreCertificateErrors;
            o.CertificateValidationHandler = item.ServerOptions.IgnoreCertificateErrors ? _ => true : null;

            **if (!string.IsNullOrEmpty(item.SessionOptions.CertificatePath))
            {
                X509Certificate2Collection certificates = new()
                {
                    new X509Certificate2(item.SessionOptions.CertificatePath)
                };

                o.Certificates = certificates;
                o.ApplicationProtocols = new List<SslApplicationProtocol>() { new("mqtt") };
            }**
        });

just showing exception

When I copy this text, and paste it elsewhere, the text is correct

Version Info

I wanna subscribe on "$SYS, $SYS/broker" for example. Is it possible to listen all topics at the same time?

is there any option to access the mqtt broker by ACCESS_TOKEN?

example : I'm using to following command to publish message for my mqtt broker
mosquitto_pub -d -q 1 -h "$HOST_NAME" -p "1883" -t "temperature/sensor" -u "$ACCESS_TOKEN" -m {"temperature":25}

Order of my actions:

1. connect to my host
2. subscribe to topics
3. leave the computer for 10 minutes
4. after 10 minutes, the connection is terminated

if I use the app, the connection will never terminated

Hello,
thank you for this great app.
I am using the MQTTnetApp to send test messages to an application I am developing. It is great that the topics and their settings are saved and restored when restarting the MQTTnetApp. However, the payload is not restored and always clean after restart. Is this on purpose? Would it be possible to save and restore the payload as well?
Best regards, Philip

Hi.

This is not a real issue, but I just wanted to say thanks for that app 👍 .

I wanted a GUI that make easy to send and receive MQTT messages and your app just do that perfectly. Before that I used MQTTBox but when sending a few hundred messages in a few milliseconds it become really slow while your app remain responsive.

So thanks a lot for this.

Hello, is it possible to add a function that would allow to use a non-valid certificate ( self signed ) on a checkbox?

executable from v1.7.0.211 mqttMultimeter-linux-x64.zip

176M 2023-04-30 10:22 mqttMultimeter

file says not stripped, but after strip it'll broken.

$ file ./mqttMultimeter
./mqttMultimeter: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=8c843397ceec509a72a2b2394d574f5822bb3aad, not stripped, too many notes (256)

$ strip ./mqttMultimeter

$ ./mqttMultimeter
Failure processing application bundle; possible file corruption.
Arithmetic overflow while reading bundle.
A fatal error occurred while processing application bundle

The connection is closed if a large amount of data gets into the listbox.
You can check it by entering this data in the options: host: test.mosquitto.org port: 1883

Official mqtt-client supports only mqtt3. Does your app support mqtt5?

The "gold standard" for mqtt GUI clients (IMHO) is MQTT-Explorer which sadly is no longer actively maintained.

It has a tree-view as an alternative to the "inflight" panel in mqttnetapp, which is very useful.

It would be awesome to have something like this here as well.

I saved an export of mqtt_inflight and then when I imported it I saw nothing. I looked at the file contents and the data is all there. So it should work but the inflight viewer shows nothing. I am not sure if I am using it incorrectly or if the feature just doesn't work.

When selecting 'websocket' as the transport, the port field has no effect, since the host field effectively becomes an 'address field' where you specify the host, port and path all in one. This wasn't immediately obvious to me as a new user, until after some trial and error.

As a suggestion, when the user selects the websocket transport, could the UI disable the port field, and change the host field's label to say 'address'?

Is it possible to add TreeView which is loaded dynamically instead of ReceivedApplicationMessages?
I think that list of messages in ListBox is a bad idea, it's uncomfortable to work with it

`

When the authentication fails and you open the stacktrace window (If the error is large), the stacktrace window overlays the "Copy to clipboard" and "Ok" buttons.

If you close the stacktrace window again, the buttons are displyed again.

Not really a big thing, but this could be a bit nicer, I guess :D

Would like the app to support x509 certificate based authentication. Thanks.

I had the same issue. Ok, now we have an opportunity to subscribe to several topics. But now I would like to subscribe to all topics only by one click. Is it possible to do?

I'm not sure if this already works, but it would be nice to have the option to export / import the connection settings (E.g. as a JSON structure). This would make it more easy if you want to share connections with a colleague, etc.

Hi, I was wondering if I can use the app as documentation tool so I can share my saved entries and have it loaded to another person's application instance.

Thanks in advance

Hello, just starting with MQTTnet library. So was wondering if you have published any pre built binaries for Windows or linux anywhere? Or its just source and we have to figure out how to build in our favorite OS?

Currently, we get a directory named $HOME/.MQTTnetApp i which the various configuration files are written.

It would be great to follow the XDG Base Directory Specification https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html so as to not pollute $HOME.

Secondly, the casing is rather annoying on a case-sensitive file system where application directories are typically kept lower case. bash as an example will not auto-complete that out-of-the-box unless you get the casing right when typing the first letters.