Quoted from ARM’s website, "Extend the reach of your cloud all the way to any IoT device. Mbed Cloud is the first complete chip-to-cloud solution, built for fast IoT deployment. You don't need to recruit a team of experts in every aspect of security, network stacks or technology standards before you can see benefits. Simply take advantage of the industry's largest ecosystem, saving on months of development costs." For more information, please refer to https://cloud.mbed.com/.
Murano mbed service provides a way to connect your mbed cloud 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 cloud to Murano, and have their mbed devices mirrored in Murano’s device gateway. 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.
Also have a look to the Mbed Service reference.
Have an mbed cloud account
Have access to Murano mbed service. (Hint: only a professional-above tier business is able to purchase mbed service through the Exchange UI)
There are several steps required for initializing this service.
Create an application
Create an application in your Murano business. Instructions for creating an application can be found here.
Create and configure a product
Create a product in the same Murano business. Instructions for creating a product can be found here.
Configure your product
Configure Device Identity Format to match the format of an endpoint name from mbed Cloud-Connector (e.g. prefix = "", type = Opaque, required length = 36)
Choose CIK (Client Identification Key) as the authentication method for HTTP Device API
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’
Note: the following image is only shown when there is a device connected to the mbed cloud account.
Select "String" as "Data format", since the data are reported as String from mbed
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 The Exchange Overview page.
Configure your mbed service.
In service config tab, fill in API Key, Product ID, endpoint type. Make sure you have your working API Key
Go to the mbed service under service config page of your own solution
Go to your own application-type solution
Click "Services" tab and then click "Mbed" at left services navigator
Enter 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 e.g. default
Enter the value for parameter (1) Product ID, please refer to the following screenshots:
Enter the value for parameter (2) API key, please refer to the following screenshot:
Enter the value for parameter (3) Endpoint Type, please refer to the following screenshot:
Click "APPLY" button and you should see "Service config updated successfully" message
Check if mbed devices are listed by endpoint/route verification
Check if a new device is created
Go to Device page, and you will see the device, which has been successfully created and provisioned.
Check if data is reporting
Click the device, and you will see the resource value, which has been updated
Associate application with product
Enter the application-type solution page
Click "Services" tab
Click "Products" at left services navigator
Check the checkbox next to the applicable product
Type "Mbedservice" (for example) as script alias next to the "EDIT SCRIPT"
Note: "Mbed" on its own cannot be used as the Lua Script Alias
Click "Apply" button
After you see the "Updates completed successfully." message on Snackbar, you have associated application with product successfully
Check if mbed devices are listed by calling device2.listIdentities() in endpoint
Click "Endpoints" tab under application page
Click "+ NEW ENDPOINT"
At the "New Route" pop-up, type "mbedservice" (for example) in path field , and click "CREATE" button
Enter the new created endpoint and write down the Lua code as below:
Note: To successfully use device2 public API, the alias device2 must be substituted with script alias created in the step above (which is Mbedservice as example here); further information about device2 APIs, please refer to the connectivity page
Click the link for AUTO-GENERATED DOCS
Click the "Try" for mbed/devices route
Should see all the mbed devices