This is the Avnet IoTConnect mbed SDK. More info about IoTConnect, Please refer to https://www.iotconnect.io/. This could also work with Microsoft Azure IoT hub, more about Azure IoT hub, please refer to https://docs.microsoft.com/en-us/azure/iot-hub/ .
# mbed-iot-connect
This is the Avnet IoTConnect mbed C/C++ SDK. More info about IoTConnect, Please refer to https://www.iotconnect.io/. The backend of IoTConnect is Microsoft Azure IoT hub, more about Azure IoT hub, please refer to https://docs.microsoft.com/en-us/azure/iot-hub/.
This mbed SDK, is an IoTConnect MQTT client library, More about mbed, please refer to https://os.mbed.com/
...
...
@@ -8,23 +9,23 @@ This mbed SDK, is an IoTConnect MQTT client library, More about mbed, please ref
### Features have been supported
- Authentication
- Symmetric Key
- X.509 certificate
- Symmetric Key
- X.509 certificate
- MQTT - Lowlevel
- Publish
- Subscribe
- Device Property - Highlevel, users could get/set properties instead of managing of a RAW MQTT message
- Support String / Int / Bool property types
- Support Muti properties in a device
- Set a property and publish to IoT hub
- Subscribe IoT hub, it will manage the device properties, if any property has been changed, an on_change() callback is called, in callback, users could do things according to the new property
### Features to be supported
- Device Attributes (Device to Could Messages)
- cJSON as the Attribute backend
- Support String / Int / Object json types
- Support Muti attributes in a device
- Set / Update attributes and publish to IoTConnect
- Commands (Cloud to Device Messages)
- Subscribe MQTT Topic
- Support register callback of different commands to handler
- Device Twins
- OTA
## How to
## Install mbed Development Environment
### Install mbed Development Environment
This is a mbed library, so you should install the development env first. The Arm Mbed OS ecosystem includes many tools designed to work with Mbed OS and projects:
...
...
@@ -33,18 +34,16 @@ This is a mbed library, so you should install the development env first. The Arm
# ./BUILD/CY8CKIT_062_WIFI_BT/GCC_ARM/sample.hex will be generated
```
### Board Setup and Load the .Hex
- Use the USB lead to connect your Mbed to a PC. The status light will come on, indicating it has power. After a few seconds of activity, the PC will recognise the Mbed Microcontroller as a standard USB drive.
- Copy the sample.hex file to the USB drive
### Demo
> NOTE: The main difference between IoTConnect and your Microsoft Azure IoT hub is the device ID, it makes a new Device ID with (cpid + device id in IoTConnect), But in debug / development periods, Microsoft has many tools can help you debug.
#### Microsfot Azure IoT Hub
**Demo - Subscribe**
Login https://portal.azure.com/ and enter the device page, Clike 'Message to device', this allow you to send a message to device. message could be: