Jon00 Homeseer Log Monitor for Homeseer 3 and Homeseer 4

[jon00]

There is not, however in your case why not just create a virtual device with on/off buttons (default) and add the following to the very top of your script:

If hs.devicevalueEx(xxxx) = 100 then exit sub

When the new device is 'on', the script is disabled.

[prsmith777]

There is not, however in your case why not just create a virtual device with on/off buttons (default) and add the following to the very top of your script:

If hs.devicevalueEx(xxxx) = 100 then exit sub

When the new device is 'on', the script is disabled.

Very good. I will indeed do this. Thanks

[Pocster]

Hi

Would this log plugin allow me to keep track of which touch clients are available?
So at any point in a script I could effectively ask for example if iPad:iPad available then ...

Thanks in advance

[jon00]

Yes, you can use it for this. In its simplest form you can trigger events on connect/disconnect and set a virtual device to on or off.

An example of the triggers can be seen here:

https://forums.homeseer.com/forum/le...45#post1392545

If you are proficient at scripting, you can trigger on HSTouch log entries (which contain connect/disconnect) and that log line is passed to a defined script parameter. You can then act on the contents of the log line in your script to do what you wish.

Finally, the latest version supports sending JSON commands on a trigger, so you can update your devices directly i.e.

JSON=/JSON?request=controldevicebyvalue&ref=1234&value=100

[Pocster]

Yes, you can use it for this. In its simplest form you can trigger events on connect/disconnect and set a virtual device to on or off.

An example of the triggers can be seen here:

https://forums.homeseer.com/forum/le...45#post1392545

If you are proficient at scripting, you can trigger on HSTouch log entries (which contain connect/disconnect) and that log line is passed to a defined script parameter. You can then act on the contents of the log line in your script to do what you wish.

Finally, the latest version supports sending JSON commands on a trigger, so you can update your devices directly i.e.

JSON=/JSON?request=controldevicebyvalue&ref=1234&value=100

Hi,

All sounds good. Though my skills may need improving!
Much appreciated!

[jon00]

If you get stuck, give me a shout.

[Pocster]

If you get stuck, give me a shout.

Thats incredibly kind! I'm learning as fast as I can and have already in a short time achieved more than the previous HA was doing. Must admit I do find HS a bit of a double edged sword. Some things so easy - other things a bit of a workout 😀

[Spudjr]

Jon - on your webpage is says "Jon00 Homeseer Log Monitor for Homeseer 3 - THIS DOES NOT WORK UNDER HS3. PLEASE DOWNLOAD THE HS4 VERSION HERE" Is that a typo, does the HS3 version still work under HS3. Thanks

[jon00]

Thanks, yes a typo. Should read HS4. Now fixed!

[Spudjr]

Quick question, using log monitor to send alert on error when message contains "failed to send zwave command:" Is there a way to also have appended the rest of the message that appears in the homeseer log. Sometimes the failed sending is to device1 or device 3 etc. Dont want to make a trigger for each device.

Thanks

[jon00]

Yes, you use its global variables to insert into emails, pushover etc. For example you would use $$GLOBALVAR:jon00logmessage: which contains the log message which caused the trigger.

[jon00]

Version 1.0.7 (HS3), Version 1.0.4 (HS4) has been released

Added Linux Support (Mono 6+) – Only tested on Ubuntu.
Added Message Balloon feature to display all HS Log entries on Windows tray.

[martinisoft]

Jon, at first I want to thank you for this and your many other plugins/scripts, great work!

I have a question about log monitor for HS3.
When applying the following config the Normal triggers are fired just fine, but the special triggers are not.
I would expect them to fire since (in this example) Trigger1 and Trigger2 are fired within the same second.
I already tried to replace "Timespan" with "TimePeriod" since the documentation is not consistant on this but no reveal.

[Trigger1]
HSLogging=1
SearchType=""
SearchMessage ="ApplicationCommandHandler from Network: CF340FE8 Node: 196 HANDLING: COMMAND_CLASS_SCENE_ACTIVATION Frame(7)=1"
UseRegex=0
WatchPeriod=0
TriggerCount=1
ReTriggerPeriod=1
EventTrigger=
ScriptTrigger=
HSLogTriggerText="Trigger1 fired"

[Trigger2]
HSLogging=1
SearchType=""
SearchMessage ="Received a Scene Activation for Scene ID 11"
UseRegex=0
WatchPeriod=0
TriggerCount=1
ReTriggerPeriod=1
EventTrigger=
ScriptTrigger=
HSLogTriggerText="Trigger2 fired"

[Trigger3]
HSLogging=1
SearchType=""
SearchMessage ="Received a Scene Activation for Scene ID 12"
UseRegex=0
WatchPeriod=0
TriggerCount=1
ReTriggerPeriod=1
EventTrigger=
ScriptTrigger=
HSLogTriggerText="Trigger3 fired"

[SpecialTrigger1]
Trigger=1,2
Timespan=8
ReTriggerPeriod=8
EventTrigger=Muziek Terras Aan
ScriptTrigger=
HSLogTriggerText="SpecialTrigger1 fired"


[SpecialTrigger2]
Trigger=1,3
Timespan=8
RetriggerPeriod=5
EventTrigger=Muziek Terras Uit
ScriptTrigger=
HSLogTriggerText="SpecialTrigger2 fired"



Within the HS log I can see that Trigger1 and Trigger2 are fired:

jan-03 11:32:44

Jon00_HSLogMon

Trigger2 fired

jan-03 11:32:44

Jon00_HSLogMon

[Trigger2] Successful trigger parameters

jan-03 11:32:44

Jon00_HSLogMon

Trigger1 fired

jan-03 11:32:44

Jon00_HSLogMon

[Trigger1] Successful trigger parameters

jan-03 11:32:44

Jon00_HSLogMon

[Trigger1] LogColor: #008000

Am I missing something obvious here?

thanks in advance,

Martijn.

[jon00]

Looks like poor documentation on my part

Rather than :

[SpecialTrigger1]
Trigger=1,2

It should be:

[SpecialTrigger1]
TriggerList=1,2

The default ini file supplied has the correct settings.

You should be using TimeSpan, not TimePeriod. I'll correct the docs shortly.

[martinisoft]

Looks like poor documentation on my part

Rather than :

[SpecialTrigger1]
Trigger=1,2

It should be:

[SpecialTrigger1]
TriggerList=1,2

The default ini file supplied has the correct settings.

You should be using TimeSpan, not TimePeriod. I'll correct the docs shortly.

Wow! that was quick and TriggerList indeed fixed it.

Thanks again!

Martijn.