An Online Azure IoT Hub Developer Tool – IoT DevTool (Overview)


IoT DevTool is not a Microsoft official project.

I hope it’s not too late to release this online tool for Azure IoT Hub. IoT Hub is an important part of Azure IoT, it’s the bond of connection between Internet and Things. Many developers are already using iothub-explorer, an X-platform CLI tool in NodeJS for IoT Hub, including our team at Microsoft. However, there’re also many developers do not have NodeJS environment setup in their machine, especially on Windows.

An X-platform tool is necessary for IoT Hub, what if we change our X-platform focus from operating system to browser? That’s why we’ve been working hard on developing a web based IoT Hub dev tool. Today we are releasing IoT DevTool, which brings your IoT development into a browser.

A series of posts to introduce IoT DevTool:

  1. Overview
  2. For Cloud Developers
  3. For IoT Hub Device Administrators
  4. For Device Developers
  5. For RESTful Developers

IoT DevTool supports Chrome, Firefox, Safari, Edge and IE 11, to start using it, just open your favorite browser and visit aka.ms/iotdevtool.

There are four parts in IoT DevTool for developers in different roles, Device, Registry, Service and RESTful.

IoT DevTool

Device is a device simulator tool for cloud developers, you can send Device-to-Cloud messages, retrieve Cloud-to-Device messages, listen direct method and get or update device twin reported properties in this part. If you are a developer on cloud side, you can verify your code with this tool very simply.

Registry is a device management tool for IoT Hub device administrator, you can manage IoT devices with simple some clicks, including create or remove devices, generate device SAS token, check device connection state.

Service is a cloud simulator for developers on device side, you can send Cloud-to-Device messages, retrieve Device-to-Cloud messages, call direct method and get or update device twin desired properties.

And last, the RESTful part. You can verify RESTful API request with this tool. RESTful tool has already had a built in API list, and when you select an API, request host name, path, authorization header and body will be already filled for you. Also, you can modify any of the filled information and make your own request.

Comments (2)

  1. Andrea Tosato says:

    HttpRestfull “Upload file upload status” is incorrect:
    https://docs.microsoft.com/en-us/rest/api/iothub/httpruntime#HttpRuntime_UpdateFileUploadStatus

    Http request require field “fileUploadCompletionStatus”. What format does?
    Thaks

    1. Sneezry says:

      Hi Andrea,

      fileUploadCompletionStatus is in format of

      {
      “correlationId”: “xxx”,
      “isSuccess”: true,
      “statusCode”: 200,
      “statusDescription”: “xxx”
      }

      If you get error Http request require field “fileUploadCompletionStatus”, you should forget to post data.

      Zhe

Skip to main content