Shared publicly  - 
Just in case anyone buys a new TEMPer usb thermometer, the latest models seem to be completely different (they show up as idVendor 0C45 and idProduct 7401 and dmesg lists them as RDing TEMPerV1.2). I had to use a new program from instead of the perl module I used before.
Cícero Silva's profile photoPhilipp Adelt's profile photoThomas Thorne's profile photoThomas Bludau's profile photo
Philipp: You won't believe what good timing you have! I'm about to write a new column about using the new TEMPer device so this update is very welcome.
Great, hope it helps someone. Let me know when you publish that please. Today another TEMPer1 arrived, I hope to integrate that as well. Maybe it works OOTB, but I doubt it.
If you need inspiration (and given your publication list I doubt that): Raspian (the Raspberry Pi's Debian-based hardfloat-distribution) could use a package like temper-snmp. Until now I never made a debian package myself so I just hope for someone to pick that up. ;-)
Expect something more about this class of TEMPer device in the March 2013 Linux Journal :)
Kyle, you don't know how great YOUR timing is!  I'm banging my head on the wall, trying to get this to work.  Now I can just wait for the LJ article!   ;)
Just as an update, the March 2013 Linux Journal is now out and contains my new column about using a TEMPer USB thermometer with a Raspberry Pi to control my beer fridge.
Thanks for the link to that tarball, worked perfectly for me. 
Hi, i have TEMPerHUM 0c45:7402. how can i get moisture.
My plan is to start a monitoring over nagios with the temper Devices (~20) for some home activities under raspberry pi :-) At the moment i've a problem under Ubuntu to identify the different multiple usb devices, because there is no serial number. 

After the extension from Philipp i think the only way is to write a script, which is checking the order you add on a Temper device to the usb port. Like: plug in usb device with a handwritten one on it ... wait ok, system device number one. plugin the handwritten number two, wait ... system device number two. 
(in short technical language, remember the usb-bus and device id and create a list where all defined tempers are plugged in, then start phillips new pcsensor in the right order)

This is a very strong temporary solution, because you have to plug in every temper device after a reboot again. Have you some better solutions/ideas for my problem? 
+Thomas Bludau I have experimented a lot with two and three TEMPer devices attached to the Raspi. At the end of the day: It is not possible to distinguish the sensors. Your idea to hand-identify the sensors is great - until reality strikes: Sometimes the devices "disappear" for a second and are reenumerated. Et voilà - you have no idea what USB device is what sensor. I have not had more than 1 or 2 days of a "stable" USB bus situation without reenumerations.
The real solution here would be to have such a cheap sensor that carries a unique value in the serial number field. But the devices we are talking about don't have any. Sorry...
+Kyle Rankin +Philipp Adelt perhaps i've found a way to identify the temper device much more better. 

i saw that the command "lsusb -t" shows all ports where the devices are activated. man-entry: "Tells lsusb to dump the physical USB device hierarchy as a tree. This overrides the v option" 

in this way i can see the the actually usb device number. with a self-wrote script i can now identify which Temper has which pcsenser device number for -n. 

is it right Philipp, that the actually pcsenser script with the -n parameter is using a sorted list of the usb device number of the bus and get the highest number for -n 0, the number after the highest number as 1 and so on?

if my assumption is correct, then the only weak point is to identify how secure the information for the physical usb device is.

i've tested it some times (but not enough to say its right). and evan after a reboot everything was so i've expected.

what are your saying to this solution?
I recently got a couple of PCsensor devices up and running on Ubuntu using the code from 

All three of the ones I purchased recently came up as:
$ lsusb 
Bus XXX Device XXX: ID 0c45:7401 Microdi
So it looks like the same kit is still going strong on eBay and Amazon.  I am quite pleased as it has meant that I could get a little Munin graph of temperature readings going with a bit of bash script.  
Add a comment...