Mbed Service Quickstart Guide

Follow

Quoted from ARM’s website, “The ARM® mbed™ Device Connector service lets you connect Internet of Things (IoT) devices to the cloud without having to build infrastructure, while providing security, simplicity and capacity required by developers to prove IoT applications at scale.” For more information, please refer to https://connector.mbed.com/.

Murano mbed service provides a way to connect your mbed connector accounts to Murano applications. It enables Murano application developers to access device data and device status within Murano via the Murano mbed service.

With Murano mbed service, Murano application developers can connect an mbed connector to Murano, and have their mbed devices mirrored in Murano’s Advanced Device Connectivity (ADC). This will allow mbed device data and events such as device registration/unregistration to be visible within Murano. With this association, you can use Murano’s feature-rich services to build your IoT solutions with mbed devices.

Requirements

  • have an mbed account
  • have access to Murano mbed service. (Hint: only a professional-above tier business is able to purchase mbed service through the Exchange UI)

Getting Started

There are several steps required for initializing this service.

Step 1: Create an application

Create an application in your Murano business. Instructions for creating an application can be found at http://docs.exosite.com/reference/ui/create-application/.

 

Step 2: Create and configure a product

Create a product in the same Murano business. Instructions for creating a product can be found at http://docs.exosite.com/reference/ui/create-product/.

  • Configure your product
    • Choose CIK (Client Identification Key) as the authentication method for Https Data Api
    • Configure Device Identity Format to match the format of an endpoint name from mBed Connector (e.g. prefix = “”, type = Opaque, required length = 36)

image14.png

image15.png

  • Create Resource
    • Navigate to the “Resources” tab within the product.
    • Click “+New Resource” button and fill in Alias as defined in mbed Resource Path but replace  ‘/’ with ‘_’; for example, resource path: “/Test/0” → resource alias: ‘_Test_0’
    • Select “String” as “Data format”, since the data are reported as String from mbed
    • Please note that the following image is only shown when there is a device connected to the mbed account.

image13.png

image8.png

Step 3 Subscribe/Add Mbed service in Exchange for your application

After the application and product have been created. You can now subscribe to Murano mbed service. For more information on how Murano Exchange works, please refer to http://docs.exosite.com/reference/ui/exchange-guide/.

 

Step 4 Configure your mbed service.

In service config tab, fill in API Key, Product ID, endpoint type. Make sure you have your working API Key

  • Step 4.1 Go to the mbed service under service config page of your own solution
    • Step 4.1.1 Go to your own application-type solution

image5.png

    • Step 4.1.2 Click “SERVICES” tab and then click “Mbed” at left services navigator

image10.png

  • Step 4.2 Fill in (1)Product ID (2)API key (3)Endpoint Type as parameters for the mbed service (Note: the match-all star sign (*) doesn’t work for endpoint type, must input a specific type like in Step 4.2.3)

image11.png

    • Step 4.2.1 To fill the value for parameter(1)Product ID, please refer to the following screenshots:

image17.png

    • Step 4.2.2 To fill the value for parameter(2)API key , please refer to the following screenshot:

image4.png

    • Step 4.2.3 To fill the value for parameter(3)Endpoint Type, please refer to the following screenshot:

image2.png

  • Step 4.3 Click “APPLY” button and you should see “Service config updated successfully” message

image3.png

Step 5 Verify

  • Step 5-A. Check if new device is created
    • Go to  Device page, and you will see the device, which has been successfully created and provisioned.

image16.png

  • Step 5-B. Check if data is reporting
    • Click the device, and you will see the resource value, which has been updated

image6.png

  • Step 5-C. Check if mbed devices are listed by endpoint/route verification
    • Step 5-C-1 - Associate application with product 
      • 1 - Entry the application-type solution page
      • 2 - Click “SERVICES” tab
      • 3 - Click “Products” at left services navigator
      • 4 - Check the checkbox next to the applicable product
      • 5 - Type “Mbed20170911”(for example) as script alias next to the “EDIT SCRIPT”
      • image18.png
        • Note: “Mbed” on it's own cannot be used as the Lua Script Alias
      • 6 - Click “Apply” button
      • 7 - After you see the “Products updated successfully” message on Snackbar, you have associated application with product successfully

image1.png 

    • Step 5-C-2 - Check if mbed devices are listed by calling device2.listIdentities() in endpoint
      • 1 - Click “ROUTES” tab under application page
      • 2 - Click “+ NEW ENDPOINT”  image9.png
      • 3 - At the “New Route” pop-up, type mbed/devices(for example) in path field , and click “CREATE” button                                                  image7.png
      • 4 - Entry the new created endpoint and write down the Lua code as below:

return Mbed20170911.listIdentities()

Note: To successfully use device2 public API, the alias device2 must be substituted with script alias created in Step 1.5(which is Mbed20170911 as example here); further information about device2 APIs, please refer to: http://docs.exosite.com/reference/services/device2

      • 5 - Click the link for AUTO-GENERATED DOCS
      • 6 - Click the “Try” for mbed/devices route
      • 7 - Should see all the mbed devices

image12.png

Have more questions? Submit a request

Comments