Can Device Profile choose percentage or 100 fanSpeed?

[nayelyz (SmartThings Developer Support)]

Hi, sorry for the delay.

Thanks, @philh30 so much for your collaboration, it’s highly appreciated.

@exosite, if you want to change the range of fanSpeed, please consider that the values 0-4 have alternatives configured. This means that, instead of showing the number, it shows a “speed” related text, for example: instead of the number “4”, the app will show “Max” and instead of “1” it will show “Low”. After that, the next numbers will show the number itself, so it could cause some confusion.

@exosite

1. I followed your previous example to modify the labels.

As @philh30 mentioned, it could be cached, this happens mostly with the text that we can set in the labels, so we suggest you make the changes carefully. If the update is not made in the presentation itself, you might have to add/remove a capability to force the refresh.
Remember the difference between these API calls:

1. Get the device presentation’s current configuration:
   https://api.smartthings.com/v1/presentation?presentationId=ST_f19d367f-93b4-48e8-88d1-fd71fb78d489&manufacturerName=0A6z
2. Get the device configuration used to create a device presentation:
   https://api.smartthings.com/v1/presentation/deviceconfig?presentationId=ST_f19d367f-93b4-48e8-88d1-fd71fb78d489&manufacturerName=0A6z
   Note: This call could differ from the current configuration of the device presentation, that’s why the call in #1 is better to verify the change was received.

@exosite

I was trying to upload the json file through smartthings cli too:

We don’t suggest the usage of the CLI to modify the configuration of a device profile created in the Developer Workspace because it could cause a sync conflict.

@exosite

Is that possible I replace switchLevel label as fanSpeed label like this?

No, it cannot be changed dynamically, so, this parameter wouldn’t be accepted: {{fanSpeed.value}}

@exosite

3. What is the different between

We don’t suggest using deviceprofiles:view now as its functionality isn’t complete.
See this post: Device Profile created from the CLI is incomplete - #14 by andresg

@exosite

What does this mean cannot be certificated if using custom capabilities?

It means that any capabilities you created directly using the ST API are not accepted in the certification process. Even if you made the certification request, it will be rejected.
But, as mentioned in a previous post, modifying the label of the capability would override the translation, so, the text shown there would be static for every language.
Also, other things to consider if you use a capability for a different purpose than the one it was made for are:

1. It will confuse other integrations like voice assistants because it will use the default configuration (range and usage)
2. In this case, the testing team for the certification would need guidance to understand the expected result from your integration and that’s not supported either.

@exosite

Maybe in the future we need to implement N speed fan control. Is there any custom device profile supporting N speed fanSpeed? Or maybe No.1 question can be treated as a 100 speed fanSpeed?

What do you mean by this? You mentioned it is handled based on the percentage of speed, isn’t it? That means 0-100, would the range increment in other cases?

I would need to check if modifying the range of the fanSpeed capability can be accepted for certification because of the alternatives configured.