You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I also have a 413d:2107 device. It is supposed to do both T and R.H.: vendor, Amazon. By pressing the button, I can get it to operate like a keyboard and just dump its output to /dev/stdin. So I know it works, and it puts out T and R.H. in a human readable way. But that's not really practical.
My biggest issue right now is that hid-query /dev/hidraw3 0x01 0x86 0xff 0x01 0x00 0x00 0x00 0x00 gives me this error: Write failed: (null). I am doing this as root, and hid-query detects it successfully (that's how I know that it is hidraw3). Is this perhaps a slightly different device? Does it need a different string sent? Or is something about permissions set up the wrong way, so that writing does not work?
The text was updated successfully, but these errors were encountered:
Unfortunately there are many different devices that use this vendor ID, but you can try this:
Please look at https://github.com/mreymann/temperx under "Prerequesites". Make sure the hidquery binary uses libusb not hidraw! /usr/local/bin/hid-query -e should then give you a USB path like this: 000x:000x:01.
Then use this path with hidquery. E. g.:
$ /usr/local/bin/hid-query 0005:0003:01 0x01 0x80 0x33 0x01 0x00 0x00 0x00 0x00
Device 0005:0003:01 : 0c45:7401 interface 1 : RDing TEMPerV1.4
I also have a 413d:2107 device. It is supposed to do both T and R.H.: vendor, Amazon. By pressing the button, I can get it to operate like a keyboard and just dump its output to
/dev/stdin
. So I know it works, and it puts out T and R.H. in a human readable way. But that's not really practical.My biggest issue right now is that
hid-query /dev/hidraw3 0x01 0x86 0xff 0x01 0x00 0x00 0x00 0x00
gives me this error:Write failed: (null)
. I am doing this as root, and hid-query detects it successfully (that's how I know that it is hidraw3). Is this perhaps a slightly different device? Does it need a different string sent? Or is something about permissions set up the wrong way, so that writing does not work?The text was updated successfully, but these errors were encountered: