Tod Kurt

Hmm, well I tried the simple example on the README on my Ubuntu 22 x86 box and while it doesn't panic, it also doesn't seem to actually do anything. Unfortunately,...

I believe the cache is in `$HOME/.electron-gyp` on Mac/Linux and `$env:HOMEPATH\.electron-gyp` on Windows, judging from this line: https://github.com/electron/electron-rebuild/blob/367e08129aea4a3099eb49986f90668e39a142e7/src/rebuild.ts#L397 But often the issue is a bad prebuild from `prebuild-install` so you...

In `hidapi` (the library that `node-hid` wraps), there isn't (yet) an ability to do device plug/unplug detection, so you either check the state of your read/write calls and catch the...

Yeah this is why I typically wrap my reads & writes in `try { } catch {}` blocks to decide programmatically what to do when I/O fails. (as one would...

Correct. If your device uses reportIds, then the length passed to `getFeatureReport()` needs to be one more than the report size. This is how hidapi works, which node-hid is wrapping.

You are not asking for enough bytes for your report. You should ask for 5 bytes. node-hid/hidapi is giving you back the correct size buffer, since it's abiding by the...

No sorry, I mean do this instead: ```js console.log(dev.getFeatureReport(0x04, 5) ```

Hi @hrueger, Unfortunately that stack trace isn't very helpful. The `hid_get_feature_report()` is actually from `hidapi`, of which `node-hid` is a thin wrapper on. But the problem I would say lies...