qctables shows that lately (not last week), A4 0.5m TRH was the highest RH.  Replaced SHT.  A10 0.5m TRH was the lowest RH.  Replaced SHT.

Also, Gordon noticed that A17 0.5mTRH was coming in as S/N87, with id=0x11.  This SHT was labeled 068!  Also, Gordon's serial number logbook entry shows a different S/N 2 weeks ago.  Using mote_dump, we don't see a 0x10 sensor, however statsproc has been creating NetCDF files with data for both 0.5m and 2m TRHs.  This is all very odd.  Replaced this SHT with 060 and data now coming in ok.

From the log output of mote_dump, here are the serial number messages from the TRH mote at 17 from Sep 20 through Oct 6:

2012 09 20 19:52:34.913, mote=17, sensorType=0x11 SN=43, typeName=TRH
2012 09 20 19:55:21.532, mote=17, sensorType=0x10 SN=68, typeName=TRH
2012 09 20 20:24:40.643, mote=17, sensorType=0x11 SN=87, typeName=TRH
2012 09 20 20:25:12.672, mote=17, sensorType=0x11 SN=43, typeName=TRH
2012 09 20 20:42:35.153, mote=17, sensorType=0x11 SN=87, typeName=TRH
2012 09 20 20:43:05.852, mote=17, sensorType=0x11 SN=43, typeName=TRH
2012 10 06 19:06:56.001, mote=17, sensorType=0x11 SN=87, typeName=TRH
2012 10 06 19:09:37.901, mote=17, sensorType=0x11 SN=43, typeName=TRH
2012 10 06 19:27:18.501, mote=17, sensorType=0x11 SN=87, typeName=TRH
2012 10 06 19:27:33.401, mote=17, sensorType=0x11 SN=43, typeName=TRH
2012 10 06 19:47:10.631, mote=17, sensorType=0x10 SN=60, typeName=TRH

My best guess is that the SN=87 records are somehow incorrect, in that there wasn't really an 87 at that location.

I also see the same issue at 19, where it is claiming that TRH 127 is present. In today's /var/log/isfs/isfs.log from statsproc, 17 and 19 are the only stations exhibiting this issue:

2012 10 06 17:13:53.194, mote=19, sensorType=0x10 SN=46, typeName=TRH 
2012 10 06 18:01:52.954, mote=19, sensorType=0x11 SN=65, typeName=TRH 
2012 10 06 20:49:41.294, mote=19, sensorType=0x10 SN=46, typeName=TRH 
2012 10 06 20:49:41.294, mote=19, sensorType=0x11 SN=65, typeName=TRH 
2012 10 07 02:31:43.613, mote=19, sensorType=0x10 SN=46, typeName=TRH 
2012 10 07 02:31:43.613, mote=19, sensorType=0x11 SN=65, typeName=TRH 
2012 10 07 09:17:06.213, mote=19, sensorType=0x11 SN=127, typeName=TRH
2012 10 07 09:32:27.243, mote=19, sensorType=0x11 SN=65, typeName=TRH 
2012 10 07 09:33:50.863, mote=19, sensorType=0x11 SN=127, typeName=TRH
2012 10 07 09:35:32.293, mote=19, sensorType=0x11 SN=65, typeName=TRH

NIDAS only logs the serial numbers in a run the first time they are encountered, and when they change.