The MQTT client helps test broker connectivity and topic traffic from an Android device. It is useful during IoT development when you need to confirm that a broker, credentials, and topic path work from the client network.
How it works
MQTT uses a broker to route published messages to subscribers. The verified implementation offers MQTT 3.1.1 or 5 options, authentication, TLS, subscribe, and publish workflows.
How to use it in Network Toolkit
- Enter the broker host, port, and MQTT version.
- Configure TLS and authentication to match the broker.
- Connect and subscribe to a narrowly scoped test topic.
- Publish a harmless test message and verify delivery.
What information you can see
- Connection state and broker errors
- Messages received on subscribed topics
- Publish results
- Protocol, TLS, and authentication feedback
Common use cases
- Test an IoT broker from WiFi
- Verify credentials and TLS settings
- Observe a device telemetry topic
- Publish a controlled test command in a lab
Limitations and Android considerations
Related network tools
Port Scanner for Android, Ping Tool for Android, Network Scanner for Android can help confirm the result from another angle.
Frequently asked questions
Which MQTT versions are available?
The current implementation exposes MQTT 3.1.1 and MQTT 5 options.
Why can the TCP port be open while MQTT fails?
The broker can reject the protocol version, client identifier, credentials, TLS settings, or topic permissions.
Is MQTT traffic encrypted?
Only when the connection is configured to use TLS. Plain MQTT does not encrypt message contents.