Connecting to the MQTT Broker
This section explains:
- The hosts and ports that are available when connecting to the Connectivity Management MQTT broker.
- The credentials to use for authentication purposes.
Host and Port Details
The Connectivity Management MQTT broker supports two different communication protocols. These are MQTTS and WebSocket.
Connectivity Management recommends that MQTTS is used, as it is a standard, encrypted MQTT socket.
The WebSocket host is an un-encrypted WebSocket.
The host and port details for the Connectivity Management MQTT broker are detailed in the table below.
These details should be entered in to your chosen MQTT client in order to establish a connection with the Connectivity Management MQTT broker.
| Protocol | Host | Port |
|---|---|---|
| MQTTS | 8883 | |
| WebSocket | 3000 |
User Authentication
The user credentials for MQTT users vary depending on whether you are logging in as a company level user or as a device level user.
To log in as a company level user, you must provide the following details using your chosen MQTT client:
- Username
For company level users, the username must match the value that was defined when the user was created in Connectivity Management.
- Password
For company level users, the password must match the value that was defined when the user was created in Connectivity Management.
To log in as a device level user, you must provide the following details using your chosen MQTT client:
- Username
For device level users, the username is always use-token-auth.
- Password
For device level users, the password is the token that you were provided by Connectivity Management when the user was created.
On This Page
Pelion
Ground and First Floor
St. Vincent Plaza
319 St. Vincent Street
Glasgow, G2 5LD
Ground and First Floor
St. Vincent Plaza
319 St. Vincent Street
Glasgow, G2 5LD