macOS cannot open device with some specific paths

[GanZhiXiong]

macOS cannot open device with path IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC1@14/XHC1@14000000/HS03@14300000/USB2.0 Hub@14300000/AppleUSB20Hub@14300000/AppleUSB20HubPort@14310000/HELLOKEY-8F3A4DEAFF1A0D6A@14310000/IOUSBHostInterface@0/IOUSBHostHIDDevice@14310000,0

Using 'node-hid' can open the device on Windows and Linux, but it cannot be opened on macOS.

I've submitted in 'node - hid issue, and discussed this matter todbot, specific can look here: node-hid/node-hid#348

---

I tested it on my colleague's computer today, and found that macOS Mojave 10.14.6 could open the device, but macOS Mojave 10.14.5 could not open the device, I will try to upgrade the system when I have time

[Youw]

As far as I can see in the discussion, your device is a keyboard-like device, and as @todbot already mentioned, you will not be able to open it as a general HID device since macOS won't let you.

If the device is your own development, I'd suggest adding another USB-HID interface to that device with a custom (vendor) HID protocol (or use one of the standard ones, but not a Keyboard), and use it for communication you need.

Without the device itself there is not much we can help you with.

[z3ntu]

Have you maybe tried running your application as root?

[GanZhiXiong]

Have you maybe tried running your application as root?

Even if I run with the 'sudo' command, I can't turn on the device

[GanZhiXiong]

@Youw @z3ntu
In macOS calls HID.Devices(), MacOS there's only one usagePage and one usage for the same device, macOS Device cannot be open.

But you can get two usagePage and two usage on the same device under Windows, and can open device.

This is the device information that you got under Windows

{
   vendorId: 6790,
   productId: 57568,
   path: '\\\\?\\hid#vid_1a86&pid_e0e0&col02#7&83dd5c8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd',      
   serialNumber: '30A31F8ED8F3BFCE',
   manufacturer: 'TJT-USB',
   product: 'test-30A31F8ED8F3BFCE',
   release: 0,
   interface: -1,
   usagePage: 1,
   usage: 6
 },
 {
   vendorId: 6790,
   productId: 57568,
   path: '\\\\?\\hid#vid_1a86&pid_e0e0&col01#7&83dd5c8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}',
   serialNumber: '30A31F8ED8F3BFCE',
   manufacturer: 'TJT-USB',
   product: 'test-30A31F8ED8F3BFCE',
   release: 0,
   interface: -1,
   usagePage: 65280,
   usage: 1
 },

[jdk]

Don’t believe one of my patches has been merged yet. Can you try my fork and let me know if that works? https://github.com/flirc/hidapi Very Sincerely, Jason

…

On Nov 14, 2019, at 10:14 PM, 干志雄 ***@***.***> wrote:  @Youw @z3ntu In macOS calls HID.Devices(), MacOS there's only one usagePage and one usage for the same device, macOS Device cannot be open. But you can get two usagePage and two usage on the same device under Windows, and can open device. This is the device information that you got under Windows { vendorId: 6790, productId: 57568, path: '\\\\?\\hid#vid_1a86&pid_e0e0&col02#7&83dd5c8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd', serialNumber: '30A31F8ED8F3BFCE', manufacturer: 'TJT-USB', product: 'test-30A31F8ED8F3BFCE', release: 0, interface: -1, usagePage: 1, usage: 6 }, { vendorId: 6790, productId: 57568, path: '\\\\?\\hid#vid_1a86&pid_e0e0&col01#7&83dd5c8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}', serialNumber: '30A31F8ED8F3BFCE', manufacturer: 'TJT-USB', product: 'test-30A31F8ED8F3BFCE', release: 0, interface: -1, usagePage: 65280, usage: 1 }, — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[Youw]

@GanZhiXiong macOS merges all usage pages into a single device, if endpoints don't overlap over usage pages, so, as a workaround for now, you may just skip filtering usage page on macOS and open a device by VID/PID/SN only, on macOS.

Once #65 is done - hidapi will report separate devices for different usage pages on macOS. Technically it will be same native device.

[GanZhiXiong]

@jdk Thanks. I use 'node - hid' https://github.com/node-hid/node-hid, I know 'node - hid' use 'hidapi', but I don't know how to use your fork in 'node - hid'.

