Typically, each driver has a command that performs the desired function.

While editing the Launch of a Flow, use the "Test" option to verify the input command (or any other function you need) prior to adding to the Flow.

Drivers are always written to cover a whole line of models from a given brand. The uses the command names defined by that brand's API (application programming interface). 

While all of the models from a brand may share the same API, the labels applied to each model will often differ from the name in the API. This is especially common with AVR inputs. This is a common pattern among most manufacturers.

You should expect that input commands will sometimes not match the label on the actual device. What matters is whether AVA OS has a command to perform the switching correctly. If the commands exist to allow a Flow to control a device correctly, your client will never see that the driver command based on the API does not match the label on the device.