How to make custom `command` parameters Required?

[storageanarchy]

Built-in capabilities apparently use some mechanism to define that certain parameters are required, as in deviceNotification for the Notification capability:

(Note the red underline for the Text* parameter).

I know how to specify the title for the parameter:

    command  "fooCommand", ["Text"]

I'd really like to implement "required" for parameters of custom commands in my drivers - can someone tell me (us) how this can be accomplished?

[veeceeoh]

@storageanarchy

I'd really like to implement "required" for parameters of custom commands in my drivers - can someone tell me (us) how this can be accomplished?

So you mean you'd like some kind of error to be presented if the user doesn't enter / select the parameter(s)?

Currently the only source of documentation on the command definition / syntax I'm aware of is here:

Requiring Fields for commands

This was intended for documentation but slipped... The command definition in drivers allows now for an optional 3 map to be passed into commands Original code: command "testEnum", ["Enum"] resulted in this: [image] with 2.0 we added support for defining a few things: command "testEnum", [[name:"Testing Enum", type: "ENUM", description: "Pick an option", constraints: ["one","two","three"] ] ] will result in this: [image] What has happened is we have expanded the 2nd parameter to command…

No required parameter functionality is described, so it seems that would have to be handled by the command's method in the driver's code somehow.

[storageanarchy]

Well, that's a help...

Yes - I'm try to ensure the user enters the proper commands in the Hubitat Web Console for the device, should they be testing/trying stuff there.

I wonder what happens if I add a required: true attribute to the command map...I'll try that when I get the chance...

[storageanarchy]

Actually - the answer is in fact in that paragraph you referenced (emphasis mine):

Name is the value that shows up where "ENUM" used to be, directly above the input. If the name ends with an asterisk (*) it will be considered required and the input box will be red and the button will not submit without a value

[veeceeoh]

@storageanarchy

Actually - the answer is in fact in that paragraph you referenced

Clearly I should have read that post a second time! For some reason I thought the asterisk feature was only related to ENUM, but your OP screenshot clearly shows its use with a string. Glad to be of (indirect) help!