Problem with LogMonitor Trigger Threshold

[pdishere]

Hi Jon,
I thought I would give your Log Monitor Utility a try and I've run into a problem I'm hoping you can help with. It appears with using a TriggerThreshold="5" for example, that the Event,Script and HSLog are firing as many times as the string is found up to 5 instead of only once since the last time the JON00HSLogMonitor script is run which I have set to execute every minute. I'm currently running 2.5.0.52 version of Homeseer and also have copied/pasted my ini file and log entries below..Any help is appreciated! Thanks, Pete

INI
[Settings]
HSLogging=1
[Trigger1]
xString1="X10 Received"
String1Parm="1"
TriggerThreshold="5"
Logging="1"
EventTrigger="Disable Plugin"
ScriptTrigger="Homeseer Problem Test.vb"
HSLogTriggerText="Problem2"

LOG
5/11/2012 8:27:17 PM ~!~Event~!~Running script and waiting: Jon00HSLogMonitor.vben
5/11/2012 8:27:17 PM ~!~Problem~!~
5/11/2012 8:27:17 PM ~!~Jon00_HSLogMon~!~Problem2
5/11/2012 8:27:17 PM ~!~Problem~!~
5/11/2012 8:27:17 PM ~!~Jon00_HSLogMon~!~Problem2
5/11/2012 8:27:17 PM ~!~Problem~!~
5/11/2012 8:27:17 PM ~!~Jon00_HSLogMon~!~Problem2
5/11/2012 8:27:17 PM ~!~Problem~!~
5/11/2012 8:27:17 PM ~!~Jon00_HSLogMon~!~Problem2
5/11/2012 8:27:17 PM ~!~Problem~!~
5/11/2012 8:27:17 PM ~!~Jon00_HSLogMon~!~Problem2



[Version]
Version=1.0.0

[jon00]

I don't believe you have a string defined yet:

The line in the ini file:

xString1="X10 Received"

should be:

String1="X10 Received"

[pdishere]

Sorry Jon for the confusion, I had commented that out as a quick way to disable...For example, I just uncommented that entry in INI and I see the following in the log. The "Script Called" is my script putting an entry in the log when its called for debug purposes.
5/12/2012 11:20:17 AM ~!~Event~!~Event Trigger "Problem Detection"
5/12/2012 11:20:17 AM ~!~Event~!~Running script in background: Jon00HSLogMonitor.vben
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Trigger1 detected (No1)
5/12/2012 11:20:17 AM ~!~Problem~!~Script called
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Problem2
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Trigger1 detected (No2)
5/12/2012 11:20:17 AM ~!~Problem~!~Script called
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Problem2
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Trigger1 detected (No3)
5/12/2012 11:20:17 AM ~!~Problem~!~Script called
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Problem2
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Trigger1 detected (No4)
5/12/2012 11:20:17 AM ~!~Problem~!~Script called
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Problem2
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Trigger1 detected (No5)
5/12/2012 11:20:17 AM ~!~Problem~!~Script called
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Problem2
5/12/2012 11:20:17 AM ~!~Jon00_HSLogMon~!~Trigger1 string(s) were detected 5 time(s)

[jon00]

OK understand,

Apologies but I will not be able to look at this until tomorrow.

[pdishere]

No worries Jon..Thanks!

[jon00]

Try version 1.0.1 on my site.

[pdishere]

Thanks for the quick response Jon,it worked great! I'm using this in conjunction with your enable/disable utility as a temporary workaround for an occasional looping condition I'm having with a plugin...donation made...thanks again!

[jon00]

Thanks very much - silly error on my part!