How to make devices in IoT hub visible in Groups and Deployments of updates?

Question

How to make devices in IoT hub visible in Groups and Deployments of updates?

I tried registering the device through DPS, and I also tried registering the device through direct CA registration.

If it is properly set as a ConnectedDevice, shouldn't the device list be listed as $Default in the Group & Deployment section of the Updates section?

I've been wandering around this part for several days. Please ask for a quick response or if you have any questions. 🙏🙏😂

Best Regards,

Kevin Kim.

Answer 1

Hi @Kevin Kim Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

If it is properly set as a ConnectedDevice, shouldn't the device list be listed as $Default in the Group & Deployment section of the Updates section?

It appears you might have missed a few steps for the device update grouping to work as expected. After you provision the devices, you would have to install and start Device Update Agent on the IoT device for it to be compatible with updates. Once the Device Update Agent is installed and there is an update imported into the IoT Hub, you would then be able to see the devices grouped on this page. Here, if you haven't specified any tags to the devices, every device would be grouped under the $Default group.

Please refer the following prerequisites needed to deploy an update using Device Update for Azure IoT Hub

• Access to an IoT Hub with Device Update for IoT Hub enabled. We recommend that you use an S1 (Standard) tier or above for your IoT Hub.
• An imported update for the provisioned device.
• An IoT device (or simulator) provisioned for Device Update within IoT Hub.
• The device is part of at least one default group or user-created update group.

Please refer to the following resources that will guide you with the steps needed to set up your IoT Hub environment and deploy a test update.

1. Create Device Update for IoT Hub resources
2. Import an update to Device Update for IoT Hub
3. Device Update Agent Provisioning
4. Deploy an update by using Device Update for Azure IoT Hub

Hope this helps. Please let us know, in the comments below, if you experience any issues after trying out the steps in the above articles. We would be glad to assist you further.

---

If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.

Answer 2

Hi @LeelaRajeshSayana-MSFT . Thanks for your reply.

Unfortunately, we haven't solved the problem yet.

Still, thanks to the information you provided, there is some hope.

I would like to ask a few more questions.

---

Q1. Can you provide detailed instructions on installing Device Update Agent in a Windows WSL (ubuntu 18) environment?

1. Create Device Update for IoT Hub resources
2. Import an update to Device Update for IoT Hub
3. Device Update Agent Provisioning
4. Deploy an update by using Device Update for Azure IoT Hub

I'm having trouble with number 3 in this phrase, Device Update Agent Provisioning.

I would like to install Device Update Agent in a Windows environment and apply it to the sample of Azure SDK C.

We tried using Azure IoT SDK C.

By building prov_dev_client_sample.c that your company kindly provided,

we confirmed that the device was automatically registered with Azure IoT DPS -> Azure IoT Hub.

(~\azure-iot-sdk-c\provisioning_client\samples\prov_dev_client_sample\prov_dev_client_sample.c)

I want to build it by adding device update agent to prov_dev_client_sample.

Is there another way?

👍😂

We simply want to make sure that the device group is visible.

We are working on a demo project to use Azure IoT for actual services.

Please support us. please.

---

Q2. It is a similar environment to Azure RTOS, but why is device update agent necessary?

I think we're using devices that use Azure RTOS. (It's not exact, though.)

We successfully registered the device, checked the IoT hub and telemetry, and thought it was a success.

However, I didn't know that there would be such a blockage in the area of ​​adding device updates as an OTA function.

We're starting to wonder if Device Update Agent is required.

Why does RTOS not need an ADU agent?

Is this guide limited to Azure RTOS NetX Duo?

---

I will leave our situation in more detail. If you have any questions or need more information, please let me know!

We registered the connection with the device and IoT hub through mqtt and x509.self-certificate.

And we have completed creating DPS and Update Service instances, as well as creating containers.

I checked by going to the Device management -> Updates section in IoT-Hub.

Import a new update was successfully created and uploaded as a sample file.

The problem is that the device group does not appear in the Groups and Deployments tab.

(even the $Default group)

In my opinion, the device environment we use is similar to the environment using Azure RTOS.

Successfully registered a device other than the file provided by SDK-c. And since it is similar to the RTOS environment, I thought that all I had to do was "Tag your device" and the 'Device Group' would appear in the "IoT Hub".