CODEWITHSUNDEEP
azureazure-iot-hubotaazure-iot-sdk
Gaurav Choubey
Gaurav Choubey

Reputation: 21

Customization in OTA flow between IOT device and IOT HUB service

I am working on device update or OTA implementation with azure. Azure has device update feature with IOT hub. I am utilizing same service for my task.

I want to customized the IOT device update code for OTA operation. Normally IOT HUB Service initiate the all action(Download, Install, Apply) and based on request device will be acted, once requested action done ,device will update the state to IOT hub service and go ideal state where wait for next action..

I want to add one additional layer or confirmation layer for each action[Download, Install, Apply)] , mean when IOT hub Service request for any action, device will received as twin properties update. Instead executing the respective process(e.g. downloading the Firmware), device will wait for confirmation/ approval (which is customization part to be implemented ) from external/manual resource. Once confirmation/approval received, device will resume with flow and execute the respective process( device will start downloading the firmware and update response to IOT HUB Service).

My Question based on above scenario as follow

  1. Does it possible to implement above follow with current IOT HUB
    device update implementation from azure.
  2. What will happen if device not reply to IOT hub service for requested action ? Does it discard the whole OTA process ?
  3. What is time period of waiting for IOT hub service when it request for any action and waiting for reply ? My target to make wait for 30 days and if no approval or confirmation
    receive the, reply back to IOT hub service with fail/Discard
    response.
  4. Can I make 30 days waiting period for IOT hub service API response ?

Please answer me as soon as possible. As most of development depend on it.

Regards, Gaurav Choubey

Upvotes: 0

Views: 119

Answers (1)

asergaz
asergaz

Reputation: 1051

The Device Update Agent (installed on your device) will be responsible to set the "update status" as started succeeded , failed or idle.

As per your scenario and since Device Update Agent is open-sourced you can customize the Interface and Platform Layers to achieve it. IoT Hub should not be impacted by 30 days or more waiting period for the update to be completed.

Upvotes: 0

Related Questions