Humidity sensor issue

[alphatech]

I added a Midon Temp/Humidity sensor to Temp05. MCS temperature can read the humidity sensor via the debug but it would not update the database or the device. It seems that new Humidity sensors get automatically created in the Device list. I also get these errors in the log.
(1)Device Temperature Humidity 0000000000000126H has properties different from its current device type of virtual - device type has been changed to virtual.1
This is from the log.
1/26/2010 7:52:55 AM mcsTemperature Temp05/08 Data: Humidity #01=45%=====140
1/26/2010 7:52:56 AM mcsTemperature Temp05/08 Data: Sensor #01[BF000800472F6010]=53.15F

Thanks

[Michael McSharry]

This does not seem like a good humidity reading without the line termination after the %. Is this format consistently provided? Is the Temp08 configured in a debug mode?

Humidity #01=45%=====140

[alphatech]

Hi Michael,
Thank you for your fast reply. These are the two readings from the log. By the way, I have Temp05 V4.
For some reasons, it creates other Humidity sensors in the "device" screen. The last one in the group seems to be the good one.

0 Temperature Humidity 0000000000000126H \42 virtual Never Set
0 Temperature Humidity 0000000000000126H \43 virtual Never Set
0 Temperature Humidity 0000000000000126H \44 virtual Never Set
0 Temperature Humidity 0000000000000126H \45 virtual Never Set
0 Temperature Humidity 0000000000000126H \46 virtual Never Set
0 Temperature Humidity 0000000000000126H \47 virtual Never Set
0 Temperature Humidity 0000000000000126H \48 virtual Never Set
0 Temperature Humidity 0000000000000126H \49 virtual Never Set
0 Temperature Humidity 0000000000000126H \65 virtual Never Set
0 Temperature Humidity 0000000000000126H \66 virtual Never Set
0 Temperature Humidity 0000000000000126H \67 virtual Never Set
0 Temperature Humidity 0000000000000126H \68 virtual Never Set
45 %Temperature Humidity 0000000000000126H \69 Humidity Today 5:39:53 PM

1/26/2010 5:32:53 PM mcsTemperature Temp05/08 Data: Humidity #01=45%=====209
1/26/2010 5:32:54 PM mcsTemperature Temp05/08 Data: Sensor #01[BF000800472F6010]=53.36F
1/26/2010 5:33:00 PM mcsTemperature Temp05/08 Data: Sensor #04[0F00080045F83910]=74.51F
1/26/2010 5:33:04 PM mcsTemperature Temp05/08 Data: Sensor #06[C4000800474F4410]=53.25F
1/26/2010 5:33:06 PM mcsTemperature Temp05/08 Data: Sensor #08[6C000800E9827510]=54.95F
1/26/2010 5:33:53 PM mcsTemperature Temp05/08 Data: Humidity #01=45%=====210
1/26/2010 5:33:54 PM mcsTemperature Temp05/08 Data: Sensor #01[BF000800472F6010]=53.36F
1/26/2010 5:34:00 PM mcsTemperature Temp05/08 Data: Sensor #04[0F00080045F83910]=74.51F
1/26/2010 5:34:04 PM mcsTemperature Temp05/08 Data: Sensor #06[C4000800474F4410]=53.25F
1/26/2010 5:34:06 PM mcsTemperature Temp05/08 Data: Sensor #08[6C000800E9827510]=54.95F

Thanks,
Aldo

[Midon]

This is from the log.
1/26/2010 7:52:55 AM mcsTemperature Temp05/08 Data: Humidity #01=45%=====140

Aldo/Michael,

This is a normal reading from TEMP05 (NOT TEMP08) older versions. Humidity sensor values in those versions of software did not include the sensor ID. Also, the "=====" reading following "%" can be ignored. It is a carry over from some (very) old debug software.

Mitch

[Michael McSharry]

It looks as if the V4 firmware puts Humidity, Wind and Rain on the same line. I'm not certain what the last number on that line (148, 209, 210) is representing. You indicated that device \69 does correctly show the humidity reading. Was \69 selected on the Sensor page for recording to the database?

You have an issue of multiple Humidity devices being created. I see in the source where there was some debug code added where the output went to the file mcsTemperatureHumidityDebug.txt in the Homeseer folder. This seems to indicate that someone had an issue in the past but the investigation was never completed. I dont remember what ist was about, but let us start by seeing what is in that file on your computer.

[Midon]

Good catch, Michael. The rain gauge is being reported on since jumper H2 is not equipped on his unit. However, since Aldo has no rain gauge connected, random outputs are being presented. That was a fault in v4.25 and lower of TEMP05.

Wind Speed/direction are presented on a seperate line.

Mitch

[alphatech]

Out of town

