McsTemperature Event Error

[chrisbor]

Hi,

I created an event to control my heating ,this is a homeseer event witch called "temperature Action " and I have this error in ""Event log" when it runs.

<TABLE cellSpacing=2 cellPadding=0 width="100%" border=0><TBODY><TR><TD class=LOGDateTime1 noWrap align=left>25/04/2008 10:18:16 </TD><TD class=LOGType1 align=left colSpan=3>Info </TD><TD class=LOGEntry1 align=left colSpan=8>Event Trigger "Test"</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>25/04/2008 10:18:16 </TD><TD class=LOGType0 align=left colSpan=3>mcsTemperature Debug </TD><TD class=LOGEntry0 align=left colSpan=8>Trigger Action </TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>25/04/2008 10:18:16 </TD><TD class=LOGType1 align=left colSpan=3>mcsTemperature </TD><TD class=LOGEntry1 align=left colSpan=8>TriggerAction on line 670 Subscript out of range


</TD></TR></TBODY></TABLE>
Have you a idea

Thank's a lot

[Michael McSharry]

No answer now, but I added some additional info in the error output in 5.13.7. mcsTemperature was recently updated in the HS2 updater and you should get it from there first before installing the V5.13.7 from the message board at the top of this forum.

[chrisbor]

Ok I try and I wish you informed

regards

[chrisbor]

Hello


I downloaded the version by homeseer updater and now I've this error

25/04/2008 23:53:47 - Error - Initializing script run: Fichier 'C:\Program Files\HomeSeer 2\scripts\mcsTemperatureActions.vb' introuvable. " not found " in english .


bye

[Michael McSharry]

Try reloading the from the updater. It looks as if the file was not uploaded so you did not receive any updates.

[chrisbor]

Hello

I've reloaded it and it's the same error and the same sequence only on the same DS18B20


Help my heating don't work correctly

Thank's






26/04/2008 10:28:50 - mcsTemperature - Trigger Action
26/04/2008 10:28:50 - mcsTemperature - TriggerAction MonitoredEventCount=101 101 on line 670 Subscript out of range
26/04/2008 10:28:51 - mcsTemperature - DS9x9x Port <COM2> Device = DS18B20 DD0000008937A028
26/04/2008 10:28:52 - mcsTemperature - DS18B20(1):
26/04/2008 10:28:52 - mcsTemperature - Calibrate 0 with bias 0
26/04/2008 10:28:53 - mcsTemperature - DS18B20(1):
26/04/2008 10:28:53 - mcsTemperature - Calibrate 0 with bias 0
26/04/2008 10:28:54 - mcsTemperature - DS9x9x Port <COM2> Device = DS18B20 DD0000008937A028
26/04/2008 10:28:55 - mcsTemperature - DS18B20(1):
26/04/2008 10:28:55 - mcsTemperature - Calibrate 0 with bias 0
26/04/2008 10:28:56 - mcsTemperature - DS18B20(1):
26/04/2008 10:28:56 - mcsTemperature - Calibrate 0 with bias 0
26/04/2008 10:28:57 - mcsTemperature - DS9x9x Port <COM2> Device = DS18B20 DD0000008937A028
26/04/2008 10:28:58 - mcsTemperature - DS18B20(1):
26/04/2008 10:28:58 - mcsTemperature - Calibrate 0 with bias 0
26/04/2008 10:28:59 - mcsTemperature - DS18B20(1):
26/04/2008 10:28:59 - mcsTemperature - Calibrate 0 with bias 0
26/04/2008 10:29:00 - mcsTemperature - DS9x9x Port <COM2> Device = DS18B20 DD0000008937A028
26/04/2008 10:29:00 - Info - Event Trigger "Test"
26/04/2008 10:29:00 - mcsTemperature - DS18B20(1):
26/04/2008 10:29:00 - mcsTemperature - Calibrate 0 with bias 0

[Michael McSharry]

Your output is showing that there are 101 "thermostats" being monitored. I suspect you intend to have only 1. A temperature Action is usually triggered only 1 time and it setup to persist forever. The event that contains the Temperature Action is almost always setup as a manual event and triggered only once. I'm guessing you have it setup to trigger based upon temperature limit so each time the limit is reached another "thermostat" is being placed into service. The plugin has a limit of 100 so when the 101th is triggered the subscript error is produced.

[chrisbor]

Thank's Michael for your explanations , but I' ve a question how stop the process .

I've stopped the device ON / OFF several times but the process still persist !

Bye

[Michael McSharry]

The TemperatureAction's persistance is based upon how you set it up. One option is to run untill manually turned on or off. This is what it looks as if you are trying to do. Another is to run forever which looks as if what you have setup. Change the TemperatureAction of the event and then restart HS and you should be able to control it as you desire.