Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to see Azure Device Update Groups in IoT Hub #76

Closed
sihbher opened this issue Jun 14, 2021 · 2 comments
Closed

Unable to see Azure Device Update Groups in IoT Hub #76

sihbher opened this issue Jun 14, 2021 · 2 comments
Assignees

Comments

@sihbher
Copy link

sihbher commented Jun 14, 2021

I followed this procedure I manually prepared my VM

I added a tag for ADUGroup to my edge device in the Device Twin and in the IoTHubDeviceUpdate module Twin (because it was not clear to me to which I had to):

'tags': {
'ADUGroup': 'gerryTest'
}

image

image

When I try to create a Group in Device Updates - Groups the tag is not present, in fact NO TAGS are available in the drop down at all.

image

image

UPDATE:
I tried using the "Deploy to Azure" Button and it worked!!, after I checked what was the difference, I noticed that the template used for creating the VM has these commands:

    apt install -y deviceupdate-agent
    apt install -y deliveryoptimization-plugin-apt
    systemctl restart adu-agent

I believe the trick is done by restart adu-agent before tag the device! that instruction is not referenced in the manually procedure, please confirm, if it is the case please add to the documentation

@cdbierl
Copy link

cdbierl commented Feb 3, 2022

Using 0.8.0 release and connecting as module from my host, can't for the life of me get the ADUGroup tag to trigger any changes in the "Create Group" dropdown in IoTHub portal.....

This just in, the IoTHub portal just received an update! I see some new user interface and tags!

@jw-msft
Copy link
Contributor

jw-msft commented Feb 3, 2022

Yes, the agent needs to connect before setting the ADUGroup tag.
Can set ADUGroup to null in the twin and then restart via sudo systemctl restart adu-agent to resolve it.

Once you see it is connected in the twin, then add the ADUGroup tag.
Then you should be able to see the group available when adding a group.

@esha0611 Could you include this in relevant ms docs? I'll update the .md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants