# Required arguments on device flows

**URL:** <https://community.homey.app/t/required-arguments-on-device-flows/66619>\
**Category:** Developers\
**Tags:** flow\
**Created:** [July 28, 2022, 12:56pm UTC](https://community.homey.app/t/required-arguments-on-device-flows/66619 "2022-07-28T12:56:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Monique\_Jilesen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/monique_jilesen/32/48184_2.png) [@Monique\_Jilesen](https://community.homey.app/u/Monique_Jilesen)\
**Post date:** [July 28, 2022, 12:56pm UTC](https://community.homey.app/t/required-arguments-on-device-flows/66619/1 "2022-07-28T12:56:22Z")

</div>

I have added actions to driver.flow.compose.json and I would like some arguments to be optional. Like described for non-device specific action flows, I have added “required”:false to the JSON definition:

“actions”: [  
{  
“id”: “SetMode”,  
“title”: { “en”: “Set mode”,  
“nl”: “Zet mode” },  
“titleFormatted”: { “en”: “Set mode to [[acMode]], merit A to [[meritA]] and merit B to [[meritB]]”,  
“nl”: “Zet mode naar [[acMode]], merit A naar [[meritA]] en merit B naar [[meritB]]” },  
“$filter”: “capabilities=target\_ac\_mode1|target\_ac\_mode2|target\_ac\_mode3”,  
“args”: [  
{  
“name”: “acMode”,  
“type”: “autocomplete”,  
“title”:{“en”:“Mode”, “nl”: “Mode”}  
},  
{  
“type”: “autocomplete”,  
“name”: “meritA”,  
“required”:false,  
“title”:{“en”:“Merit A”, “nl”: “Merit A”}  
},  
{  
“type”: “autocomplete”,  
“name”: “meritB”,  
“required”:false,  
“title”:{“en”:“Merit B”, “nl”: “Merit B”}  
}  
]  
},

Everything works, except the “required” option. When defining the flow, both meritA en meritB arguments need to have a value.  
Is this bug/not existing feature in Homey or am I doing something wrong?

Note: it does work on the web interface, so it looks like a bug in the app. Does anybody know how to register a bug for Homey?