Remote type, code and key assignments
These three settings solve different problems:
| Setting | Responsibility |
|---|---|
| Remote control type under Input Devices | Select a handset type supported by the receiver. |
| Remote control code | Match a supported handset and receiver to a code/code family; this may also separate multiple receivers. |
| Keymap / hotkey | Assign a function to an already recognised button. Does not change the IR code transmitted by the handset. |
Menu → Setup → Usage & GUI → Remote Control Code Settings appears only with suitable hardware support. Available codes and the procedure for changing the handset are manufacturer-dependent. The shared handbook therefore does not prescribe a supposedly universal button sequence.
Before changing anything, read the handset’s manufacturer instructions, note the current setting and check a second control method. Then match receiver and handset codes and use any offered test/confirmation function. A remote-type dialog may offer a timed fallback; rely on it only when the actual dialog explicitly provides it. A GUI switch does not automatically reprogramme an external handset.
Two receivers in one room must both actually support separate codes. Bluetooth/radio pairing, HDMI-CEC and IR codes are different control paths. See HDMI-CEC for TV control through HDMI.
If IR input stops completely, check code/type first. If a recognised key performs the wrong action, check hotkeys and button settings. A skin change does not fix an incorrect IR code.
This conditional entry is described without model-specific assumptions. No remote code was changed on the test receiver.
