Passkey module

Use the passkey module to handle numeric passkey input. The input handling is based on button presses.

Module events

Source Module	Input Event	This Module	Output Event	Sink Module
Buttons module	button_event	passkey
Button simulator module
Function key module
Source modules for module_state_event	module_state_event
Bluetooth LE passkey module	passkey_req_event
			module_state_event	Sink modules for module_state_event
			passkey_input_event	Bluetooth LE passkey module

Note

See the Overview: Firmware architecture for more information about the event-based communication in the nRF Desktop application and about how to read this table.

Configuration

The passkey input handling is based on button_event.

To configure the passkey module, complete the following steps:

1. Enable and configure the CAF: Buttons module.

2. Enable the passkey module by using the CONFIG_DESKTOP_PASSKEY_BUTTONS Kconfig option.

3. Define the maximum number of digits in the passkey by using the CONFIG_DESKTOP_PASSKEY_MAX_LEN option.

4. Define the IDs of the keys used by the passkey module in the passkey_buttons_def.h file located in the board-specific directory in the configuration directory. You must define the IDs of the following keys:

   • Keys used to input the digits.

   • Keys used to confirm the input.

   • Keys used to remove the last digit (short-press removes only the last digit, but if the key is held for longer than 2 seconds, the whole input is cleared).

   You can define multiple sets of keys used to input the digits, but every set should contain keys used to input every digit. This is to ensure that the user will be able to input the passkey. The index of the key ID in the input configuration array represents the digit.

The example configuration of the module can be found in the configuration/nrf52kbd_nrf52832/passkey_buttons_def.h file.

Implementation details

The passkey module reacts to passkey_req_event by switching between the idle and the active state:

• The user input is handled only in the active state. Key presses are remembered in an array.

• When the input is confirmed, the passkey_input_event that contains the user input is submitted and the module switches to the idle state.