Learn to create script:

[Dagfinn Andestad]

Where can I find the overview of the whole script language (.Txt file) to homesser?

I need to learn it.

What is the syntax to check whether the clock greater than 13?

[stipus]

You should not use the .txt file syntax anymore. You'd better use the new .vb file syntax.

For this new VB.NET syntax, there are many sites with tutorials.

Just google for VB.NET tutorial or VB.NET reference

[stipus]

If DateTime.Now.Hour > 13 Then ... End If

[EDIT] fixed a typo...

[Dagfinn Andestad]

I get the error on the dateTimeobject. Why?

Sub Main()
If DateTime.Now.Hours > 13 Then
hs.execx10 "Q1","off",0
end if
End Sub

[tenholde]

Originally Posted by Dagfinn Andestad

I get the error on the dateTimeobject. Why?

Sub Main()
If DateTime.Now.Hours > 13 Then
hs.execx10 "Q1","off",0
end if
End Sub

It should be DateTime.Now.Hour (singular)

If you were entering the statement in VS using tenScripting, intellisense should have made that obvious while you were entering the statement.

tenholde

[jon00]

You are mixing VBScript & VB.NET with the syntax used.

Sub Main(ByVal Parms As Object)
If DateTime.Now.Hour > 13 Then
hs.execx10 ("Q1","off",0)
end if
End Sub

This will run only when the script name has a .vb extension (not .txt)

If you want to do this in VBScript, it would become:

Sub Main()
If Hour(Time) > 13 Then
hs.execx10 "Q1","off",0
end if
End Sub

This would only run when the script name has a .txt extension

[Moskus]

Originally Posted by Dagfinn Andestad

Where can I find the overview of the whole script language (.Txt file) to homesser?

I need to learn it.

What is the syntax to check whether the clock greater than 13?

Se også her:
http://www.homeseer.com/support/home...2/homeseer.htm

Many years ago I read a "Teach yourself VB.net in 21 days" book. It was very good to explain the basics. The rest is just logic.

[Rupp]

I disagree with Stipus, the vb script syntax is much easier to learn for beginners and both still work just fine. The best way to learn is go to the script library and look at existing scripts. The HomeSeer help files also have many examples for each scripting command as well.

[stipus]

One day you'll learn how to spell my name

You might be right, however the old syntax is just a language from the past.

Learning VB.Net might be usefull for many other systems...

[Uncle Michael]

...the old syntax is just a language from the past.

I am torn by this statement. While true from the standpoint that it makes effective use of current OS capabilities, vb.net design is definitely not forward looking. As far as I can tell, it was munged together by a bunch of drunk C# programmers with no one having overall project design responsibility. Worse, they don't appear to have talked to one another, or at least couldn't decide on a common set of conventions for object class specifications. Worst, they turned the task of crafting error messages over to a robot with no prior experience!

From a usability and learning point of view, VBS is far superior. It is internally self consistent. It's documentation is comprehensive, and reasonably easy to understand. The language is inherently (by design!) quite forgiving, and when you make an error, it is usually helpful in identifying the problem and suggesting an appropriate solution.

If you plan to go anywhere with Visual Basic, you owe it to yourself to learn to use vb.net. If you are just starting out learning how to write a script. Your frustration level will be much lower if you begin with VBS.

[Moskus]

Originally Posted by Uncle Michael

Your frustration level will be much lower if you begin with VBS.

I disagree.

I started with VBA and VBS around the time when .NET Framework version 1.0 came along. I was thrilled with the switch to .NET. Finally some structure and logic!



But... we can't all like the same things. And thankfully we don't.

[Rupp]

Originally Posted by stipus

One day you'll learn how to spell my name

Learning VB.Net might be usefull for many other systems...

I fixed my misspelling

This is true but for the true beginner sometimes jumping into .net is a bit daunting and they give up. The beauty of vbs is the beginner doesn't have to worry about defining each variable type. This can be bad but when learning it make things a ton easier.

[Moskus]

Originally Posted by Rupp

The beauty of vbs is the beginner doesn't have to worry about defining each variable type.

And that is something that is wrong with VBS. The sooner people learn to declare their variables, the better. It just makes more readable code (especially when the code gets complicated, which probably is going to happen if you like HomeSeer ).


Developing .NET scripts with tenScripting is extremely easy!
Just download VB.NET Express and off you go!

[rmasonjr]

If I had to do it over again, I wish I had not gone VBS first. Coding in VB.NET is much easier with tenScripting. Enforcing variable type and definition is key for good programming practices.

Another reason is single vs multi-threading. When you have multiple scripts firing at the top of every hour, etc. you're better off having VB.NET scripts.

[Uncle Michael]

Originally Posted by Moskus

And that is something that is wrong with VBS. The sooner people learn to declare their variables, the better. It just makes more readable code (especially when the code gets complicated, which probably is going to happen if you like HomeSeer ).

Developing .NET scripts with tenScripting is extremely easy!
Just download VB.NET Express and off you go!

I mostly agree. But, although my earlier rant was deliberately exaggerated, I still think it is much easier to start with VBS for simple scripts. VBS was designed for casual programmers. Learning to use it is mostly a learn by example process. Because it is limited in scope, the pertinent examples are relatively easy to capture in a guide book of approachable size.

Vb.net is clearly much more structured and much more capable than VBS, and I've converted nearly all my VBS scripts to vb.net thanks in large part to tenScripting. (A godsend! Without it, I would still be at square -1. ) That said, I still find that opening a separate application to create a simple script is not that appealing, and I usually start by trying to adapt an existing script in Notepad when I need to create something new. I also find the class structure very confusing. I usually cannot predict which class contains which functionality, and have not found any guides that have been useful - except to ask on this board for help.

That is really my point. If you are dedicated to programming and study vb.net closely, I'm sure it becomes second nature. For those of us who come to HA from other fields, and who see scripting as a necessary evil to accomplish something we consider useful, it is not transparent at all. We still need concrete examples to get started. But, vb.net is so powerful and so comprehensive it is overwhelming for simple tasks. It feels like driving a tractor trailer to get to the corner store.

Once your script is working correctly, ONLY THEN do you export it into your HomeSeer Script directory for production use.

Unfortunately, either I don't fully understand how to use the tool or I'm really incompetent (or both ), but I find that my most annoying errors are those that involve interactions within the HS environment, and they only surface AFTER I've installed the script and run in for a few cycles - maybe over a few days or weeks - to discover the subtle bugs in my logic. Unfortunately, vb.net didn't change that.

[Moskus]

Originally Posted by Rupp

I disagree with Stupis, the vb script syntax is much easier to learn for beginners and both still work just fine.

The VB script syntax is outdated and should have been removed from HomeSeer a long time ago. In my opinion it's also harder to learn as it's not as logical as .NET is.

Go the .NET route, you won't regret it.