Write to Log File

[mmnissan]

I am running HS4 in case this makes a difference. I want to write to the log file. So I started out simple, hs.writelog ("temp= "). I does not work. My goal is to print out the actual device temp as well. Any suggestions?

[Uncle Michael]

The WriteLog function requires two string parameters:

[donstephens]

You might run into problems if you follow the example if using vb scripts. You will fare better with

hs.WriteLog("Error","An error has occurred in my script!")

[Otto-mation]

You might run into problems if you follow the example if using vb scripts. You will fare better with

hs.WriteLog("Error","An error has occurred in my script!")

I am using a Hometroller Zee S2 and just tried your example verbatim but it doesn't appear in my HS log window.
Any suggestions? It would be a highly useful feature for my needs.
-steve

[donstephens]

No error message? Sorry, but I'm out of suggestions.

[Guest]

I am using a Hometroller Zee S2 and just tried your example verbatim but it doesn't appear in my HS log window.
Any suggestions? It would be a highly useful feature for my needs.
-steve

How are you specifying your WriteLog? Part of a script file? If so, can you show us the complete script?

If the script is an immediate script, then you would want to precede the hs.Writelog with a "&n". Example:

&nhs.WriteLog("Error", "Error message goes here")

[Otto-mation]

How are you specifying your WriteLog? Part of a script file? If so, can you show us the complete script?

If the script is an immediate script, then you would want to precede the hs.Writelog with a "&n". Example:

&nhs.WriteLog("Error", "Error message goes here")

Thanks for the example - I did exactly that in the immediate script - as per the screen grab below - I use test events for small pieces before using them in anything bigger.

[Uncle Michael]

Does the event itself show in the log?
If there are no error messages, I wonder if there is a filter being applied to your log. (Try resetting the log to be sure no filters are active.)

This is what I see in the log when I try a test event to write to the log (last entry is at the top):

Aug-19 8:55:22 AM Test vbs test
Aug-19 8:55:22 AM Event Running script statement immediately: &hs.WriteLog "Test", "vbs test"
Aug-19 8:55:22 AM Event Event Trigger "Test Immediate script"
Aug-19 8:55:22 AM Event Event Test Immediate script triggered by the event page 'Run' button.

[Otto-mation]

Thanks for the suggestion - I reset the log filter but doesn't appear to have made a difference.
Here's the latest log clip and the event itself follows.....

[Guest]

Interesting. Just for giggles, try temporarily removing the Speak command and then re-run the event. Maybe the Speak is causing some sort of problem?

[Otto-mation]

WOW!!! You score!!!
I removed the speak command
SOLVED!
I'm ecstatic and grateful for your suggestion and help!
WOOHOOOO!!!

[wpiman]

WOW!!! You score!!!
I removed the speak command
SOLVED!
I'm ecstatic and grateful for your suggestion and help!
WOOHOOOO!!!

I know this is an old thread, but were you able to write to the log file as such and not have the "event writing to the log file" in the log file? It sort of is redundant.

[joegr]

I know this is an old thread, but were you able to write to the log file as such and not have the "event writing to the log file" in the log file? It sort of is redundant.

Click on "do not log this event" on the event options.