I am actually hoping they thought about a way the dropdownfields in flowcards are update too.
But yeah, else using autocomplete would do the trick yeah.
AFAIK you can’t change Flowcards for custom capabilities, but autocomplete would still work fine (only thing that you’ll miss is tag selection)
FYI - I use the Tuyal Local app by @Andi and that app allows me to set custom labels/entries for picker lists. The flowcards then also show those custom labels in their pull down menu. Maybe you could get inspiration from @Andi‘s implementation 
.
But you can’t select a tag as the item, right? This means it uses autocomplete, which means the items that are shown are returned from the Homey app (backend). The advantage of this is that you can return any entry, and also first check with a server for example (the Spotify app uses it to get playlists, and the Olisto app uses it to get a list of Now buttons), however it does take a bit longer to load since the autocompletion has to be done on Homey first before it returns any items.
Not sure if I understand you correctly, but - as far as I can see - I can. Just for illustration. The respective device I control via the Tuya Local app is an airconditioner. It uses a picker list for the Mode and Fan Speed.
I can set the possible values in the device’s settings screen:
The flowcards for both setting the Mode and Fan Speed list these custom items in the menu that appears when clicking the respective parameter field in those cards.
Both the Mode and Fan Speed values are also available as tags:
This is an autocomplete field. Dropdown fields have a tag icon next to them so that you can insert a tag instead of pre-defining an option
Ah right, so you mean that you can select/insert a tag in the (in this case) Mode and Fan Speed flowcards, instead of only being able select/insert the actual values. In that case you are right: I need to select one of the available values and cannot inset a variable/tag holding that value.
Yes, that’s what I mean. Usually you use autocomplete fields if you need to fetch the items of the list from a server (f.e. my Olisto app uses this for the Now buttons and Triggs). Since each autocompletion has to be performed on the Homey app itself (and in most cases also fetched from the manufacturer’s server), it takes a bit longer to load the items
Hi,
great powerfull app!
Would it be possible to get the following ‘prefixed list’:
off, auto, heater, water
kind regards,
Floris
Hey @Arie_J_Godschalk
Have you been able to look at this generic/configurable list at all?
It would be extremely useful and helpful, and greatly appreciated. Thank you.
EDIT: I don’t know who marked this as the 
Solution but behave yourself, this is a question to the developer, and definitely not the solution 
you can make a custom picker for me?
EV charge target / EV-laaddoel
Auto | 80% | 90% | 100%
EV charging deadline / EV-laaddeadline
None | 07:00 | 12:00 | 18:00 | 23:00
Please check the first post on how to request a picker (and what info/which format is expected).
I requested one in the requested format on 9th June… not sure they will get done even if in the correct format to be honest. We even had that discussion on how to achieve a generic list that users could name the entries for, to save having to request custom ones a couple months ago
I am still hoping for the functionality that you can define your own picker. If I am correct that is still the intention of the developer, but also understand he is currently struggling with some health issues. So we have to wait and hope he recovers soon.
Yes, its a work in progress, but not finished yet.
@Arie_J_Godschalk thank you kindly for the update good sir.
In the test version of the app, you can now create your own custom lists in the App Settings and select them in the AVD.
Hi Arie @Arie_J_Godschalk
This is most spectacular news. You have made my day good sir, and made it a very good one 
Thank you!!
EDIT: Hit a bit of a snag, at least for my use case. The Custom Lists don’t seem to give you the option to create Flow cards, to use the list entries to trigger actions within Flows.
Well, for all field types there are flowcards, also for (custom) lists, as shown by @Peter_Kawa .
But the “create real fields and flowcards” option is only available for default homey capabilities/properties. You sometimes need those so Homey recognises the device (capabilities) as a specific device.
For instance, if you add all thermostat capabilities and check all Create real fields and capabilities, then that device will also show up in homey climate and you will get certain build in default homey flowcards.
Custom lists cannot serve that purpose.
However, I plan on making it possible with Custom lists to overrule default capabilities, for instance the thermostat_mode capability, so you can have Custom modes, but have it still be recognised as a real thermostat.
But there are always flowcards to set the fields 
