Script error writing to log:

[ewkearns]

I am running the following script and receiving this error:

HomeSeer Error 1 Running script ATMCDown_50.vb: Exception has been thrown by the target of an invocation.

Sub Main(ByVal Parm As String)
Dim NetworkFullPath As String = "C:\Program Files (x86)\HomeSeer HS3\Logs\Network Loss.log"
My.Computer.FileSystem.WriteAllText(NetworkFullPath, "Gateway Packet Loss above 49%: " & Now() & vbCrLf, True)
End Sub

The oddity is that it still works fine! Does anybody know what I'm doing wrong?

[SteveMSJ]

I am running the following script and receiving this error:

HomeSeer Error 1 Running script ATMCDown_50.vb: Exception has been thrown by the target of an invocation.

Sub Main(ByVal Parm As String)
Dim NetworkFullPath As String = "C:\Program Files (x86)\HomeSeer HS3\Logs\Network Loss.log"
My.Computer.FileSystem.WriteAllText(NetworkFullPath, "Gateway Packet Loss above 49%: " & Now() & vbCrLf, True)
End Sub

The oddity is that it still works fine! Does anybody know what I'm doing wrong?

Don't the parameters for Main in a HomSeer VB.Net script have to be an object, i.e. not a string? Certainly I always define them as an object which is normally passed an array of objects, or nothing.

Steve

[ewkearns]

Thanks, Steve! That was it! This was not an original composition and I may have screwed it up. I don't truly understand this "parameter" stuff, especially when I am not passing a parameter.

[Guest]

Script calls from an Homeseer event will pass a single string. Script calls from an HS Touch will pass an array of strings. Declaring the input parameters for one way will earn that error message if called from the other side. However, an Object can contain either a string or an array of strings, so declaring the parameter as an object will make it work without the parameter mismatch error when called from either side.

Programming can be needlessly complicated sometimes.

[SteveMSJ]

Thanks, Steve! That was it! This was not an original composition and I may have screwed it up. I don't truly understand this "parameter" stuff, especially when I am not passing a parameter.

Glad you are sorted😊

I haven't tested whether HS complains if you leave the parameter field blank, i.e. Main(). I always use Main(ByVal Parm as object) in HS scripts, whether I am passing any parameters or not. Strictly speaking you could use ByRef rather than ByVal because, for an object, a pointer is passed to the object so there is nothing to be gained using ByVal. However, the performance difference is probably insignificant.

Steve

[Guest]

I haven't tested whether HS complains if you leave the parameter field blank, i.e. Main().

Leaving the parameter field blank will just earn you another error. A parameter will always be passed by the system, even if that parameter is blank (or null in programming terms)

[SteveMSJ]

Leaving the parameter field blank will just earn you another error. A parameter will always be passed by the system, even if that parameter is blank (or null in programming terms)

Thanks for the confirmation.
That's probably why I always define a parameter even when I'm not using one. I probably ran into the issue many years ago, but my memory is not so good now🙁

Steve

[Guest]

I forgot to add that an empty string (actually a null string) is an even different type of variable from string or an array of strings, which fortunately can also be held in an Object. Therefore you cannot go wrong declaring it an object. The ByVal is not necessary here, as it is assumed.

[ewkearns]

I understand more about that now than from reading several books. Thanks, folks!