https://bugs.winehq.org/show_bug.cgi?id=44279
--- Comment #6 from epigramx@yahoo.com --- A relatively important update: I figured the PID and VID returned by wine is erroneously of the adapter's instead of the device's (as it should be as it is listed on windows on the same tool). However, the same pid/vid (of the adapter's) can be found in /sys per these instructions: http://www.signal11.us/oss/udev/ but as I said before querying /dev/hidrawX does return the correct device id (code for that querying is included in another post here). My guess at the moment is that there is either a bug with udevlib or/and /sys or there is a better way to use udevlib for bluetooth devices.