Develop for Android Things platform using Azure IoT SDKs

Azure IoT Hub SDKs provide first tier support for popular platforms such as Windows, Linux, OSX, MBED, and mobile platforms like Android and iOS. As part of our commitment to enable greater choice and flexibility in IoT deployments, the Java SDK also supports Android Things platform. Developers can leverage the benefits of Android Things operating system on the device side, while using Azure IoT Hub as the central message hub that scales to millions of simultaneously connected devices.

This tutorial outlines the steps to build a device side application on Android Things using the Azure IoT Java SDK.

• An Android Things supported hardware with Android Things OS running. You can follow Android Things documentation on how to flash Android Things OS. Make sure your Android Things device is connected to the internet with essential peripherals such as keyboard, display, and mouse attached. This tutorial uses Raspberry Pi 3.

• Latest version of Android Studio

• Latest version of Git

You can use the local Azure CLI.

• If you prefer, install the Azure CLI to run CLI reference commands.

• Local Azure CLI, see how to install the Azure CLI. If you're running on Windows or macOS, consider running Azure CLI in a Docker container. For more information, see How to run the Azure CLI in a Docker container.

  • Sign in to the Azure CLI by using the az login command. To finish the authentication process, follow the steps displayed in your terminal. For other sign-in options, see Sign in with the Azure CLI.

  • When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see Use extensions with the Azure CLI.

  • Run az version to find the version and dependent libraries that are installed. To upgrade to the latest version, run az upgrade.

This section describes how to create an IoT hub using the Azure portal.

1. Sign in to the Azure portal.

2. On the Azure homepage, select the + Create a resource button.

3. From the Categories menu, select Internet of Things, and then select IoT Hub.

4. On the Basics tab, complete the fields as follows:

   Important

   Because the IoT hub will be publicly discoverable as a DNS endpoint, be sure to avoid entering any sensitive or personally identifiable information when you name it.

   Expand table

   Property	Value
   Subscription	Select the subscription to use for your hub.
   Resource group	Select a resource group or create a new one. To create a new one, select Create new and fill in the name you want to use.
   IoT hub name	Enter a name for your hub. This name must be globally unique, with a length between 3 and 50 alphanumeric characters. The name can also include the dash ('-') character.
   Region	Select the region, closest to you, where you want your hub to be located. Some features, such as IoT Hub device streams, are only available in specific regions. For these limited features, you must select one of the supported regions.
   Tier	Select the tier that you want to use for your hub. Tier selection depends on how many features you want and how many messages you send through your solution per day. The free tier is intended for testing and evaluation. The free tier allows 500 devices to be connected to the hub and up to 8,000 messages per day. Each Azure subscription can create one IoT hub in the free tier. To compare the features available to each tier, select Compare tiers. For more information, see Choose the right IoT Hub tier for your solution.
   Daily message limit	Select the maximum daily quota of messages for your hub. The available options depend on the tier you've selected for your hub. To see the available messaging and pricing options, select See all options and select the option that best matches the needs of your hub. For more information, see IoT Hub quotas and throttling.

   

5. Select Next: Networking to continue creating your hub.

6. On the Networking tab, complete the fields as follows:

   Expand table

   Property	Value
   Connectivity configuration	Choose the endpoints that devices can use to connect to your IoT hub. Accept the default setting, Public endpoint, for this example. You can change this setting after the IoT hub is created. For more information, see Managing public network access for your IoT hub.

   

7. Select Next: Management to continue creating your hub.

   

   Accept the default settings here. If desired, you can modify any of the following fields:

   • Pricing and scale tier: Tier selection depends on how many features you want and how many messages you send through your solution per day. The free tier is intended for testing and evaluation. The free tier allows 500 devices to be connected to the hub and up to 8,000 messages per day. Each Azure subscription can create one IoT hub in the free tier. For details about other tier options, see Choosing the right IoT Hub tier.

     If you're working through a quickstart, select the free tier.

   • IoT Hub units: The number of messages allowed per unit per day depends on your hub's pricing tier. For example, if you want the hub to support ingress of 700,000 messages, choose two S1 tier units.

   • Role-based access control: This property decides how you manage access to your IoT hub. Allow shared access policies or choose only role-based access control. For more information, see Control access to IoT Hub by using Azure Active Directory.

   • Device-to-cloud partitions: This property relates the device-to-cloud messages to the number of simultaneous readers of the messages. Most hubs need only four partitions.

   Note

   Prices shown are for example purposes only.

