Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Install an MQTT client on your device.

  2. Download an MQTT server certificate onto your device.

  3. Configure the MQTT client to authenticate the device to ClearBlade IoT Core.

  4. Initiate a TLS handshake over mqtt.googleapis.com the appropriate MQTT regional URL or a long-term support domain.

  5. Publish telemetry events or set the device state.

...

If port 8883 is blocked by your firewall, you can also use port 443: mqtt.googleapis.com:443.Note: If you are using Private Google Access with the default domains, port 8883 is not reachable. Use port 443 instead. If you are using private.googleapis.com or restricted.googleapis.com, including using Private Google Access for on-premises hosts, MQTT is not supported.

Note: The MQTT standard is defined for implementing a full publish/subscribe broker. However, the managed MQTT bridge run by ClearBlade IoT Core does not support all publish/subscribe operations, such as creating arbitrary topics that devices can use to send messages between them. (Filtering can be accomplished with downstream processes running on Cloud Pub/Sub.) ClearBlade IoT Core uses a predefined set of topics and specific topic formats.

...