This topic describes how to download, build and use the Device Explorer tool. You can use this tool to manage devices connecting to your IoT hub. For example, you can register a device with your IoT hub, monitor messages from your devices, and send messages to your devices.
Device Explorer runs on your local machine and connects to your IoT hub in Azure. It communicates with the following IoT Hub endpoints:
- Device identity management to provision and manage devices registtered with your IoT hub.
- Receive device-to-cloud to enable you to monitor messages sent from your device to your IoT hub.
- Send cloud-to-device to enable you to send messages to your devices from your IoT hub.
Note: The Device Explorer utility only runs on Windows. On other platforms use the iothub explorer tool.
To learn more about IoT Hub, see What is Azure IoT Hub?.
- Getting Device Explorer
- Configure an IoT Hub connection
- Manage devices
- Monitor device-to-cloud events
- Send cloud-to-device messages
You can either download a pre-built version of Device Explorer or build it yourself.
A pre-built version of the Device Explorer application for Windows can be downloaded by clicking on this link: Downloads (Scroll down for SetupDeviceExplorer.msi). The default installation directory for this application is "C:\Program Files (x86)\Microsoft\DeviceExplorer". You might want to pin the DeviceExplorer.exe application to the taskbar for easier access.
To build Device Explorer yourself, open the tools\DeviceExplorer\DeviceExplorer.sln file in your local copy of this repository (azure-iot-sdks) in Visual Studio 2015. Then build and run the solution.
## Configure an IoT Hub connection- In the Configuration tab, add the connection string for your IoT Hub. For information about how to find this connection string, see the document Setup your IoT Hub. Then click Update.
You only need to complete this step if you are using a Protocol Gateway (such as the Microsoft Azure IoT Protocol Gateway).
Add the address of your protocol gateway to the Protocol Gateway HostName field with the address of your protocol gateway before you try to get a device connection string on the Management tab. If you are running the protocol gateway locally on the same machine as Device Explorer, you can use localhost as the address, otherwise you will need the network address of the machine where you deployed the protocol gateway.
## Manage devices - Click the **Management** tab to manage the devices connected to the IoT hub.
Creating a device adds device details to the device identity registry. IoT Hub uses this information to generate a device-specific connection string that enables the device to connect to the IoT hub.
- On the Management tab, click Create to register a new device with that IoT Hub. The Create Device dialog appears. In the Device ID field, type a unique name for your device (or select Auto Generate ID to generate a unique ID instead). Then click Create.
- A Device Created window appears, indicating that your device has been successfully registered with this IoT Hub.
- Click Update to change the primary or secondary key for the selected device. You will need to update your device to use any new keys you generate.
- Click Delete to delete the selected devices from the connected IoT hub.
- Click SAS Token... to generate a device specific connection string with SAS token.
-
Use the mouse right click for context menu for the selected device. The menu has the following options
The following steps describe how to use Device Explorer to monitor device-to-cloud events sent from a sample application on a client to an IoT hub and use the Device Explorer utility to observe as the IoT hub receives the event data.
You can use one of the sample applications included in this repository (azure-iot-sdks) to send device-to-cloud events to your IoT Hub. Follow the step by step tutorial to set up the sample application. Use Device Explorer to create a device and generate a connection string.
- You can obtain the IoT Hub connection string from Device Explorer. In the Management tab, right-click on the selected device and select "Copy connection string for selected device". The device connection string is silently copied to the clipboard.
Note: Device Explorer requires an IoT hub connection string obtained from the Azure portal to enable it to connect to the hub. You can then use Device Explorer to generate device-specific connection strings that enable devices to communicate with the hub.
-
Update the device connection string placeholder in the application you are using with the connection string from Device Explorer.
-
In the Device Explorer Data tab, select the device name you created from the drop-down list of device IDs and leave the other fields with their default values for now.
-
Click Monitor.
- Device Explorer is now monitoring data sent from that device to the IoT hub.
Run your sample application. Device Explorer should now show that the IoT hub has successfully received device-to-cloud data from this device.
-
To verify that you can send cloud-to-device messages from the IoT hub to your device, go to the Messages To Device tab in Device Explorer.
-
Select the device you created.
-
Add some text to the Message field, then click Send.
- You should be able to see the command received in the console window for the client sample application you are using.
Note: You must be sure to use the correct format when you send a message to your device. For example, the simplesample_amqp sample for the C serializer library accepts the following JSON commands:
{"Name":"SetAirResistance","Parameters":{"Position":55}}
{"Name":"TurnFanOn","Parameters":{}}