Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

macOS cannot open device with some specific paths #116

Closed
GanZhiXiong opened this issue Nov 8, 2019 · 31 comments
Closed

macOS cannot open device with some specific paths #116

GanZhiXiong opened this issue Nov 8, 2019 · 31 comments
Labels
macOS Related to macOS backend

Comments

@GanZhiXiong
Copy link

GanZhiXiong commented Nov 8, 2019 •
edited by mcuee
Loading

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 Youw added the macOS Related to macOS backend label Nov 8, 2019
@Youw
Copy link
Member

Youw commented Nov 8, 2019

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
Copy link
Collaborator

z3ntu commented Nov 8, 2019

Have you maybe tried running your application as root?

@GanZhiXiong
Copy link
Author

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
Copy link
Author

@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
Copy link

jdk commented Nov 15, 2019 via email

@Youw Youw mentioned this issue Nov 15, 2019
Closed
@Youw
Copy link
Member

Youw commented Nov 15, 2019

@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
Copy link
Author

@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
Copy link
Contributor

todbot commented Nov 18, 2019

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
Copy link
Author

@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
Copy link
Contributor

todbot commented Nov 18, 2019

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

@jdk
Copy link

jdk commented Nov 18, 2019 via email

@GanZhiXiong
Copy link
Author

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
Copy link

jdk commented Nov 25, 2019 via email

@todbot
Copy link
Contributor

todbot commented Nov 25, 2019

Hi @jdk, the hidapi PR is #65 if you haven't seen it already. I'm not sure why it was closed, I was getting ready to make the changes requested but I won't be able to get to it until Weds. If you're quick with git, I think one could knock it out quickly.

@Youw
Copy link
Member

Youw commented Nov 25, 2019

Wow, it appears I closed it 2 day ago, but I definitely didn't mean to.
Maybe I pressed "Close and comment" instead of "Comment" by accident, when giving you an answer.

The patch is still welcome anyway.

@jdk
Copy link

jdk commented Nov 25, 2019

For clarification, #65 may solve another issue. The patch in my branch wasn't specifically for a usage table, but may be related if a device interface can not be found. The original issue for my patch was: signal11/hidapi#301

signal11/hidapi#301 is long standing and patches to address were:
flirc/hidapi@8d251c3
and
flirc/hidapi@a4dd0f3

Issue signal11/hidapi#301 is still present on our current top of tree. I will rebase these patches this week and submit a pull request.

@Youw
Copy link
Member

Youw commented Nov 25, 2019

it seems that a variation of flirc/hidapi@a4dd0f3 is already in master

as for flirc/hidapi@8d251c3 - I think it is not related to #65
and worth a separate discussion (e.g., how to reproduce the original issue it tries to solve)

@mcuee mcuee changed the title 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 macOS cannot open device with some specific paths Nov 29, 2019
@epegzz
Copy link

epegzz commented Mar 24, 2020

I've been tracking this issue for a while now, as I'm having the same issue.

Trying to use hidapi to talk to Elgato Stream Deck

[ { model: 'xl',
    path: 'IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG2@1,2/IOPP/UPSB@0/IOPP/DSB1@1/IOPP/UPS0@0/IOPP/pci-bridge@0/IOPP/pci1b73,1100@0/AppleUSBXHCIFL1100@02000000/AppleUSB20XHCIPort@02200000/Stream Deck XL@02200000/IOUSBHostInterface@0/AppleUserUSBHostHIDDevice',
    serialNumber: 'CL18I1A01810' } ]

I lost a bit track of the status though. Is there any pending PR that may solve the issue? :)

@Youw
Copy link
Member

Youw commented Mar 24, 2020

Not right now.
If your device is a keyboard-like device - there might even not be a solution for it, if it is under a limitation of the OS security policies.

@epegzz
Copy link

epegzz commented Mar 26, 2020 •
edited
Loading

Yeah, I guess the Stream Deck is keyboard like, as it has mainly keyUp and keyDown events. But I'd also assume you would be able to grant those (accessibility?) MacOS permissions to the program that's using the hidapi though, no?

@Youw
Copy link
Member

Youw commented Mar 26, 2020 •
edited
Loading

Not sure regarding accessibility, never tried.

Not having access a keyboard input events is a general security concern, since if any app could just open a keyboard and read all input, it could simply steal your input the data, like your password/card pin etc.

For key Up/Down events more reliable approach is to use native input event hooks, but those work only when your application is active/have a window.

What exactly are you trying to achieve? Is this your device (you developing it) or do you want to use an existing device?

@epegzz
Copy link

epegzz commented Mar 26, 2020

I am using node-hid, so I tried adding sh, zsh, node to this list here, but without success:

System Preferences 2020-03-26 at 14 59 53

What exactly are you trying to achieve? Is this your device (you developing it) or do you want to use an existing device?

I want to handle keyUp and keyDown inside a custom NodeJS app instead of using the proprietary app that comes with the device.

However, I gave up on HIDAPI yesterday and am now hooking into their plugin system and send all events from via WebSocket to my node app from there. It was a bit more pain to code, but since it's done now, I'll not pursue the original approach further.

However, I'll be happy to test and debug if that helps! :)

@Youw
Copy link
Member

Youw commented Mar 26, 2020

the proprietary app that comes with the device

that is likely an easier solution to actually get it done

@bridgewaterrobbie
Copy link

Is there a way to capture a keyboard device with HIDAPI if I am fine with the restriction that the app be focused?

I would prefer to stick with this library rather than native hooks since it is easily cross platform, and I'd prefer to use raw HID packets (My plan is to forward them to a second device and send them into a virtual HID device, so that it is "extended")

If this deserves another issue due to the focus on the Stream deck, I can split mine out, but this came up in my searching. Thanks.

@todbot
Copy link
Contributor

todbot commented Apr 7, 2020 •
edited
Loading

It doesn't matter the state of the app, the OS "owns" keyboards and mice for security reasons.
If your app is focussed and you're just looking for keypresses, use standard key reading techniques of either Node or Electron (or whatever language you're using)

If you're trying to control the non-keyboard parts of a keyboard-like device, it's almost guaranteed the device exposes an alternate usage/usagePage, interface number, or entire interface. You should be able to see the first two HID.devices() as devices with the same VID/PID but different usages/usagePages or interface numbers. If you're curious about usage pages, check out https://www.usb.org/sites/default/files/documents/hut1_12v2.pdf

If you're looking to write an interface to the Streamdeck, I recommend checking out the work done here and cribbing from it: https://github.com/Lange/node-elgato-stream-deck

@bridgewaterrobbie
Copy link

Thank you Tod. I am wanting the keyboard parts, so in that case I think my best bet is to reconstruct HID-like packets from the standard key reading techniques.

@fedecaccia
Copy link

Have you got a solution? Im facing the same problem using @ledgerhq/hw-transport-node-hid lib to connect with nano ledger device

@mcuee
Copy link
Member

mcuee commented Jun 19, 2021

I see that node-hid/node-hid#348 has been closed. What about this #116?

@mcuee
Copy link
Member

mcuee commented Aug 31, 2021

@GanZhiXiong Can you give latest git a try?

@mcuee
Copy link
Member

mcuee commented Aug 31, 2021

@fedecaccia Have you tried plain hidapi?

@Youw
Copy link
Member

Youw commented May 16, 2022

This should have been fixed as of #322.

@Youw Youw closed this as completed May 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
macOS Related to macOS backend
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@jdk @todbot @epegzz @mcuee @z3ntu @bridgewaterrobbie @Youw @fedecaccia @GanZhiXiong