...
After the device is configured with an MQTT client and connected to the MQTT bridge, it can publish a telemetry event by issuing a PUBLISH message to an MQTT topic in the following this format:
| Code Block |
|---|
/devices/DEVICE_ID/events |
...
Messages are forwarded to the default Cloud Pub/Sub topic instead of the additional Cloud Pub/Sub topic in the following these cases:
No subfolder is specified in the MQTT topic
A subfolder is specified in the MQTT topic but doesn't have a matching device registry’s Pub/Sub topic
...
The ClearBlade MQTT broker honors the following these MQTT 3.1.1 error codes.:
Value | Return Code Response | Description |
|---|---|---|
0 | 0x00 Connection Accepted | Connection accepted |
1 | 0x01 Connection Refused, unacceptable protocol version | The server does not support the MQTT protocol level requested by the client |
2 | 0x02 Connection Refused, identifier rejected | The client identifier is correct (UTF-8) but unallowed by the server. This can be caused by a duplicate |
3 | 0x03 Connection Refused, Server unavailable | The network connection has been made but the MQTT service is unavailable |
4 | 0x04 Connection Refused, bad user name or password | The data in the user name or password is malformed |
5 | 0x05 | Unused by IoT Core |
13 | 0x13 | All other events for connect, disconnect, publish, and subscribe |
...