Device Profile created from the CLI is incomplete

Developer Programs
10

This is normal, the VID doesn’t appear there because it hasn’t been created yet, the generate command provides a template and doesn’t save any config.
The metadata property is part of the device profile, I didn’t specify this correctly earlier.
Also, the profile ID won’t appear there because a VID can be used in several profiles but a profile can use only one VID, so, that’s why this property must be included in the device profile.

I haven’t received the confirmation from the team but I don’t think the correct info of the profile will appear in that page.
To confirm the configuration you need to use the CLI as well:

smartthings deviceprofiles profileID -j or -y

Just to confirm we’re on the same page, here’s the process to create a device profile and its config:

  1. Create your device profile, you can only specify the capabilities used:
smartthings deviceprofiles:create
//You can also create it from a file adding -i profile.json or yaml
  1. Generate the device-config file which takes the list of capabilities in the device profile and puts them in each view.
smartthings presentation:device-config:generate profileID -j -o=deviceConfig.json
  1. Edit the file to add your custom configuration (change enums available, numbers range, etc.). You can also leave it as it is, then, create the device presentation to get its VID:
smartthings presentation:device-config:create -i deviceConfig.json

In the result of that command, you’ll see the VID and mnmn that you’ll use later.
4. Edit the device profile and add the metadata property with the correct VID and mnmn. This is an example using the YAML format:

name: multi-switch
components:
- id: main
  capabilities:
  - id: switch
    version: 1
  label: Main
  categories:
  - name: Switch
metadata:
  vid: xxx-xxx-xxx
  mnmn: SmartThingsCommunity

//command:
smartthings deviceprofiles:update profileId -i deviceProfile.yaml
  1. After this, you can use the profile normally but other users won’t have access to it unless it’s published. If you rather ask users to create it, they just need to do it using the final config (metadata included). The device presentation (VID) isn’t linked to an account so others can use it on their side.