[ST Edge] What is the purpose of 'state' section in the 'list' display type?

[nayelyz (SmartThings Developer Support)]

@nmpu

I populated both sections with keys ‘0’ - ‘9’. The command values are ‘One’, ‘Two’, ‘Three’, etc… The state values are ‘ONE’, ‘TWO’, ‘THREE’, etc…

You’re referring to the case you mentioned in this post, right?

Edge driver device-config creation

Here’s where I’ve been successful so far: Show/hide capabilities in dashboard and detailView without any internal configuration changes Modify the label and alternatives in dashboard Modify the label, range and alternatives for fanSpeed in detailView Here’s where I still have trouble. I have a custom capability with 2 attributes-- mode and filter. mode is displayed as a list with supportedValues: filter.value. The filter works as expected. When I apply my device-config, the dashboard changes, but the detailView is unchanged. When I smartthings presentation:device-config:create, the correct details scroll up the screen. However, if I go back and examine the vid, the changes to detailView are missing. Is this even supposed to work? My goal is to create multiple devices with different l…

Let me make some tests with your capability to have a better reference on the behavior you describe.

About the “two” alternatives properties (one in states and the other in commands, I agree with @orangebucket:

@orangebucket

Presumably because there is not necessarily any similarity between the attribute values and the command arguments and even if there were you might want to present them in a different way e.g. System armed v Arm the system .

The behavior I’ve seen is that if you define different states and commands, all values will appear in the list. However, only the commands are allowed to select, the states appear in gray, for example: