Skip to end of metadata
Go to start of metadata

What is the Advantage of Configuring LoopCloud Connectivity?

The LoopCloud platform seamlessly integrates with LoopEdge to provide a centralized view of the devices from which data is collected. A LoopEdge DataHub Cloud Connector facilitates the communication from LoopEdge to LoopCloud. See also, DataHub Overview.

LoopEdge is a client for LoopCloud, but any device (or even a script) that is able to send data via MQTT/LWM2M/HTTP can be used with LoopCloud. Poll devices, which request data from http (SOAP/REST) services, are also supported.

Note that you do not need LoopCloud to collect data from a device and to visualize the data. This can be accomplished in LoopEdge using DeviceHub and LoopFlows. However, there are significant benefits to taking advantage of the built-in compatibility of the two Litmus Automation products. LoopCloud offers a flexible device and data management platform that enables you to securely connect and manage any type of hardware, device, sensor or machine, while providing extensive control at scale for all your IoT projects and deployments. LoopEdge's edge-level data collection from IoT devices/systems, combined with LoopCloud's granular control and flexibility, expedite IoT deployments.


Before a LoopEdge DataHub Cloud Connector can be configured, a model and device must be created in LoopCloud, as described in the following procedure.

Configure a LoopCloud Model and Device

To set up LoopCloud to connect with LoopEdge:

  1. In LoopCloud, create a LoopEdge model, as described in Create a Device Model.

    For the purpose of this exercise, configure the model for both MQTT Plain TCP and LWM2M connections.

  2. Add a device based on the LoopEdge model you just created, as described in Add a Device From a Model.

  3. Save the JSON file that is created and downloaded when the device is added to LoopCloud.

    This JSON file contains the configuration parameters to communicate with LoopEdge. You will upload this JSON file when you configure a LoopEdge Cloud Connector.

    Example Device JSON File

    "mqttHostName": "",
    "mqttTcpPort": "1883",
    "mqttUserName": "7c7cfjfiqci6up5w5sbjua72a",
    "mqttPassword": "ig9strug01ag9v3mdi6l77vi76",
    "mqttClientId": "7c7cfjfiqci6up5w5sbjua72a",
    "mqttReqTopicName": "loop/req/7c7cfjfiqci6up5w5sbjua72a/1vx9e4aytou07is705bux9psn/json",
    "mqttRespTopicName": "loop/resp/7c7cfjfiqci6up5w5sbjua72a/1vx9e4aytou07is705bux9psn/json",
    "mqttDataTopicName": "loop/data/7c7cfjfiqci6up5w5sbjua72a/1vx9e4aytou07is705bux9psn/json",
    "remoteNetwork": "8bd5124fd66cd1c3",
    "lwm2mHostName": "",
    "lwm2mPortNoSec": "5683",
    "lwm2mEndpoint": "8e1a66fc69c366c69136",
    "deviceId": "7c7cfjfiqci6up5w5sbjua72a"

    Note that the JSON file contains parameters required by LoopEdge to make the connection, for example, hostname, username, password, and MQTT topics.

Configure LoopEdge Cloud Components

Once you have configured LoopCloud, as described above, continue making the necessary corresponding connections on the LoopEdge side.

Proceed to the following procedures to complete the configuration.