Appearance
Settings
Each action's settings can be found at the bottom of the Stream Deck software when an action is selected. Settings are split into three tabs: Command, Appearance, and Connection.
Command
The Command tab contains settings specific to the action, such as vehicle type and control mode in this example. See the MAVLink actions section for details on each action's settings.
Appearance
The Appearance tab controls how the button icon looks. Choose from a set of built-in colour palettes or create a custom one. The previews show how the button will appear in each possible connection and vehicle state. Note that not all actions have as many states as shown in this example.
Colour palettes
Three colour palettes are provided, you can also configure custom colours, these can be selected with the palette dropdown.
| State | Dark | High contrast | Fire & Ice |
|---|---|---|---|
| Disconnected |  | | |
| No data |  |  |  |
| Connected inactive |  |  |  |
| Connected unknown |  |  |  |
| Connected active |  |  |  |
Custom colours
There are also two custom colour palettes which allow user selected colours. "Custom global" is a global palette that if changed will affect all actions with that palette selected. Use this if you want all, or most of your actions to have the same colour palette. "Custom instance" allows each action to have different colours, this can be useful to differentiate between actions.
Connection
The Connection tab holds the global MAVLink connection settings shared across all actions. Select a connection type, enter the address and port, and optionally provide a signing key to enable MAVLink packet signing. Use the Connect and Disconnect buttons to manage the connection. See Connecting for more details.
Advanced
The advanced settings are found at the bottom of the Connection tab. They let you configure the MAVLink system and component IDs that KH Control sends from and targets it sends to. By default the target system ID is set automatically to the first system detected after connection. For setups with multiple systems or components, enabling Per instance IDs allows each action to be configured to target a different system and component ID independently. See the custom targets for more details.
