You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am updating devices that are already in the field. The devices support the Azure Device update service and has previously been updated using this.
My new version has updated with new libs so that ADU client has changed it reported data from
from interfaceId = dtmi:azure:iot:deviceUpdateContractModel;1
to contractModelId = dtmi:azure:iot:deviceUpdateContractModel;2
So the device is using the interfaceId while the new image is reporting contractModelId.
It seems that the update fails. and I do not know the reason. Is ADU service not supporting the contractModelId ?
Expected behavior
Device is updated by ADU service.
Steps to reproduce the issue
One device capable of updating with interfaceId.
A new image reporting contractModelId
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Version
main branch Jun 13 2023
Description of the issue
I am updating devices that are already in the field. The devices support the Azure Device update service and has previously been updated using this.
My new version has updated with new libs so that ADU client has changed it reported data from
from interfaceId = dtmi:azure:iot:deviceUpdateContractModel;1
to contractModelId = dtmi:azure:iot:deviceUpdateContractModel;2
So the device is using the interfaceId while the new image is reporting contractModelId.
It seems that the update fails. and I do not know the reason. Is ADU service not supporting the contractModelId ?
Expected behavior
Device is updated by ADU service.
Steps to reproduce the issue
One device capable of updating with interfaceId.
A new image reporting contractModelId
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: