Mosquitto: Testing with mosquitto_pub and mosquitto_sub

This documentation is part of the Getting Started guide. You can view the complete guide here: How to Begin with Mosquitto.

👋 Welcome to the Stackhero documentation!

Stackhero provides you with a fully managed Mosquitto MQTT cloud environment, designed for reliability and flexibility:

• Unlimited message throughput and data transfers, so your workflows never encounter artificial limits.
• Unlimited device authentication via your own external API, making onboarding and access management straightforward.
• Advanced ACLs for precise control over topics, users, and actions.
• A custom domain name with integrated HTTPS for secure, branded endpoints (for example: https://mqtt.your-company.com).
• Effortless updates: apply improvements or security patches with a single click.
• Consistent performance and enhanced security, with every instance running on a private, dedicated infrastructure.

Accelerate your IoT projects and reduce operational overhead. You can have a secure, production-ready Mosquitto MQTT cloud hosting instance up and running in just a few minutes.

The mosquitto_pub and mosquitto_sub CLI tools are excellent for testing MQTT setups. Before using them, ensure that the "Allow clear connections" option is disabled in your Mosquitto configuration on the Stackhero dashboard.

Here is how you can test:

1. Subscribe to all topics using the # wildcard:

   mosquitto_sub -L -d "mqtts://admin:<PASSWORD>@<XXXXXX>.stackhero-network.com:<PORT_TLS>/#"
   

2. Open another terminal to publish a message to a topic:

   mosquitto_pub -L -d "mqtts://admin:<PASSWORD>@<XXXXXX>.stackhero-network.com:<PORT_TLS>/sensor/a" -m "It works"
   

In the first console, you should see the published message along with debug logs enabled by the -d flag.