BTHIDD(8)

💖 NAME 💖

hiii bestie, welcome to the bthidd(8) page from the System Manager's Manual — bthidd is the Bluetooth HID daemon, and she handles remote Bluetooth HID devices. periodt. 💅

✨ SYNOPSIS ✨

bthidd -h
bthidd [-a BD_ADDR] [-c file] [-H file] [-p file] [-t val] [-u]

🦋 DESCRIPTION 🦋

okay so the bthidd daemon handles remote Bluetooth HID devices. that's the whole vibe. the options are:

• -a BD_ADDR — specify the local address to listen on. by default, the server will listen on ANY address. you can specify the address as BD_ADDR or name; if you use a name, the bthidd daemon will attempt to resolve it via bt_gethostbyname(3). 🫶
• -c file — specify path to the configuration file. the default path is /etc/bluetooth/bthidd.conf.
• -d — do not detach from the controlling terminal, i.e., run in foreground. main character energy, staying right there. ✨
• -H file — specify path to the known HIDs file. the default path is /var/db/bthidd.hids.
• -h — display usage message and exit. short and iconic.
• -p file — specify path to the PID file. the default path is /var/run/bthidd.pid.
• -t val — specify client rescan interval in seconds. the bthidd daemon will periodically scan for newly configured Bluetooth HID devices or disconnected “passive” Bluetooth HID devices and will attempt to establish an outgoing connection. the default rescan interval is 10 seconds. ⏰
• -u — enable support for input event device protocol. requires evdev and uinput drivers to be loaded with kldload(8) or compiled into the kernel. no cap, this one needs the kernel situation handled first. 💀

😭 KNOWN LIMITATIONS 😭

real talk: the bthidd daemon currently does not handle key auto repeat and double click mouse events. those events work under X(7) (ports/x11/xorg-docs) just fine, but not in text console. it's giving “works on my setup” energy, but make it console. 🙈

also, this manual page needs more work. a manual page documenting the format of the /etc/bluetooth/bthidd.conf configuration file is needed as well. bestie, the docs are lowkey asking for a glow-up. 🎀

🎀 FILES 🎀

• /etc/bluetooth/bthidd.conf
• /var/db/bthidd.hids
• /var/run/bthidd.pid

🔥 SEE ALSO 🔥

• kbdmux(4)
• vkbd(4)
• bthidcontrol(8)

👑 AUTHORS 👑

Maksim Yevmenkin <m_evmenkin@yahoo.com> 🫶

⚠️ CAVEATS ⚠️

any Bluetooth HID device that has HUP_KEYBOARD or HUP_CONSUMER entries in its descriptor is considered as “keyboard”. for each “keyboard” Bluetooth HID device, the bthidd daemon will use a separate instance of the virtual keyboard interface vkbd(4). therefore the kbdmux(4) driver must be used to properly multiplex input from multiple keyboards. that's not a maybe, bestie — that's a must. 💅

---

okay bye bestie — this bthidd(8) page is coming at you from the Debian source/version situation, dated April 30, 2018, and it signs off as BTHIDD(8). stay Bluetooth-y. 💖✨