You can also use MQTT Client Tool - MQTTX as another client for the message publishing and receiving the test. If you subscribe the “Csharp/mqtt" topic in MQTTX, you will receive the message every second. - Source: dev.to / 7 months ago

Then, their MQTTX client, implemented in Electron, supports all platforms, just download and use. - Source: dev.to / about 1 year ago

This section will introduce how to use Neuron to collect data from FINS TCP devices, upload the collected data to EMQX, and view it using MQTTX. - Source: dev.to / over 1 year ago

Next, we open MQTTX, create a new connection, copy the JWT output when JWKS Endpoint starts to the Password field, and click Connect in the upper right corner to connect. - Source: dev.to / almost 2 years ago

Again, we can use MQTTX or any other MQTT client to publish MQTT data to the demo/sensor topic. Those data will be processed by the rule. For example, we publish the following data to the topic with a 30 seconds interval, and the two minutes data is like this:. - Source: dev.to / almost 2 years ago

Sounds like you're on a good path tracking the problem to aws, not the esp. First of all, I'd try to make it work with a "proven" solution, then move on to your own implementation. I have had good success using http://mqtt-explorer.com/ on windows to diagnose a similar situation. Mqtt explorer gives you very granular control over endpoints and topics, so might be helpful to you too. Source: about 2 years ago

I would suggest using Mqtt explorer (http://mqtt-explorer.com/) to see how often the sensor updates its values. This as a first step to narrow down the problem. Source: about 2 years ago

Use MQTT Explorer to view and generate messages: http://mqtt-explorer.com/. Source: about 2 years ago

You can write test programs to send very specific messages to simulate errors, or simulate entire components that aren't written yet. There are also free programs like MQTT Explorer that will let you browse the message traffic, generate messages manually, log whatever you cant, and even graph your values if you happen to send numerical values (that is really cool when you do some long-term testing). Source: over 2 years ago

To use a local server can let you control all details of your full messaging chain. Try other clients can make you away from the ill behaviors or bugs of specific client. I recently demonstrate how easy a free MQTT client (MQTT explorer) send to a free MQTT database on Windows 10 in my video. Source: over 2 years ago