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.

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

Unknown device subtype string: TEMPerHumV1.1rHu #27

Open
Catscrash opened this issue Mar 22, 2014 · 3 comments
Open

Unknown device subtype string: TEMPerHumV1.1rHu #27

Catscrash opened this issue Mar 22, 2014 · 3 comments

Comments

@Catscrash
Copy link

Hi,

it seems I had the bad luck to get a device which is not part of your program yet

Mar 22 14:25:33 catscrash-desktop kernel: [10862.424198] usb 1-2.1: new low-speed USB device number 10 using ehci_hcd
Mar 22 14:25:33 catscrash-desktop kernel: [10862.521943] usb 1-2.1: New USB device found, idVendor=0c45, idProduct=7402
Mar 22 14:25:33 catscrash-desktop kernel: [10862.521948] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 22 14:25:33 catscrash-desktop kernel: [10862.521951] usb 1-2.1: Product: TEMPerHumiV1.1
Mar 22 14:25:33 catscrash-desktop kernel: [10862.521954] usb 1-2.1: Manufacturer: RDing
Mar 22 14:25:33 catscrash-desktop kernel: [10862.525256] input: RDing TEMPerHumiV1.1 as /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2.1/1-2.1:1.0/input/input24
Mar 22 14:25:33 catscrash-desktop kernel: [10862.525380] hid-generic 0003:0C45:7402.0008: input,hidraw7: USB HID v1.10 Keyboard [RDing TEMPerHumiV1.1] on usb-0000:00:1a.7-2.1/input0
Mar 22 14:25:33 catscrash-desktop kernel: [10862.527709] hid-generic 0003:0C45:7402.0009: hiddev0,hidraw8: USB HID v1.10 Device [RDing TEMPerHumiV1.1] on usb-0000:00:1a.7-2.1/input1

when running tempered it says:

Unknown device subtype string: TEMPerHumV1.1rHu

querying it with hid-query results in:

sudo ./hid-query /dev/hidraw8 1 0x80 0x33 1
Device /dev/hidraw8 : 0c45:7402 interface 1 : RDing TEMPerHumiV1.1

Writing data (9 bytes):
00 01 80 33 01 00 00 00 00

Response from device (8 bytes):
80 04 1a e0 04 7f 44 55

@exuvo
Copy link

exuvo commented Mar 24, 2014

I encountered the same problem and I seem to have fixed it in my fork exuvo@09f0a62.

@mmalmeida
Copy link

Nice one. Don't you want to make it configurable and add a pull request @exuvo ?

@exuvo
Copy link

exuvo commented Oct 19, 2014

I really don't have the time for it. I've got more important things to code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants