Skip to content

Instantly share code, notes, and snippets.


ukBaz/ Secret

Last active Sep 3, 2022
What would you like to do?
Create a Bluetooth HID server

This was an experiment to turn a Raspberry Pi into a Human Interface Device (HID). A keyboard to be more precise.

I followed the instructions at the following location to get me started:

I wanted to move to Python3 and tidy things up on the Bluetooth side to bring it in to line with current ways things are done in BlueZ.

Configure Raspberry Pi.

These instructions assuming you have BlueZ 5.43 installed. You can check this with:

$ bluetoothctl -v

Ensure Raspberry Pi is at the latest version:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

Check that the packages required for this are installed

sudo apt-get install python3-dbus
sudo pip install evdev

Here is an outline of things I changed:

Moved to Python3

I wanted to do this because not only is it a good thing to do but it also allowed some of the dependancies to be removed. After Python 3.3 Bluetooth sockets are supported in the native Python installs. The downside to this is that there are clear distinctions between str and bytes in the code. For me, this broke the keyboard client. This is what required the biggest re-write to get Python3 working.

Reconfigure the Bluetooth Daemon

The instructions worked that were provided but things have moved on a little bit. To stop the Bluetooth daemon running then the following command is preferred:

sudo service bluetooth stop

The input Bluetooth plugin needs to be removed so that it does not grab the sockets we require access to. As the original author says the way this was documented could be improved. If you want to restart the daemon (without the input plugin) from the command line then the following would seem the preferred:

sudo /usr/lib/bluetooth/bluetoothd -P input

If you want to make this the default for this Raspberry Pi then modify the /lib/systemd/system/bluetooth.service file. You will need to change the Service line from:



ExecStart=/usr/lib/bluetooth/bluetoothd -P input

Configure D-Bus

When a new service is created on the D-Bus, this service needs to be configured.

sudo cp org.yaptb.btkkbservice.conf /etc/dbus-1/system.d

Event loop

The original article used Gtk for the event loop. I changed it to the library that I normally use and this removed the warning the original author was getting.


This command has been deprecated in the BlueZ project.

In the setup of the original article the hciconfig command used to get the BD address. I have modified this so that the code queries the adapter and gets the address.

There were also os.system calls to hciconfig from within the Python. With the new BlueZ D-Bus interface these are unnecessary and have been replaced with D-Bus calls.


Moving to a new version (> 3.3?) of Python will not require the import bluetooth line that was there previously. More information on the Python socket support of Bluetooth is available at:

Registering of Profile

As the original author noted, the registering of the HID profile does not seem to work as documented at: The NewConnection method did not seem to get called on a new connection being made. Requests to the BlueZ mailing list did not seem to yield any insight as to why this is.


With the settings used in this setup the pairing steps described in the original tutorial should not be required. While this is probably not a sensible choice for a real situation, for this experiment I chose convenience over security.

Below is a transcript from the two terminal I had open for this experiment.

Terminal 1

pi@raspberrypi:~/python/bluetooth_hid/btkeyboard/server $ sudo service bluetooth stop
pi@raspberrypi:~/python/bluetooth_hid/btkeyboard/server $ sudo /usr/lib/bluetooth/bluetoothd -P input &
pi@raspberrypi:~/python/bluetooth_hid/btkeyboard/server $ sudo python3
Setting up service
Setting up BT device
Configuring for name BT_HID_Keyboard
Configuring Bluez Profile
Reading service record
Profile registered
Waiting for connections

Scan for the keyboard Pi and connect from main computer

8C:2D:AA:44:0E:3A connected on the control socket
8C:2D:AA:44:0E:3A connected on the interrupt channel

Terminal 2

pi@raspberrypi:~/python/bluetooth_hid/btkeyboard/keyboard $ python3
Setting up keyboard
found a keyboard
starting event loop
Bluetooth HID keyboard emulator DBUS Service
Original idea taken from:
Moved to Python 3 and tested with BlueZ 5.43
import os
import sys
import dbus
import dbus.service
import socket
from gi.repository import GLib
from dbus.mainloop.glib import DBusGMainLoop
class HumanInterfaceDeviceProfile(dbus.service.Object):
BlueZ D-Bus Profile for HID
fd = -1
in_signature='', out_signature='')
def Release(self):
in_signature='oha{sv}', out_signature='')
def NewConnection(self, path, fd, properties):
self.fd = fd.take()
print('NewConnection({}, {})'.format(path, self.fd))
for key in properties.keys():
if key == 'Version' or key == 'Features':
print(' {} = 0x{:04x}'.format(key,
print(' {} = {}'.format(key, properties[key]))
in_signature='o', out_signature='')
def RequestDisconnection(self, path):
print('RequestDisconnection {}'.format(path))
if self.fd > 0:
self.fd = -1
class BTKbDevice:
create a bluetooth device to emulate a HID keyboard
MY_DEV_NAME = 'BT_HID_Keyboard'
# Service port - must match port configured in SDP record
P_CTRL = 17
# Service port - must match port configured in SDP record#Interrrupt port
P_INTR = 19
# BlueZ dbus
PROFILE_DBUS_PATH = '/bluez/yaptb/btkb_profile'
ADAPTER_IFACE = 'org.bluez.Adapter1'
DEVICE_INTERFACE = 'org.bluez.Device1'
DBUS_PROP_IFACE = 'org.freedesktop.DBus.Properties'
DBUS_OM_IFACE = 'org.freedesktop.DBus.ObjectManager'
# file path of the sdp record to laod
install_dir = os.path.dirname(os.path.realpath(__file__))
SDP_RECORD_PATH = os.path.join(install_dir,
# UUID for HID service (1124)
UUID = '00001124-0000-1000-8000-00805f9b34fb'
def __init__(self, hci=0):
self.scontrol = None
self.ccontrol = None # Socket object for control
self.sinterrupt = None
self.cinterrupt = None # Socket object for interrupt
self.dev_path = '/org/bluez/hci{}'.format(hci)
print('Setting up BT device')
self.bus = dbus.SystemBus()
self.adapter_methods = dbus.Interface(
self.adapter_property = dbus.Interface(
print('Configuring for name {}'.format(BTKbDevice.MY_DEV_NAME))
# set the Bluetooth device configuration
self.alias = BTKbDevice.MY_DEV_NAME
self.discoverabletimeout = 0
self.discoverable = True
def interfaces_added(self):
def _properties_changed(self, interface, changed, invalidated, path):
if self.on_disconnect is not None:
if 'Connected' in changed:
if not changed['Connected']:
def on_disconnect(self):
print('The client has been disconnect')
def address(self):
"""Return the adapter MAC address."""
return self.adapter_property.Get(self.ADAPTER_IFACE,
def powered(self):
power state of the Adapter.
return self.adapter_property.Get(self.ADAPTER_IFACE, 'Powered')
def powered(self, new_state):
self.adapter_property.Set(self.ADAPTER_IFACE, 'Powered', new_state)
def alias(self):
return self.adapter_property.Get(self.ADAPTER_IFACE,
def alias(self, new_alias):
def discoverabletimeout(self):
"""Discoverable timeout of the Adapter."""
return self.adapter_props.Get(self.ADAPTER_IFACE,
def discoverabletimeout(self, new_timeout):
def discoverable(self):
"""Discoverable state of the Adapter."""
return self.adapter_props.Get(
self.ADAPTER_INTERFACE, 'Discoverable')
def discoverable(self, new_state):
def config_hid_profile(self):
Setup and register HID Profile
print('Configuring Bluez Profile')
service_record = self.read_sdp_service_record()
opts = {
'Role': 'server',
'RequireAuthentication': False,
'RequireAuthorization': False,
'AutoConnect': True,
'ServiceRecord': service_record,
manager = dbus.Interface(self.bus.get_object('org.bluez',
print('Profile registered ')
def read_sdp_service_record():
Read and return SDP record from a file
:return: (string) SDP record
print('Reading service record')
fh = open(BTKbDevice.SDP_RECORD_PATH, 'r')
except OSError:
sys.exit('Could not open the sdp record. Exiting...')
def listen(self):
Listen for connections coming from HID client
print('Waiting for connections')
self.scontrol = socket.socket(socket.AF_BLUETOOTH,
self.scontrol.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
self.sinterrupt = socket.socket(socket.AF_BLUETOOTH,
self.sinterrupt.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
self.scontrol.bind((self.address, self.P_CTRL))
self.sinterrupt.bind((self.address, self.P_INTR))
# Start listening on the server sockets
self.scontrol.listen(1) # Limit of 1 connection
self.ccontrol, cinfo = self.scontrol.accept()
print('{} connected on the control socket'.format(cinfo[0]))
self.cinterrupt, cinfo = self.sinterrupt.accept()
print('{} connected on the interrupt channel'.format(cinfo[0]))
def send(self, msg):
Send HID message
:param msg: (bytes) HID packet to send
class BTKbService(dbus.service.Object):
Setup of a D-Bus service to recieve HID messages from other
Send the recieved HID messages to the Bluetooth HID server to send
def __init__(self):
print('Setting up service')
bus_name = dbus.service.BusName('org.yaptb.btkbservice',
dbus.service.Object.__init__(self, bus_name, '/org/yaptb/btkbservice')
# create and setup our device
self.device = BTKbDevice()
# start listening for socket connections
def send_keys(self, cmd):
if __name__ == '__main__':
# The sockets require root permission
if not os.geteuid() == 0:
sys.exit('Only root can run this script')
myservice = BTKbService()
mainloop = GLib.MainLoop()
import dbus
import evdev
import keymap
from time import sleep
HID_DBUS = 'org.yaptb.btkbservice'
HID_SRVC = '/org/yaptb/btkbservice'
class Kbrd:
Take the events from a physically attached keyboard and send the
HID messages to the keyboard D-Bus server.
def __init__(self):
self.target_length = 6
self.mod_keys = 0b00000000
self.pressed_keys = []
self.have_kb = False = None
self.bus = dbus.SystemBus()
self.btkobject = self.bus.get_object(HID_DBUS,
self.btk_service = dbus.Interface(self.btkobject,
def wait_for_keyboard(self, event_id=0):
Connect to the input event file for the keyboard.
Can take a parameter of an integer that gets appended to the end of
:param event_id: Optional parameter if the keyboard is not event0
while not self.have_kb:
# try and get a keyboard - should always be event0 as
# we're only plugging one thing in = evdev.InputDevice('/dev/input/event{}'.format(
self.have_kb = True
except OSError:
print('Keyboard not found, waiting 3 seconds and retrying')
print('found a keyboard')
def update_mod_keys(self, mod_key, value):
Which modifier keys are active is stored in an 8 bit number.
Each bit represents a different key. This method takes which bit
and its new value as input
:param mod_key: The value of the bit to be updated with new value
:param value: Binary 1 or 0 depending if pressed or released
bit_mask = 1 << (7-mod_key)
if value: # set bit
self.mod_keys |= bit_mask
else: # clear bit
self.mod_keys &= ~bit_mask
def update_keys(self, norm_key, value):
if value < 1:
elif norm_key not in self.pressed_keys:
self.pressed_keys.insert(0, norm_key)
len_delta = self.target_length - len(self.pressed_keys)
if len_delta < 0:
self.pressed_keys = self.pressed_keys[:len_delta]
elif len_delta > 0:
self.pressed_keys.extend([0] * len_delta)
def state(self):
property with the HID message to send for the current keys pressed
on the keyboards
:return: bytes of HID message
return [0xA1, 0x01, self.mod_keys, 0, *self.pressed_keys]
def send_keys(self):
def event_loop(self):
Loop to check for keyboard events and send HID message
over D-Bus keyboard service when they happen
for event in
# only bother if we hit a key and its an up or down event
if event.type == evdev.ecodes.EV_KEY and event.value < 2:
key_str = evdev.ecodes.KEY[event.code]
mod_key = keymap.modkey(key_str)
if mod_key > -1:
self.update_mod_keys(mod_key, event.value)
self.update_keys(keymap.convert(key_str), event.value)
if __name__ == '__main__':
print('Setting up keyboard')
kb = Kbrd()
print('starting event loop')
# Convert value returned from Linux event device ("evdev") to a HID code.
# This is reverse of what's actually hardcoded in the kernel.
# Lubomir Rintel <>
# License: GPL
# Ported to a Python module by Liam Fraser.
keytable = {
"KEY_ESC": 41,
"KEY_1": 30,
"KEY_2": 31,
"KEY_3": 32,
"KEY_4": 33,
"KEY_5": 34,
"KEY_6": 35,
"KEY_7": 36,
"KEY_8": 37,
"KEY_9": 38,
"KEY_0": 39,
"KEY_MINUS": 45,
"KEY_EQUAL": 46,
"KEY_TAB": 43,
"KEY_Q": 20,
"KEY_W": 26,
"KEY_E": 8,
"KEY_R": 21,
"KEY_T": 23,
"KEY_Y": 28,
"KEY_U": 24,
"KEY_I": 12,
"KEY_O": 18,
"KEY_P": 19,
"KEY_ENTER": 40,
"KEY_A": 4,
"KEY_S": 22,
"KEY_D": 7,
"KEY_F": 9,
"KEY_G": 10,
"KEY_H": 11,
"KEY_J": 13,
"KEY_K": 14,
"KEY_L": 15,
"KEY_GRAVE": 53,
"KEY_Z": 29,
"KEY_X": 27,
"KEY_C": 6,
"KEY_V": 25,
"KEY_B": 5,
"KEY_N": 17,
"KEY_M": 16,
"KEY_COMMA": 54,
"KEY_DOT": 55,
"KEY_SLASH": 56,
"KEY_SPACE": 44,
"KEY_F1": 58,
"KEY_F2": 59,
"KEY_F3": 60,
"KEY_F4": 61,
"KEY_F5": 62,
"KEY_F6": 63,
"KEY_F7": 64,
"KEY_F8": 65,
"KEY_F9": 66,
"KEY_F10": 67,
"KEY_KP7": 95,
"KEY_KP8": 96,
"KEY_KP9": 97,
"KEY_KP4": 92,
"KEY_KP5": 93,
"KEY_KP6": 94,
"KEY_KP1": 89,
"KEY_KP2": 90,
"KEY_KP3": 91,
"KEY_KP0": 98,
"KEY_KPDOT": 99,
"KEY_102ND": 100,
"KEY_F11": 68,
"KEY_F12": 69,
"KEY_RO": 135,
"KEY_HENKAN": 138,
"KEY_SYSRQ": 70,
"KEY_HOME": 74,
"KEY_UP": 82,
"KEY_LEFT": 80,
"KEY_RIGHT": 79,
"KEY_END": 77,
"KEY_DOWN": 81,
"KEY_MUTE": 239,
"KEY_POWER": 102,
"KEY_PAUSE": 72,
"KEY_HANJA": 145,
"KEY_YEN": 137,
"KEY_STOP": 243,
"KEY_AGAIN": 121,
"KEY_PROPS": 118,
"KEY_UNDO": 122,
"KEY_FRONT": 119,
"KEY_COPY": 124,
"KEY_OPEN": 116,
"KEY_PASTE": 125,
"KEY_FIND": 244,
"KEY_CUT": 123,
"KEY_HELP": 117,
"KEY_CALC": 251,
"KEY_SLEEP": 248,
"KEY_WWW": 240,
"KEY_COFFEE": 249,
"KEY_BACK": 241,
"KEY_STOPCD": 233,
"KEY_EDIT": 247,
"KEY_F13": 104,
"KEY_F14": 105,
"KEY_F15": 106,
"KEY_F16": 107,
"KEY_F17": 108,
"KEY_F18": 109,
"KEY_F19": 110,
"KEY_F20": 111,
"KEY_F21": 112,
"KEY_F22": 113,
"KEY_F23": 114,
"KEY_F24": 115
# Map modifier keys to array element in the bit array
modkeys = {
def convert(evdev_keycode):
return keytable[evdev_keycode]
def modkey(evdev_keycode):
if evdev_keycode in modkeys:
return modkeys[evdev_keycode]
return -1 # Return an invalid array element
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
<policy context="default">
<allow own="org.yaptb.btkbservice"/>
<allow send_destination="org.yaptb.btkbservice"/>
<?xml version="1.0" encoding="UTF-8" ?>
<attribute id="0x0001">
<uuid value="0x1124" />
<attribute id="0x0004">
<uuid value="0x0100" />
<uint16 value="0x0011" />
<uuid value="0x0011" />
<attribute id="0x0005">
<uuid value="0x1002" />
<attribute id="0x0006">
<uint16 value="0x656e" />
<uint16 value="0x006a" />
<uint16 value="0x0100" />
<attribute id="0x0009">
<uuid value="0x1124" />
<uint16 value="0x0100" />
<attribute id="0x000d">
<uuid value="0x0100" />
<uint16 value="0x0013" />
<uuid value="0x0011" />
<attribute id="0x0100">
<text value="Raspberry Pi Virtual Keyboard" />
<attribute id="0x0101">
<text value="USB > BT Keyboard" />
<attribute id="0x0102">
<text value="Raspberry Pi" />
<attribute id="0x0200">
<uint16 value="0x0100" />
<attribute id="0x0201">
<uint16 value="0x0111" />
<attribute id="0x0202">
<uint8 value="0x40" />
<attribute id="0x0203">
<uint8 value="0x00" />
<attribute id="0x0204">
<boolean value="false" />
<attribute id="0x0205">
<boolean value="false" />
<attribute id="0x0206">
<uint8 value="0x22" />
<text encoding="hex" value="05010906a101850175019508050719e029e715002501810295017508810395057501050819012905910295017503910395067508150026ff000507190029ff8100c0050c0901a1018503150025017501950b0a23020a21020ab10109b809b609cd09b509e209ea09e9093081029501750d8103c0" />
<attribute id="0x0207">
<uint16 value="0x0409" />
<uint16 value="0x0100" />
<attribute id="0x020b">
<uint16 value="0x0100" />
<attribute id="0x020c">
<uint16 value="0x0c80" />
<attribute id="0x020d">
<boolean value="true" />
<attribute id="0x020e">
<boolean value="false" />
<attribute id="0x020f">
<uint16 value="0x0640" />
<attribute id="0x0210">
<uint16 value="0x0320" />
Copy link

ukBaz commented Apr 3, 2021

@HeadHodge has created an example that uses the newer HID over GATT Profile (HOGP) and thought it might be a useful reference for people:

Copy link

ackerleytng commented Sep 28, 2021

I'm trying to follow this guide to build a bluetooth "keyboard" that is able to send a few keystrokes, such as the equivalent of alt-tab, to my Android phone.

So far, I've been able to

  • Register a profile through org.bluez.ProfileManager1.RegisterProfile with an sdp_record.xml that I'm not sure is completely correct
  • Register a service through org.bluez.Profile1 that exports a few methods

I would start the program on my laptop (linux), which does the above 2 registrations, and then use bluetoothctl to manually do discoverable on, and then get my Android phone to pair with the laptop. Pairing is successful, but the service, which listens on ports 0x11 and 0x13, never seem to receive any connections. accept() is never called.

Is my overall understanding right? The laptop, acting as the bluetooth keyboard, will serve a profile and a service (SDP), that the phone will read. When it tries to pair with the laptop, it will read the ports listed in the profile and attempt to connect to those ports?

Any ideas on where I can start debugging?

Copy link

ukBaz commented Sep 28, 2021

The general advice I give to get Bluetooth debug information on Linux is the following.

When running your script have separate terminals open with the following running to get more debug information:

  • bluetootctl
  • journalctl -f -u bluetooth
  • sudo busctl monitor org.bluez
  • sudo btmon

Your general understanding sounds correct but the trouble is always in the detail. You don't mention about re-configuring the bluetooth daemon which is a very important step. Does your laptop show up as a keyboard after you have paired the two devices?

Copy link

ackerleytng commented Sep 28, 2021

Thank you soooo much! You hit the nail on the head!

I'm trying to reproduce this in golang.

When binding, I initially didn't specify the address to bind to. Binding succeeded, but I'm also not sure which interface it was binding to, and there was no EADDRINUSE error. If I read and use the org.bluez.Adapter1 Address read from /org/bluez/hci0, then I start getting the EADDRINUSE error.

I definitely needed to reconfigure the bluetooth daemon to remove the default input plugin by stopping bluetoothd and then restarting it as follows

sudo /usr/lib/bluetooth/bluetoothd --noplugin input

(--noplugin is the same as -P documented above)

Thanks once again!

Copy link

TehseenHasan commented Oct 5, 2021

I followed the procedure and Now My PC is connected to the Bluetooth of the Raspberry Pi Zero W. Terminal 1 is showing this :

>>> %cd /home/pi/Desktop/BluetoothHID
>>> %Run
Setting up service
Setting up BT device
Configuring for name BT_HID_Keyboard
Configuring Bluez Profile
Reading service record
Profile registered 
Waiting for connections
D8:0F:99:73:BC:14 connected on the control socket
D8:0F:99:73:BC:14 connected on the interrupt channel

But when I run the it is giving this error:

sudo python3
Setting up keyboard
Keyboard not found, waiting 3 seconds and retrying
found a keyboard
Keyboard not found, waiting 3 seconds and retrying
found a keyboard
Keyboard not found, waiting 3 seconds and retrying
found a keyboard
Keyboard not found, waiting 3 seconds and retrying

and So on......

I am using my Raspberry Pi through VNC Server and there are no Physical Keyboard or Mouse is attached to the Rasberry Pi USB port.

I want to send the text data from my Custom python Code to the PC over Bluetooth HID. It seems that in your code you are trying to detect a physical keyboard attached to the RPi and then sending its keystrokes over the Bluetooth.

But I just need to send a custom string from my python code, not from the keyboard. Please guide me on how can I do this. Thanks a lot!


for testing, I just connected a USB keyboard to my Raspberry Pi Zero W and then run sudo python3 and now It is working perfectly and I am receiving the keystrokes from the Raspberry Pi's keyboard to my PC over Bluetooth HID.

Now my only question is that how can I send the custom string data through my python code instead of using a physical keyboard.?

Copy link

ukBaz commented Oct 5, 2021

@TehseenHasan, this kind of question has been asked further up in this gist. I think it starts about here

Copy link

joyobooto commented Oct 8, 2021

Is there a plan to get mouse support working? I've found a similar project which I'm trying to migrate over but my knowledge over the libraries used is limiting me a little...

Copy link

HeadHodge commented Oct 8, 2021

you can use your existing code by modifying your sdp file to add a second usb hid report descriptor for a mouse.

it takes effort, but this tool helps:

once the report descriptor is modified, you send reports for either the keyboard or mouse by specifying the correct report id in your reports.

Here is an example of a report descriptor i made, that works well, that has 3 reports for a keyboard, mouse and consumer device.

//Report Reference Id = 1 (128 key Keyboard)
//Modifier Byte: bit 0 is L CTRL, bit 1 is L SHIFT, bit 2 is L ALT, bit 3 is L GUI, bit 4 is R CTRL, bit 5 is R SHIFT, bit 6 is R ALT, and bit 7 is R GUI
0x05, 0x01, 	  // Usage Page (Generic Desktop Ctrls)
0x09, 0x06, 	  // Usage (Keyboard)
0xa1, 0x01, 	  // Collection (Application)
0x85, 0x01, 	  //   Report ID (1)
0x05, 0x07, 	  //   Usage Page (Kbrd/Keypad)
0x19, 0xe0, 	  //   Usage Minimum (0xE0)
0x29, 0xe7, 	  //   Usage Maximum (0xE7)
0x15, 0x00, 	  //   Logical Minimum (0)
0x25, 0x01, 	  //   Logical Maximum (1)
0x75, 0x01, 	  //   Report Size (1)
0x95, 0x08, 	  //   Report Count (8)
0x81, 0x02, 	  //   Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x95, 0x01, 	  //   Report Count (1)
0x75, 0x08, 	  //   Report Size (8)
0x15, 0x00, 	  //   Logical Minimum (0)
0x25, 0x65, 	  //   Logical Maximum (101)
0x05, 0x07, 	  //   Usage Page (Kbrd/Keypad)
0x19, 0x00, 	  //   Usage Minimum (0x00)
0x29, 0x65, 	  //   Usage Maximum (0x65)
0x81, 0x00, 	  //   Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position)
0xc0,			  // End Collection

//Report Reference Id = 2 (Consumer Entertainment Control)
0x05, 0x0C, 	  // Usage Page (Consumer)
0x09, 0x01, 	  // Usage (Consumer Control)
0xA1, 0x01, 	  // Collection (Application)
0x85, 0x02, 	  //   Report ID (2)
0x75, 0x10, 	  //   Report Size (16)
0x95, 0x01, 	  //   Report Count (1)
0x15, 0x01,		  //   Logical Minimum (1)
0x26, 0xff, 0x07, //   Logical Maximum (2047)
0x19, 0x01, 	  //   Usage Minimum (Consumer Control)
0x2A, 0xff, 0x07, //   Usage Maximum (0x07FF)
0x81, 0x00, 	  //   Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position)
0xC0, 	  	  	  // End Collection

//Report Reference Id = 3 (Generic Mouse)
0x05, 0x01,       // Usage Page (Generic Desktop Ctrls)
0x09, 0x02,       // Usage (Mouse)
0xA1, 0x01,       // Collection (Application)
0x85, 0x03, 	  //   Report ID (3)
0x09, 0x01,       //   Usage (Pointer)
0xA1, 0x00,       //   Collection (Physical)
0x05, 0x09,       //     Usage Page (Button)
0x19, 0x01,       //     Usage Minimum (0x01)
0x29, 0x03,       //     Usage Maximum (0x03)
0x15, 0x00,       //     Logical Minimum (0)
0x25, 0x01,       //     Logical Maximum (1)
0x95, 0x03,       //     Report Count (3)
0x75, 0x01,       //     Report Size (1)
0x81, 0x02,       //     Input (Data,Var,Abs,No Wrap,Linear,...)
0x95, 0x01,       //     Report Count (1)
0x75, 0x05,       //     Report Size (5)
0x81, 0x03,       //     Input (Const,Var,Abs,No Wrap,Linear,...)
0x05, 0x01,       //     Usage Page (Generic Desktop Ctrls)
0x09, 0x30,       //     Usage (X)
0x09, 0x31,       //     Usage (Y)
0x15, 0x81,       //     Logical Minimum (-127)
0x25, 0x7F,       //     Logical Maximum (127)
0x75, 0x08,       //     Report Size (8)
0x95, 0x02,       //     Report Count (2)
0x81, 0x06,       //     Input (Data,Var,Rel,No Wrap,Linear,...)
0xC0,             //   End Collection
0xC0,             // End Collection

Copy link

joyobooto commented Oct 11, 2021

Thanks, I've made a little progress (just getting mouse buttons working). Wondering if you have a code sample on how you sent using your report descriptor? My modifications for the mouse client detect buttons correctly but when I send button info, it triggers media keys for reasons I do not know yet...

Copy link

HeadHodge commented Oct 11, 2021


i don't use bt 3.0 classic any longer, just bt 4.2 or bt 5.0, so don't have any good code snips for you.

looking at report 3 (mouse) above, the report code boils down to a report of 3 bytes.

byte 1: uses 1st 3 bits of the byte to determine button presses. 0-no buttons, 1-left button, 2-right button, 3-center button. the remaining bits of the byte are ignored.

byte 2: X-axis cursor relative offset movement from current cursor location.

byte 3: Y-axis cursor relative offset movement from current cursor location.

this is from memory but example use something like:

    elif(reportNum == 3):    
        #Send Report #3
        print('SEND Report 3')
        #Send Report #3
        await loop.sock_sendall(options['connection'], bytes([ 0xA1, reportNum, buttons, x-axis, y-axis ]))
        await asyncio.sleep(hold)  
        await loop.sock_sendall(options['connection'], bytes([ 0xA1, reportNum, 0, 0, 0 ]))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment