Device is not detected or features do not work when Secure Input is enabled

Ideally, Secure Input should only be enabled while the cursor is active in a sensitive information field, such as when you enter a password, and should be disabled right after you leave the password field. However, some applications may leave the Secure Input state enabled. In that case, you may experience the following issues with devices supported by Logi Options+:

• When the device is paired via Bluetooth, it's either not detected by the software or none of the software-assigned features work (basic device functionality will continue to work, however).
• When the device is paired via the USB receiver, it’s not possible to use custom keyboard shortcuts.

If you encounter these issues, check to see if Secure Input is enabled on your system. Do following:

1. Launch Terminal from /Applications/Utilities folder.
2. Type the following command in Terminal and press Enter:
   

   ioreg -l -d 1 -w 0 | grep SecureInput

   • If the command doesn't return any information, then Secure Input is not enabled on the system.
   • If the command returns some information, then look for "kCGSSessionSecureInputPID"=xxxx.
     

     The number xxxx points to the Process ID (PID) of the application that has Secure Input enabled:

     1. Launch Activity Monitor from /Applications/Utilities folder.
     2. Search for PID which has secure input enabled.
     3. Once you know which application has Secure Input enabled, close that application to resolve the issues with Options+.