Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

(Windows 10) Chrome.hid.getDevices doesn't work if the device is a hid usb keyboard

See original GitHub issue

Could you change the filter to detect the hid devices? I have download the hidapi project and in the hid_enumerate function in hid.c you can remove the line if (strcmp(driver_name, "HIDClass") (https://github.com/signal11/hidapi/issues/290) and after that the device is detected and working well. Could you do something to solve that? You could do an only search via vendorid, serialnumber… Or including the same filter than usb class (the chrome.usb.getDevices detects the device well) … Or open the device via path hid_open_path (http://www.signal11.us/oss/hidapi/hidapi/doxygen/html/group__API.html)? @reillyeon @beaufortfrancois

Issue Analytics

State:
Created 7 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

danicomascommented, Jan 21, 2017

Opened a request to add a function to connect via local device path as do other hid devices https://github.com/GoogleChrome/chrome-app-samples/issues/466.

0reactions

danicomascommented, Jan 23, 2017

I have found that if you are doing strcmp(driver_name, "HIDClass")… In windows 10 the driver name is the name instead than the driver class. @reillyeon

https://github.com/signal11/hidapi/pull/291/files/f453bda38ff17ea28b7b1d59afd8d09e74e5efb5#diff-8162c58f4630fb0f3a6a21f2e094e883L354