8. Select Next: Tags to continue to the next screen.

   Tags are name/value pairs. You can assign the same tag to multiple resources and resource groups to categorize resources and consolidate billing. In this document, you won't be adding any tags. For more information, see Use tags to organize your Azure resources.

   

9. Select Next: Review + create to review your choices.

10. Select Create to start the deployment of your new hub. Your deployment will be in progress a few minutes while the hub is being created. Once the deployment is complete, select Go to resource to open the new hub.

A device must be registered with your IoT hub before it can connect. In this quickstart, you use the Azure local Shell to register a simulated device.

1. Run the following commands in Azure local Shell to add the IoT Hub CLI extension and to create the device identity.

   YourIoTHubName : Replace this placeholder below with the name you choose for your IoT hub.

   MyAndroidThingsDevice : This is the name given for the registered device. Use MyAndroidThingsDevice as shown. If you choose a different name for your device, you will also need to use that name throughout this article, and update the device name in the sample applications before you run them.

   az extension add --name azure-iot
   az iot hub device-identity create --hub-name YourIoTHubName --device-id MyAndroidThingsDevice
   

2. Run the following commands in Azure local Shell to get the device connection string for the device you just registered. Replace YourIoTHubName below with the name you choose for your IoT hub.

   az iot hub device-identity connection-string show --hub-name YourIoTHubName --device-id MyAndroidThingsDevice --output table
   

   Make a note of the device connection string, which looks like:

   HostName={YourIoTHubName}.azure-devices.cn;DeviceId=MyAndroidThingsDevice;SharedAccessKey={YourSharedAccessKey}

   You use this value later in the quickstart.

1. The first step to building an Android Things application is connecting to your Android Things devices. Connect your Android Things device to a display and connect it to the internet. Android Things provide documentation on how to connect to WiFi. After you have connected to the internet, take a note of the IP address listed under Networks.

2. Use the adb tool to connect to your Android Things device with the IP address noted above. Double check the connection by using this command from your terminal. You should see your devices listed as "connected".

   adb devices
   

3. Download our sample for Android/Android Things from the Azure IoT SDKs for Java repository or use Git to clone the repository as shown in the following example.

   git clone https://github.com/Azure/azure-iot-sdk-java.git
   

4. In Android Studio, open the Android Project from the \azure-iot-sdk-java\device\iot-device-samples\android-sample folder in your copy of the repository.

5. Open gradle.properties file, and replace "Device_connection_string" with your device connection string noted earlier.

6. Click on Run - Debug and select your device to deploy this code to your Android Things devices.

7. When the application is started successfully, you can see an application running on your Android Things device. This sample application sends randomly generated temperature readings.

You can view the data through your IoT hub as it is received. The IoT Hub CLI extension can connect to the service-side Events endpoint on your IoT Hub. The extension receives the device-to-cloud messages sent from your simulated device. An IoT Hub back-end application typically runs in the cloud to receive and process device-to-cloud messages.

Run the following commands in Azure local Shell, replacing YourIoTHubName with the name of your IoT hub:

az iot hub monitor-events --device-id MyAndroidThingsDevice --hub-name YourIoTHubName

If you will be continuing to the next recommended article, you can keep the resources you've already created and reuse them.

Otherwise, you can delete the Azure resources created in this article to avoid charges.

To delete a resource group by name:

1. Sign in to the Azure portal and select Resource groups.

2. In the Filter by name textbox, type the name of the resource group containing your IoT Hub.

3. To the right of your resource group in the result list, select ... then Delete resource group.

   

4. You will be asked to confirm the deletion of the resource group. Type the name of your resource group again to confirm, and then select Delete. After a few moments, the resource group and all of its contained resources are deleted.

• Learn about how to manage connectivity and reliable messaging using the IoT Hub SDKs.
• Learn about how to develop for mobile platforms such as iOS and Android.