[todbot]

I’m in the process of updating node-hid to use this updated version. The new version of node-his should be out in a few days. Thanks for your patience! (and thanks to hidapi team for applying all these fixes)

[GanZhiXiong]

@todbot @Youw
Thank you very much. I've been tracking this problem for a few months, and I'm looking forward to the new version of 'node-hid' that solves my problem! Thank you again! 😀 👍

[todbot]

Also, @jdk, can you check libusb/hidapi versus your signal11/hidapi changes? It appears hidapi/mac/hid.c supports interface numbers now.

[jdk]

Yes, will do this tomorrow. I need a series of hubs to help repro this. The original version had interface numbers as well, but the issue happened when we had two many parent hubs and reading our string failed. Will report back. Very Sincerely, Jason

…

On Nov 18, 2019, at 12:53 PM, Tod E. Kurt ***@***.***> wrote: Also, @jdk <https://github.com/jdk>, can you check libusb/hidapi versus your signal11/hidapi changes? It appears hidapi/mac/hid.c supports interface numbers now. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#116?email_source=notifications&email_token=AABKD5RFGNRKJJUJHH6UDLTQUL6F5A5CNFSM4JKR5KO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEL34YQ#issuecomment-555204194>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABKD5TEKKO243FJQ2TFD2DQUL6F5ANCNFSM4JKR5KOQ>.

[GanZhiXiong]

Don’t believe one of my patches has been merged yet. Can you try my fork and let me know if that works? https://github.com/flirc/hidapi Very Sincerely, Jason
…
On Nov 14, 2019, at 10:14 PM, 干志雄 @.***> wrote:  @Youw @z3ntu In macOS calls HID.Devices(), MacOS there's only one usagePage and one usage for the same device, macOS Device cannot be open. But you can get two usagePage and two usage on the same device under Windows, and can open device. This is the device information that you got under Windows { vendorId: 6790, productId: 57568, path: '\\?\hid#vid_1a86&pid_e0e0&col02#7&83dd5c8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd', serialNumber: '30A31F8ED8F3BFCE', manufacturer: 'TJT-USB', product: 'test-30A31F8ED8F3BFCE', release: 0, interface: -1, usagePage: 1, usage: 6 }, { vendorId: 6790, productId: 57568, path: '\\?\hid#vid_1a86&pid_e0e0&col01#7&83dd5c8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}', serialNumber: '30A31F8ED8F3BFCE', manufacturer: 'TJT-USB', product: 'test-30A31F8ED8F3BFCE', release: 0, interface: -1, usagePage: 65280, usage: 1 }, — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

@jdk I use macOS, can you tell me how to operate? What IDE should I use? Commands to execute?

[jdk]

I can confirm that the latest libusb/hidapi code still doesn’t solve the issue. My patch is still needed. I’ll rebase and do a pull request.

…

On Nov 14, 2019, at 10:14 PM, 干志雄 ***@***.***> wrote: @Youw <https://github.com/Youw> @z3ntu <https://github.com/z3ntu> In macOS calls HID.Devices(), MacOS there's only one usagePage and one usage for the same device, macOS Device cannot be open. But you can get two usagePage and two usage on the same device under Windows, and can open device. This is the device information that you got under Windows { vendorId: 6790, productId: 57568, path: '\\\\?\\hid#vid_1a86&pid_e0e0&col02#7&83dd5c8&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd', serialNumber: '30A31F8ED8F3BFCE', manufacturer: 'TJT-USB', product: 'test-30A31F8ED8F3BFCE', release: 0, interface: -1, usagePage: 1, usage: 6 }, { vendorId: 6790, productId: 57568, path: '\\\\?\\hid#vid_1a86&pid_e0e0&col01#7&83dd5c8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}', serialNumber: '30A31F8ED8F3BFCE', manufacturer: 'TJT-USB', product: 'test-30A31F8ED8F3BFCE', release: 0, interface: -1, usagePage: 65280, usage: 1 }, — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#116?email_source=notifications&email_token=AABKD5W23GKR7TTYY7LKEDLQTY43TA5CNFSM4JKR5KO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEENVZQ#issuecomment-554228454>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABKD5U4JLSSXYCEGIH7NH3QTY43TANCNFSM4JKR5KOQ>.