Bluetooth remote controls
A Bluetooth remote delivers supported control data over a paired wireless relationship, with its profile, host mapping and application context determining available actions.
A Bluetooth remote communicates through a supported wireless/profile relationship rather than relying solely on an optical path to an infrared receiver.
Pairing establishes part of that relationship. The host still needs to understand the remote’s control representation and deliver useful events to the application.
Connection is one layer of compatibility
| Layer | Relationship to establish |
|---|---|
| Wireless connection | Remote and host can establish the supported link |
| Profile/service | Host understands the device’s implemented control arrangement |
| Input mapping | Reports become appropriate host controls |
| Application context | The app recognizes the event in its current view |
Bluetooth SIG’s HID over GATT Profile defines one supported way to carry HID control data over Bluetooth LE. Other Bluetooth HID or vendor-specific arrangements can differ.
A remote being connected does not prove that a voice control, proprietary shortcut or every media key has a mapping in every host.
One handset can contain more than one path
A handset can use infrared for a power command while using Bluetooth for navigation. The TV’s power action may consequently work even when the paired navigation route is unavailable.
The reverse can also occur: navigation reaches the paired host while a power action aimed at another receiver does not.
For Emby, identify which device receives each particular control. A TV remote forwarding an event to an external player introduces an additional host or CEC relationship.
Reports still need state and context
A held control can produce continuing state. The application decides whether that means one action, repeated navigation or a continuous operation.
After a disconnection, stale held-state information should not be treated as a fresh press on a newly available device. The host/app’s reconnection handling supplies that policy.
HID describes how a report’s declared meaning becomes usable input. Gamepad input develops analog state and threshold decisions.
Emby’s keyboard and remote support concerns the later application actions. A useful comparison checks one named button from connection through host recognition to the focused app response.