We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Hi all - Reported this on the James' support forum few years back but never got any resolution, so I thought I'd try again here as well.
The following code hitting a specific vendor's UPS devices:
var devices = DeviceList.Local.GetHidDevices(4271).ToList(); var serialNumber = devices[0].GetSerialNumber();
Throws a DeviceIoException ("Serial Number Not Found") on MacOS, but works fine on Windows and Linux using the same device.
I built the latest source locally on the Mac to try and step through it, but didn't get very far. The call:
d._serialNumber = NativeMethods.IORegistryEntryGetCFProperty_String(service, NativeMethods.kIOHIDSerialNumberKey)
returns NULL.
Is this a known issue? Are there any suggested work arounds?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi all - Reported this on the James' support forum few years back but never got any resolution, so I thought I'd try again here as well.
The following code hitting a specific vendor's UPS devices:
var devices = DeviceList.Local.GetHidDevices(4271).ToList();
var serialNumber = devices[0].GetSerialNumber();
Throws a DeviceIoException ("Serial Number Not Found") on MacOS, but works fine on Windows and Linux using the same device.
I built the latest source locally on the Mac to try and step through it, but didn't get very far. The call:
d._serialNumber = NativeMethods.IORegistryEntryGetCFProperty_String(service, NativeMethods.kIOHIDSerialNumberKey)
returns NULL.
Is this a known issue? Are there any suggested work arounds?
Thanks in advance!
The text was updated successfully, but these errors were encountered: