Can´t parse additional arguments to Agent about iot-hub-device-update HOT 12 CLOSED

Hello,

Thank you for bringing this up, we are working on updating the documentation. While we do that, please see our responses below-

1. On this page (iot-hub-device-update/how-to-run-agent.md at main · Azure/iot-hub-device-update (github.com)

--EnableIotHubTracing

should read

--enable-iothub-tracing

2. At this moment we don't support a reference implementation of the Device Update agent on Fedora 21. But we are happy to help if you have any other questions based on our current support.

from iot-hub-device-update.

1. Is there a rough time frame when this part will be updated ? Are we talking Days or Weeks ? Which file defines these options ? Unfortunately I'm not able to find it myself.
2. I think the Agent is just running fine with the way I ported it to Fedora. But because I'm not experienced in these field I wasn't sure if I messed something up.

from iot-hub-device-update.

Hello,

1. We are working on it now, it should be updated within a week.
2. The file is here.

Thanks!

from iot-hub-device-update.

Related thread: https://docs.microsoft.com/en-us/answers/questions/355475/index.html

from iot-hub-device-update.

@ValOlson 1. Thanks for the estimate. 2. I'm not talking about the doc file but the source file of the update Agent.
@asergaz That's correct, that's my question, I also post it on Stack Overflow. I linked them to each other, so people see that's by the same author.

from iot-hub-device-update.

@Voxel07: We have a release planned in May, so you should see the source file updated as part of that release by mid May barring any issues at our end.

from iot-hub-device-update.

A little update for my side. I was looking at the right file src/agent/src/main.c the options mentioned in the doc just simply do not match at all, that's why I thought that I was missing something.

from iot-hub-device-update.

A little update for my side. I was looking at the right file src/agent/src/main.c the options mentioned in the doc just simply do not match at all, that's why I thought that I was missing something.

@Voxel07 : We have updated the how-to-run-agent.md file. It should reflect all the options in src/agent/src/main.c now.
Apologies for any confusion it caused. Please let us know if you have other questions! :)

from iot-hub-device-update.

Thanks @shiyi-peng for updating the doc file, there is an additional thing I noticed yesterday.

log level expected value hint 0-3 ist wrong. Should be 0-2 not 0-3 or the >= has to be changed to just >

logging.h

ADUC_LOG_DEBUG 0
ADUC_LOG_INFO 1
ADUC_LOG_WARN 2
ADUC_LOG_ERROR 3

main.c

if (!ret || logLevel < ADUC_LOG_DEBUG || logLEvel >= ADUC_LOG_ERROR)
{
      puts("Invalide log lebel after '--log-level' or '-l' option. Expected value: 0-3."); 
}

from iot-hub-device-update.

Thank you for your feedback, we are investigating this.

from iot-hub-device-update.

@Voxel07 this is fixed in our code and will be part of the upcoming release later in May.

from iot-hub-device-update.

There is more update in our latest release 0.8.0 https://github.com/Azure/iot-hub-device-update/tree/release/0.8.0
If interested, please check it out! ( we no longer use the Simulator agent, instead, we would use a simulator handler

from iot-hub-device-update.