Hi, I’d like to create a custom capability that can be used by different devices. Some devices support only a subset of commands. I think I need something similar to windowShade’s supported commands, where the device during initialization will provide the list of supported values/commands. Is suc…

[image] ygerlovin: Is such functionality supported for custom capabilities? In theory, yes. However even some of the most basic functionality of capability presentations that I’ve been waiting on since day one doesn’t seem to have be implemented yet (like using basic commands instead of sette…

IMHO the backlight color belongs to the settings page as users will not change this setting often. Also please think about 3rd party integrations. I am afraid that the custom capability is not discoverable for Alexa/Google, so even basic on/off feature will be unavailable for users.

@veonua , Thank you for your replay. I personally don’t see any problem displaying rarely used capability in detail view. On the other hand, putting it into settings would mean the following: The current state of the device can not be queried/updated. This means the setting shown in settings p…

[image] ygerlovin: The current state of the device can not be queried/updated. This means the setting shown in settings page might not reflect the actual device state/configuration it can’t be true. settings are just a permanent storage under the hood so you can query update fields as you li…

The difference would be in which enums for the command you can select? Eg. In windowShade you can select that in the list only appear the options “open” and “close”. The option mentioned by @orangebucket is correct,supportedValues should be an attribute in the capability (it won’t be displayed) and…

@nayelyz , Thank you. That is correct, some devices will show a subset (on,off), while others will show all three options (on, off, state). I already looked at windowShade and thermostatMode capabilities, I just wanted to make sure that supportedValues attribute can be used also for custom capabi…

No problem! Let me know how it goes :smiley:

@orangebucket @ygerlovin @nayelyz I found this very helpful and wanted to check to see if anyone has published a generic capability as described. I am looking for one to use with a virtual device that uses the capability as input from a custom rule to get the temperature and humidity from multiple d…

[image] orangebucket: Anyway the bottom line seems to be that for the list display types you can use the supportedValues key. That should be set to an attribute value of your choice that holds an array of the commands (so I guess the equivalent of supportedButtons or supportedWindowShadeCommands)…

[image] Keith_Collins: I was thinking the generic command setter would take as input “component_name” ,“capability id”, “attribute name”, “attribute value” Hi, @Keith_Collins Have you made any progress on your use case? A single command cannot accept multiple arguments, but there’s the opti…

@nayelyz Thanks for following up. It is disappointing that the automation UI doesn’t have an equivalent of the advance webUI that shows any command and it’s associated set of parameters and allows you to test the command with all of it’s inputs. I did figure out how to do a set of commands each set…

Custom capability with list of supported commands

Developer Programs Writing Edge Drivers

Andreas_Roedl April 5, 2025, 1:18pm 13

Topic		Replies	Views
Custom capability with list presentation is not shown Support capability	8	913	September 28, 2021
Custom Device Capabilities: How To? SmartApps & Automations	20	7076	January 30, 2017
Unable to see custom capabilities in UI for "Direct-Connected" device Support	31	1429	July 7, 2023
Issue with an automation for custom capability Support	3	406	May 16, 2022
Custom Capability and CLI Developer Preview Tutorials devicetype , developers	1360	62279	December 2, 2022

Custom capability with list of supported commands

Related topics