Frequently asked questions
Everything you need to know about MQTT One, connecting your devices and the integration with iotBind.
General
What is MQTT One?
MQTT One is a cloud MQTT broker for the Internet of Things. It receives messages from your devices and delivers them to every client subscribed to the same topic — reliably and in real time.
Is MQTT One free?
Yes. You can create an account and use the broker for free through the iotBind platform.
Where do I create an account or log in?
Account registration and management are now handled by iotBind. One iotBind account gives you access to both platforms.
I already have an MQTT One account. What happens to it?
Existing accounts are being merged with iotBind. Log in on the iotBind platform to manage your account and brokers. Your existing broker connections keep working as before.
Which devices and languages can I use?
Any device or software that supports MQTT: ESP32, ESP8266, Arduino, Raspberry Pi, Python, Node.js, Java, C#, Go, browsers over WebSocket, mobile apps and command-line tools such as mosquitto.
Which MQTT versions are supported?
MQTT One supports MQTT 3.1 and 3.1.1, which are supported by virtually every MQTT client library.
Connecting
Where do I find my broker address and credentials?
Each project has its own broker address, username, password and topics. You will find them in your project on the iotBind platform.
Which ports can I use?
Port 1883 for MQTT over TCP, 8883 for MQTT over TLS, 8083 for WebSocket and 8084 for secure WebSocket. The WebSocket path is /mqtt.
Can I connect from a web page?
Yes. Use an MQTT library for JavaScript (for example MQTT.js) and connect over secure WebSocket on port 8084 with the path /mqtt.
Why does my client disconnect right after connecting?
The most common causes are wrong credentials, using a topic your user is not allowed to access, or two clients connecting with the same client ID. Use a unique client ID for each device.
What QoS level should I use?
Use QoS 0 for frequent sensor readings where losing one value is acceptable, QoS 1 for most messages, and QoS 2 only when a message must be processed exactly once.
Security
Is my data secure?
Each broker user has its own credentials and access rules that define which topics it may publish or subscribe to. Use TLS (port 8883) or secure WebSocket (port 8084) to encrypt traffic.
Can other users read my messages?
No. Access to topics is controlled per user, so clients can only use the topics they have been granted.
Should I share my broker password?
Never share your credentials publicly or commit them to public code repositories. If you think they were exposed, contact our support team right away.
Still have a question? Our support team is happy to help. Contact support