Microsoft Azure IoTCentral SDK for Python

An Azure IoT Central device client library written in Python.

This repository contains code for the Azure IoT Central SDK for Python. This enables python developers to easily create device solutions that semealessly connect to Azure IoT Central applications. It hides some of the complexities of the official Azure IoT SDK and uses IoT Central naming conventions.

Disclaimer

This library is experimental and has the purpose of providing an easy to use solution for prototyping and small projects. Although stable and actively maintained, its use in production is discouraged. Please refer to official Azure IoT Python SDK when building production products.

Prerequisites

• Python 2.7+ or Python 3.7+ (recommended)

Installing iotc

pip install iotc

These clients are available with an asynchronous API, as well as a blocking synchronous API for compatibility scenarios. We recommend you use Python 3.7+ and the asynchronous API.

Python Version	Asynchronous API	Synchronous API
Python 3.5.3+	YES	YES
Python 2.7	NO	YES

Samples

Check out the sample repository for example code showing how the SDK can be used in the various scenarios:

• py3 - Sending telemetry and receiving properties and commands with device connected through symmetric key (Python 3.7+)
• py3_x509 - Sending telemetry and receiving properties and commands with device connected through x509 certificates (Python 3.7+)
• py3_file_logger - Print logs on file with rotation (Python 3.7+)
• py3_eventhub_logger - Redirect logs to Azure Event Hub (Python 3.7+)

The following samples are legacy samples, they work with the sycnhronous API intended for use with Python 2.7, or in compatibility scenarios with later versions. We recommend you use the asynchronous API and Python3 samples above instead.

• py2 - Sending telemetry and receiving properties and commands with device connected through symmetric key (Python 2.7+)
• py2_x509 - Sending telemetry and receiving properties and commands with device connected through x509 certificates (Python 2.7+)

Samples by default parse a configuration file including required credentials. Just create a file called samples.ini inside the samples folder with a content like this:

[SymmetricKey]
ScopeId = scopeid
DeviceId = deviceid
Key = group_or_device_key

[x509]
ScopeId = scopeid
DeviceId = deviceid
CertFilePath = path_to_cert_file
KeyFilePath = path_to_key_file
CertPassphrase = optional password

The configuration file can include one of the sections or both. Section names must match references in the sample file.

Run samples with local changes

It is possible to run samples against the local copy of the device client. This is particularly useful when testing patches not yet published upstream. Just add an entry to samples.ini in the DEFAULT section:

[DEFAULT]
Local = yes

Importing the module

Sync client (Python 2.7+ and 3.7+) can be imported in this way:

from iotc import IoTCClient

Async client (with asyncio for Python 3.7+ only) can be imported like this:

from iotc.aio import IoTCClient

Connecting

X509

scopeId = 'scopeID';
device_id = 'device_id';
key = {'certFile':'<CERT_CHAIN_FILE_PATH>','keyFile':'<CERT_KEY_FILE_PATH>','certPhrase':'<CERT_PASSWORD>'}

iotc = IoTCClient(device_id, scopeId,
                  IOTCConnectType.IOTC_CONNECT_X509_CERT, key)

IOTCConnectType enum can be imported from the same module of IoTCClient

'certPhrase' is optional and represents the password for the certificate if any

A handy tool to generate self-signed certificates in order to test x509 authentication can be found in the IoTCentral Node.JS SDK here.

SAS

scopeId = 'scopeID';
device_id = 'device_id';
sasKey = 'masterKey'; # or use device key directly

iotc = IoTCClient(device_id, scopeId,
                  IOTCConnectType.IOTC_CONNECT_SYMM_KEY, sasKey)

IOTCConnectType enum can be imported from the same module of IoTCClient

Connect

Sync

iotc.connect()

Async

await iotc.connect()

After successfull connection, IOTC context is available for further commands.

Reconnection

The device client automatically handle reconnection in case of network failures or disconnections. However if process runs for long time (e.g. unmonitored devices) a reconnection might fail because of credentials expiration.

To control reconnection and reset credentials the function is_connected() is available and can be used to test connection status inside a loop or before running operations.

e.g.

retry = 0 # stop reconnection attempts 
while true:
    if iotc.is_connected():
        # do something
    else
        if retry == 10:
            sys.exit("error")
        retry += 1
        iotc.connect()

Operations

Send telemetry

e.g. Send telemetry every 3 seconds

while iotc.is_connected():
        await iotc.send_telemetry({
            'accelerometerX': str(randint(20, 45)),
            'accelerometerY': str(randint(20, 45)),
            "accelerometerZ": str(randint(20, 45))
        })
        time.sleep(3)

An optional properties object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ). Properties can be custom or part of the reserved ones (see list here).

Send property update

iotc.sendProperty({'fieldName':'fieldValue'})

Listen to properties update

iotc.on(IOTCEvents.IOTC_PROPERTIES, callback)

To provide setting sync aknowledgement, the callback must reply True if the new value has been applied or False otherwise

async def onProps(propName, propValue):
    print(propValue)
    return True

iotc.on(IOTCEvents.IOTC_PROPERTIES, onProps)

Listen to commands

iotc.on(IOTCEvents.IOTC_COMMAND, callback)

To provide feedbacks for the command like execution result or progress, the client can call the ack function available in the callback.

The function accepts 3 arguments: command name, a custom response message and the request id for which the ack applies.

async def onCommands(command, ack):
    print(command.name)
    await ack(command.name, 'Command received', command.request_id)

Logging

The default log prints to console operations status and errors. This is the IOTC_LOGGING_API_ONLY logging level. The function set_log_level() can be used to change options or disable logs. It accepts a IOTCLogLevel value among the following:

• IOTC_LOGGING_DISABLED (log disabled)
• IOTC_LOGGING_API_ONLY (information and errors, default)
• IOTC_LOGGING_ALL (all messages, debug and underlying errors)

The device client also accepts an optional Logger instance to redirect logs to other targets than console. The custom class must implement three methods:

• info(message)
• debug(message)
• set_log_level(message);

One-touch device provisioning and approval

A device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.

How to set IoTC template ID in your device

Template Id can be found in the device explorer page of IoTCentral

Then call this method before connect():

iotc.setModelId('<modelId>');

Manual approval (default)

By default device auto-approval in IoT Central is disabled, which means that administrator needs to approve the device registration to complete the provisioning process. This can be done from explorer page after selecting the device

Automatic approval

To change default behavior, administrator can enable device auto-approval from Device Connection page under the Administration section. With automatic approval a device can be provisioned without any manual action and can start sending/receiving data after status changes to "Provisioned"

License

This samples is licensed with the MIT license. For more information, see LICENSE