mosquitto VS MQTT Explorer

Mosquitto_transport, an experiment of writing SObjectizer-based wrapper around mosquitto library;. - Source: dev.to / 9 days ago

References: Felipe Flop’s website https://www.filipeflop.com/blog/controle-monitoramento-iot-nodemcu-e-mqtt/ accessed on 01/27/2018. Eclipse server for MQTT Broker https://iot.eclipse.org/ accessed on 01/27/2018. Mosquitto https://mosquitto.org/ accessed on 01/27/2018. Cloud MQTT https://www.cloudmqtt.com/ accessed on 01/27/2018. DuckDNS https://www.duckdns.org/ accessed on 01/27/2018. Proftpd... - Source: dev.to / 4 months ago

This is a perfect use case for MQTT, e.g. This library for ESP boards. Create a broker on the network (e.g. a Raspberry Pi running Mosquitto, and have all the ESP boards subscribe to a topic. When you want to play a sound, publish a message to the topic, and all of the ESPs should see it very quickly. You don't need to synchronize clocks any more because it's simply based on the timing of publishing a message. Source: 5 months ago

Optional: Mosquitto, an open-source message broker that implements the MQTT protocol; this tutorial uses the public test server. - Source: dev.to / 7 months ago

I think he means implementation of MQTT protocol, like https://mosquitto.org/. - Source: Hacker News / 9 months 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: 12 months 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 1 year ago

Use MQTT Explorer to view and generate messages: http://mqtt-explorer.com/. Source: about 1 year 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 1 year 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 1 year ago