Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

There are many advantages to setting up a virtual private network of devices that need to be managed remotely. This software-defined network enables:

  • Access to devices no matter where in the world they reside
  • Access to devices for troubleshooting, without on-premise intervention

Using the network's unique Node ID as a secure token, an end-to-end handshake between devices ensures a direct, secure connection.

Configure Cloud Connectivity


This procedure assumes that you already have created a LoopCloud Company and Project. Refer to the following documentation for instructions:

To facilitate this configuration, log in to both LoopCloud and LoopEdge so that you can copy and paste configurations to connect these platforms.

In LoopCloud

  1. Create a LoopEdge Model by selecting the MQTT plain TCP connection. See Create a Device Model.
    Note that the model's JASON schema includes a remote network parameter.

      "mqttHostName": "%MQTT_HOST%",
      "mqttTcpPort": "%MQTT_TCP_PORT%",
      "mqttUserName": "%MQTT_USERNAME%",
      "mqttPassword": "%MQTT_PASSWORD%",
      "mqttClientId": "%MQTT_CLIENT_ID%",
      "mqttReqTopicName": "%MQTT_REQ_TOPIC%",
      "mqttRespTopicName": "%MQTT_RESP_TOPIC%",
      "mqttDataTopicName": "%MQTT_DATA_TOPIC%",
      "remoteNetwork": "%REMOTE_NETWORK%"
  2. From the LoopEdge model, create a LoopEdge Device. See Add a Device from a Model.
  3. In the LoopCloud navigation panel, go to Device Mgmt > Devices to view the newly created device in the list.
  4. In the device's Action list, click Status and select Activate.

  5. In the Activation Code pop-up, click the  icon to copy the code to the clipboard.

    This one-time-only code is valid for only 60 seconds. Be sure to take the following steps in LoopEdge immediately.

In LoopEdge

  1. In the LoopEdge navigation panel, go to System > Device Management.
  2. Under Cloud Activation, paste the activation code that is in the clipboard and click Activate.

    Unable to render {include} The included page could not be found.

    When the activation is complete, a LoopEdge DataHub Cloud Connector automatically gets created. To view the connector, navigate to DataHub.

Configure a Virtual Private Network

When you create a VPN, you can connect LoopEdge, LoopCloud, and devices that exist anywhere in the world. Once configured, you easily can access and securely manage your Loop network, no matter where you are located.


  • Before taking the following steps, be sure to complete the steps listed in: Configure Cloud Connectivity.
  • You will need a VPN service, such as Zero Tier One, to configure your LoopEdge VPN.

To configure this VPN, you will once again need to switch between LoopCloud and LoopEdge. In addition, you will access the VPN remote access service for node IDs.

In the Remote Access (VPN) Service

  1. Copy the network Node ID.
    This unique ID serves as a secure token to enable the Loop platform to join the private network. 

    Example of a Node ID:


In LoopCloud 

  1. In the LoopCloud navigation panel, click Remote.

    Unable to render {include} The included page could not be found.

  2. Click the + icon in the upper right of the window to add a member to the network.
  3. In the Add new member dialog, paste the Node ID that you copied from the remote access service and click Save.

    The node will be listed in the Remote Network list, as part of your virtual private network.

  4. In the Remote Network window, click the  icon to copy the network ID.
    You will use this ID in the remote access service to join the VPN. This establishes the handshake between the VPN and the Loop platform.

In the Remote Access (VPN) Service

  1. In the Remote Access Service, select Join Network and paste the network ID that you copied from LoopCloud.

In LoopEdge

  1. In the LoopEdge navigation panel, expand System and click Remote Access.

  • No labels