Ok, so, I made a test using only the VID assigned to the profile which is c47d11a4-f23f-3c6c-a618-1c81afedb05c and the change works correctly as shown below:
I checked the device profile 561d00b2-b7ea-4d23-ba70-34c6516900f1 and noticed two things:
- Its status is “development” which indicates you created it directly and it doesn’t belong to an Edge driver, right?
Currently, embedded configurations are supported only on profiles created by an Edge driver. - Did you use the command
device-profiles:view:createfor it? If so, please avoid using that one because its functionality isn’t reliable and there are plans to substitute that for embedded configurations but there’s no ETA for them to work with explicitly created profiles.
Here I shared the steps to create correctly a device profile with its device presentation manually:
Device Profile created from the CLI is incomplete - #10 by nayelyz
Note: In a device profile where embedded configurations are supported, you cannot use both (VID and embedded configurations). I confirmed with the team that won’t work because when we use embedded configurations a new presentation will be created, so the value in the “metadata” property will be ignored.