Support for product ID 413d:2107

[kenkma]

Most recent sensors seems to have a new ID, 413d:2107.

Has anyone successfully hacked the code to work with it?

this C hack seems to work.

edorfaus/TEMPered#51

Thank you.

[Estebastien]

Yes same need. I have a TEMPerX232 (thermo-hygrometer) with that ID and I can't make it work as my others Temper1F.
I have no clue. I don't really now what magic is going on in these hacks. I added the new ID to the VIPDS list, and of course I get an error ("Entity not found").
Thank you

[mreymann]

Hi I use temper-python with my Microdia TEMPer Temperature Sensor (0c45:7401) and it works like a charm. I, as well, was too adventurous when buying an obscure "TEMPerHUM" (413d:2107). It would be great to have support for this device in temper-python!

Thanks for your work!

[mreymann]

I've created a working Munin plugin for our device using hid-query: https://github.com/mreymann/temperx
Support should be fairly easy to implement in temper-python. USB commands seem to be very similar. I have a PCAP file here if anybody needs it.

[ndemou]

Hoping that this comment will help temper-python to support devices with id 413d:2107 I should note that running this hid-query gives you the temperature (hid-query is part of https://github.com/edorfaus/TEMPered more info bellow):

./hid-query /dev/hidraw1 0x01 0x80 0x33 0x01 0x00 0x00 0x00 0x00
...
Response from device (8 bytes):
         80 80 09 0e   4e 20 00 00     <--- temperature is 0x090e/100

---

P.S. Until temper-python supports them here's a complete set of commands to print the temperature:

DEVID=/dev/hidraw1 # use `hid-query --enum` to find the right DEVID
OUTLINE=`./hid-query $DEVID 0x01 0x80 0x33 0x01 0x00 0x00 0x00 0x00|grep -A1 ^Response|tail -1`
OUTNUM=`echo $OUTLINE|sed -e 's/^[^0-9a-f]*[0-9a-f][0-9a-f] [0-9a-f][0-9a-f] \([0-9a-f][0-9a-f]\) \([0-9a-f][0-9a-f]\) .*$/0x\1\2/'`
echo $(( 16#$OUTNUM ))|awk '{printf("%4.1f\n",$0/100)}'
23.1°C

The above are 99% based on TEMPered#51 "hack" from digiboule mentioned above.

To install TEMPered (that contains the hid-query utility) download it and see this post edorfaus/TEMPered#35 (comment)

P.S.3: I must admit that I'm really confused by who forked what version of TEMPered to support which device type.

P.S.4: Here's a copy of my bash session that ended up on the above commands:

root@lion:~/manual-install/TEMPered-master/utils#  lsusb
...
Bus 004 Device 002: ID 413d:2107  
...
root@lion:~/manual-install/TEMPered-master/utils# ./hid-query --enum
/dev/hidraw0 : 413d:2107 interface 0 : (null) (null)  #<---note the device ids (/dev/hidrawX)
/dev/hidraw1 : 413d:2107 interface 1 : (null) (null)

# I will try to read from the first device id
root@lion:~/manual-install/TEMPered-master.TafThorne/build/utils# ./hid-query /dev/hidraw0 0x01 0x80 0x33 0x01 0x00 0x00 0x00 0x00
Device /dev/hidraw0 : 413d:2107 interface 0 : (null) (null)

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

No data was read from the device (timeout).

# Well this device id didn't work, let's try the other one:
root@lion:~/manual-install/TEMPered-master/utils# ./hid-query /dev/hidraw1 0x01 0x80 0x33 0x01 0x00 0x00 0x00 0x00
Device /dev/hidraw1 : 413d:2107 interface 1 : (null) (null)

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

Response from device (8 bytes):
         80 80 09 0e   4e 20 00 00

# perfect so /dev/hidraw1 is the device id that does work!

[jbeale1]

As I mentioned at edorfaus/TEMPered#35 (comment) I have one of these new 413d:2107 devices which the Windows "TEMPer V26.1" software calls "Firmware: TEMPerGold_V3.1" and mine is I think temperature only, although the hidapi testgui app shows two devices with that VID:PID. The eight-byte hex string posted by ndemou above, does work when manually entered from the hidapi testgui. However the TEMPered project "hid-query" tool does not see the device at all (only sees my keyboard and mouse) so I don't know how to script this.

[ndemou]

@jbeale1: mine is also temperature only and if you notice in the transcript above I also see two devices and one of them doesn't respond.

[jbeale1]

It does work! After keyboard and mouse, it's hidraw3 on my system. Also needs 'sudo'

 sudo ./hid-query /dev/hidraw3 0x01 0x80 0x33 0x01 0x00 0x00 0x00 0x00
Device /dev/hidraw3 : 413d:2107 interface 1 : (null) (null)
Writing data (9 bytes):  00 01 80 33   01 00 00 00   00
Response from device (8 bytes):  80 80 08 4d   4e 20 00 00

[jbeale1]

Edit: awk works for float division, or after doing "sudo apt-get install bc"

#!/bin/bash
OUTLINE=`sudo ./hid-query /dev/hidraw3 0x01 0x80 0x33 0x01 0x00 0x00 0x00 0x00|grep -A1 ^Response|tail -1`
OUTNUM=`echo $OUTLINE|sed -e 's/^[^0-9a-f]*[0-9a-f][0-9a-f] [0-9a-f][0-9a-f] \([0-9a-f][0-9a-f]\) \([0-9a-f][0-9a-f]\) .*$/0x\1\2/'`
HEX4=${OUTNUM:2:4}
DVAL=$(( 16#$HEX4 ))
bc <<< "scale=2; $DVAL/100"

[jbeale1]

Bash script to print time & temp every ~15 sec, with readTEMPer.sh being my script in above comment:

while [ true ]; do
  temp=`/usr/local/bin/readTEMPer.sh`
  echo $(date +"%F %T") " , " $temp
  sleep 14
done

example output:

2018-06-17 11:45:23  ,  24.50
2018-06-17 11:45:38  ,  24.43
2018-06-17 11:45:52  ,  24.25
2018-06-17 11:46:07  ,  24.12
2018-06-17 11:46:21  ,  23.93

[ndemou]

Thanks @jbeale1 for noticing the bug with integer arithmetic. I fixed my script (just used awk instead of bc because it works perfectly for such low precision calculations and is pre-installed almost everywhere)

[jbeale1]

On my raspberry pi, 'awk' is apparently mawk 1.3.3 and it always gives me 0.0 for example:

awk "BEGIN {printf(\"%4.1f\n\",0x0891/100)}"
 0.0

awk -W version
mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan

Edit: after 'sudo apt-get install gawk' then it all works as intended.

[ndemou]

Right again. A cross platform way seems to be

echo $(( 16#891 ))|awk '{printf("%4.1f\n",$0/100)}'

(I've updated my script)

[schniepp]

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. 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?

I should add that my device is called "TemperX232". I know that some other devices also use the same 413d:2107 USB identifier (for instance the newer "TemperHum" devices).