Sorry about the delay in responding, I was out of town and I came back few days ago. I attached the file you requested. Michael, Mitch is correct, the Humidity sensor is working properly. It shows the proper Humidity values. Yesterday I restored from the an old backup, it seems to be working ok, then I applied the Microsoft patches rebooted, I lost the humidity sensor again. I currently have a bare bone Homeseer only with your Temp. application, Insteon switches and the Mildon Interface. I moved the Humidity device on local power as Mitch suggested but this did not help either. I'm attaching the INI files maybe something wrong in the setup.
Thanks for your help. <TABLE border=0 cellSpacing=1 cellPadding=0 width="100%"><TBODY><TR><TD id=dv7018 class=tablecellon></TD><TD class=tableroweven></TD><TD class=tableroweven>Temperature</TD><TD class=tableroweven>Humidity7 </TD><TD class=tableroweven>\44</TD><TD class=tableroweven noWrap>Humidity</TD><TD class=tableroweven noWrap>Never Set </TD><FORM method=post name=ctrlform action=/stif target=deviceframe><TD id=dx7018 class=tableroweven noWrap><INPUT value=7018 type=hidden name=bookmark> <INPUT value=7018 type=hidden name=IFrameRef><INPUT value=stif type=hidden name=ref_page> </TD></FORM></TR><TR><FORM method=post name=chkOPForm5272><TD class=tablerowodd noWrap align=middle><INPUT class=formcheckbox onchange=buildList(this); value=5272 type=checkbox name=chkOP5272> </TD></FORM><TD id=dv5272 class=tablecellon>0 </TD><TD class=tablerowodd></TD><TD class=tablerowodd>Temperature</TD><TD class=tablerowodd>Humidity 0000000000000126H </TD><TD class=tablerowodd>\41</TD><TD class=tablerowodd noWrap>virtual</TD><TD class=tablerowodd noWrap>Never Set </TD><FORM method=post name=ctrlform action=/stif target=deviceframe><TD id=dx5272 class=tablerowodd noWrap><INPUT value=5272 type=hidden name=bookmark> <INPUT value=5272 type=hidden name=IFrameRef><INPUT value=stif type=hidden name=ref_page> </TD></FORM></TR><TR><FORM method=post name=chkOPForm7614><TD class=tableroweven noWrap align=middle><INPUT class=formcheckbox onchange=buildList(this); value=7614 type=checkbox name=chkOP7614> </TD></FORM><TD id=dv7614 class=tablecellon>0 </TD><TD class=tableroweven></TD><TD class=tableroweven>Temperature</TD><TD class=tableroweven>Humidity 0000000000000126H </TD><TD class=tableroweven>\42</TD><TD class=tableroweven noWrap>virtual</TD><TD class=tableroweven noWrap>Never Set </TD><FORM method=post name=ctrlform action=/stif target=deviceframe><TD id=dx7614 class=tableroweven noWrap><INPUT value=7614 type=hidden name=bookmark> <INPUT value=7614 type=hidden name=IFrameRef><INPUT value=stif type=hidden name=ref_page> </TD></FORM></TR><TR><FORM method=post name=chkOPForm8630><TD class=tablerowodd noWrap align=middle><INPUT class=formcheckbox onchange=buildList(this); value=8630 type=checkbox name=chkOP8630> </TD></FORM><TD id=dv8630 class=tablecellon>0 </TD><TD class=tablerowodd></TD><TD class=tablerowodd>Temperature</TD><TD class=tablerowodd>Humidity 0000000000000126H </TD><TD class=tablerowodd>\43</TD><TD class=tablerowodd noWrap>virtual</TD><TD class=tablerowodd noWrap>Never Set </TD></TR></TBODY></TABLE>

[Michael McSharry]

Best guess right now is that there is a non-printable character on the humidity line. I added a debug to display the data in hex to see what is being transmitted. It will be in the debug log and the period of interest is the first few minutes after HS startup.

[alphatech]

Thanks Michael, I'm at lost without your guys help. I will run it tonight and send the debugging info ASAP.
In the mean time not sure if this is a question for you or for Mitch, how do I delete old sensors not longer working from the Temp05.

Thanks,
Aldo

[alphatech]

Hi Michael,
This is the log been generated from your application. I appreciated your continued support in this matter.

Thanks,
Aldo

[Michael McSharry]

I must have done something wrong last night and I did not save what I did. Let's try again with the attached. All that is of interest is the HS log for a few minutes after a restart.

The user manual that Mitch wrote describes how to manage the sensors. I dont recall the exact process.

[alphatech]

Homeseer log Files attached

Hi Michael, please see attached files as you requested.
Thank you,
Aldo

[Michael McSharry]

There is a CR and LF after the % sign in the humidity line. While I did not ask for it, the real file that is needed is the GeneralDebug .txt file as only part of the info goes to the HS Log.

[alphatech]

Hi Michael,
I hope this is the file that you were looking for. I found it in this directory. C:\Program Files\HomeSeer HS2\Data\mcsTemperature
Thanks,
Aldo

[Michael McSharry]

The problem has to do with the index for the humidity sensor. It has been too long since I worked with the Temp05 code so I'm guessing a little with this one. The DIS command is where mcsTemperature asks the Temp05 for its list of sensors and corresponding indexes. It shows the Humidity at #07, but when it delivers data it declares is at #01. There is just tool much logic in the software that tries to accomodate all the different firmware versions of the Temp05/08 to understand what really needs to be done. I made a guess with the attached. I think the mcsTemperature.ini file should also be edited to give it a good starting point. What I think belongs in there for the humidity sensor is the following. The you posted has the sensor at \44. Just replace the two lines in the .ini with these two.

[Database]
\41="sED0000004FFA3026H,6,1"
[Devices]
ED0000004FFA3026H="\41,00:00, 0,,0"

If you have success on startup, then shutdown Homeseer and try again with particular attention given to what is in the .ini in the area the edits were made. If the problem persists then post the new mcsTemperature.ini and the general debug log.