Per the forum guidelines, each of my posts is a separate issue.
This post really is just a question. I found that the CLI requires that the second alternatives must be configured if you want to display status (state) to the left of the gear in a list display type. This made me wonder what the second alternatives were even used for since I had never seen them in action.
Now that I’ve disabled the filter and added different keys, I can see the second alternatives displayed in gray. I don’t think this feature adds any useful functionality. I don’t need to use it. I still question why it was ever implemented. You can (better) accomplish the same thing with the filter.
Concerning the filter, my idea was to filter out off as a command when the device is already off. That’s not possible because the list is populated once when the app screen is created. If I were to filter out off and you turn the device on, then the list would still contain on, but the off command would still be missing. You’d have to leave detailView and reenter to see the commands update. I do not consider this a bug. It’s simply a feature limitation.
I need to revisit based on my new understanding, but I’ve still been unable to apply a device-config to a list in order to change the label or alternatives. It’s unclear whether that’s even supported. That discussion begins here. I will simplify my example and start a new post. The workaround is to create additional custom presentations with the changes already hardcoded. Of course, each custom presentation requires its own custom capability.
My ultimate goal is to implement an Edge driver package that supports all the devices in my personal home along with additional automation features. The fan controls will use the pushButton in the dashboard to cycle speed instead of just on/off. Similarly, dimmers will cycle through 3 preset levels. The detailView for a particular device will show other devices in the same room/area. I’ve found the list display type to be the most compact control. I do not want to scroll the detailView. Everything must fit one screen. I like fanSpeed, but in order to use more than 1, I need to create additional components which insert a header taking up precious screen space. Maybe now you can see how all my recent posts fit together.