Devices are not visible in Group and Deployments(Iothub update)

Question

Hi,

I want to update the device. In order to do that I was following "Update Device Package Tutorial".

https://learn.microsoft.com/en-us/azure/iot-hub-device-update/device-update-ubuntu-agent

I have prepared the device manually by following the instructions from "Tutorial and How to Guides".

I have provided all the required permissions mentioned in "configure-access-control-device-update".
https://learn.microsoft.com/en-us/azure/iot-hub-device-update/configure-access-control-device-update?tabs=portal

Device is online and $edgeAgent and $edgeHub are in running state.

IoTHubDeviceUpdate is in NA state however "Module Identity Twin" shows it in connected state.

Also it is receiving data from update agent

Since update agent was in connected state, I have added tags in Device twin. **But, even after adding the tags it is not visible "Groups and Deployments".
**

Note: Import update was working fine.

I have tried whole procedure 3-4 times after cleanup everything but facing the same issue.

Answer 1

Hello Govind Singh Parmar, thanks for reaching out on this issue,
Wanted to check few more points from your side! I know you have already invested much time in troubleshooting this, but wanted to get this discussion started!

Can you please check that tags are in the correct format and syntax which are applied to the right Device?

And any suspicious when checking Azure IoT Hub logs or device has the appropriate permissions to access Azure IoT Hub by sending any telemetry testing and monitor its data transfer?

Answer 2

Thanks Satish. The issue has been resolved with the help of support team. The issue was related to service principal permission.

We had given IoT Hub Data Contributor role to user instead of 'Azure Device Update' service.

Now we have corrected it and device are visible now in the Groups tabs.

Answer 3

Hi @Govind Singh Parmar Thank you for sharing the feedback on this and the steps you have tried so far in testing this out. I highly appreciate your patience and persistence in trying to make this work. Thank you for testing this multiple times and I apologize for the issues you are encountering.

I would like to make a note a that connection type has to be set to AIS for agents who will be using the IoT Identity Service for provisioning. Looking at the status messages returned from deviceupdate-agent, it implies that the agent could not make a successful connection with the IoT Edge device. I have followed the steps to Manually prepare a device to set up the device update. If the device update agent connection status was successful, you would see a message similar to the below image.

Kindly note that I have used connection type as string and provided the IoT Edge device ID primary connection string in the /etc/adu/du-config.json file. Here is the file for your reference.

I have added the "tags" in the Device Twin of my IoT Edge device as mentioned in the step 4 of section Add a tag to your device Please refer the below image of my device twin.

After I imported the sample-1.0.2-aziot-edge-apt-manifest and sample-1.0.2-aziot-edge.importmanifest update packages referenced in the Import the update I could see that I have available updates and the device group gets populated with the name of the ADUGroup tag I specified in the above image.

Please find the below image for your reference

Kindly give a try with the connection string approach and let us know if you still experience any issues. Please do not hesitate to reach out to us with any further questions on this.