Giter VIP home page Giter VIP logo

Comments (4)

ValOlson avatar ValOlson commented on September 24, 2024

Hi @Voxel07,

Thank you for your questions, please see our responses below-

  1. For 1 above, you are correct the current flow for the download, install and apply phases is shown here.. Any reason you need to skip the apply action?
  2. For 2 above, removing Files after the download action is a way of clearing the file list for the next deployment without consuming an additional IoT hub messages from your IoT Hub message quota. Today we have done this after download is complete, as you have observed. Is it a common scenario for your IoT device set up where you need to redownload the file after a reboot?

from iot-hub-device-update.

Voxel07 avatar Voxel07 commented on September 24, 2024

Thanks for the Answer.

  1. No, there is no reason to skip the apply step. But say for example, that the agent is running and for some reason the same update gets deployed again. Then there is no check in place to stop a new installation. That's the case I wanted to catch, maybe that's implemented in swUpdate, I don't know.
  2. It's not common or a planed workflow. I was just thinking of scenarios of what cold when go wrong. And if an Installation is interrupted, because the power to the device is cut for some reason, I can't do anything at the moment, but in my eye that's a scenario that the agent could recover from without human interaction.
    But saving the File or the download URL in nonvolatile memory is not an option at the moment. That's why I am asking.

from iot-hub-device-update.

Voxel07 avatar Voxel07 commented on September 24, 2024

Is it possible to get some information on when the backend service will ignore a reported state?

Like for e.g. when I report an Installed update when the deployment directly in the download phase. Then the device keeps the in progress state.
Or if download succeeded is reported twice, the second time the service won't send the install action. And the device is stuck in this state.

from iot-hub-device-update.

eshashah-msft avatar eshashah-msft commented on September 24, 2024

Please refer to this document on the goal state deployment that Device Update uses in the after the public preview refresh release (Feb' 22): https://github.com/Azure/iot-hub-device-update/blob/main/docs/agent-reference/goal-state-support.md

from iot-hub-device-update.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.