VB.Net Immediate Script Generates Log Entry

[BobSpen]

I have recently discovered that using a VB.Net "immediate" script(&nhs.xxxxxx) in an Event that has been set to "Not Log" still generates a log entry when the script runs. A VB script(&hs.xxxx) does not.
Can others confirm this unusual behavior???

ExampleThe second entry is the result of the script(&nhs.WriteLog (xxx, xxx, xxx)

Jun-30 10:28:34 AM On-Off Delay OnDelay= 0 OffDelay= 0
Jun-30 10:28:34 AM Info Running immediate script: C:\HomeSeer HS3\Temp\K1.vb

[rmasonjr]

Yep - been that way for a LONG time.

[langenet]

So should we be using &hs or &nhs then?

Robert

[mrhappy]

So should we be using &hs or &nhs then?

Robert

nhs is executed as VB.net whereas hs is executed as VBScript, I don't think there is guidance over what should be used and both are I would imagine going to be in HS for some time so I would say you can carry on but if something does not work with hs then try nhs.

[jhearty]

I see this problem whether it is &hs. or &nhs. The log I see is:

Jul-05 5:14:14 PM Info Running immediate script: /tmp/K2.vb

The event is below. So is there a way to stop these logs? Any help is appreciated. Thanks.

John

Edit: FWIW, when I disable logging completely in Setup, it does not write the same logs when the event runs.

[srodgers]

Copy the contents of your /tmp/K2.vb and place this in a script file and then run the script as your Then action vice the immediate script. I needed up doing that because of countdown timers that started out as immediate scripts and clutter up the logs every second when running.