tenWare Software

tenScripting Enhancements

Version 1.4.2

When you run a script from a HomeSeer Event without specifying the Method to run, HS defaults to a method name of Main.  If the method name specified in the script is main, the method will not be found and the Event execution will fail.  What is confusing is that tenScripting will allow you to define a method main and the select it and run it during testing.  When you export the script to HS with a method name of main you will have to explicitly specify a method name of main in the Event definition, or HS will look for a default name of Main.  A warning is now displayed by tenScripting if you attempt to run a method with a name of main.

Version 1.4.1

HomeSeer treats parameters passed to scripts very strangely.  Instead of letting you specify multiple parameters, separated by commas  --  HomeSeer passes a single String parameter that is truncated if it encounters a comma.  If you call a HomeSeer script from HsTouch, you can specify multiple parameters and they will be passed to the script in a more typical fashion  --  a single Object array is passed containing the parameters.  tenScripting can now be used to test scripts processing multiple parameters passed from HsTouch.  If you uncheck the Process as HS Parameters checkbox, then you can specify multiple parameters separated by commas and they will be passed to your script as an array of Objects.

tenScripting now detects if a new release has been installed, and copies the settings from the prior release.


Version 1.3.0

When tenScripting exports a script, it copies anything within the Class definition to the exported .vb file.  This created a problem if the script required one or more Imports statements, as they must appear outside of the class definition, and hence would not be included in the exported file.  Version 1.3.0 corrects this by copying any Imports statement to each script within the tenScripting .vb file.


Version 1.2.0

The distribution .ZIP file no longer includes the HomeSeer assemblies, and you must add references to the assemblies as part of the installation process.

Triggers have been added that allow you to specify scripts that should automatically be run in the development environment when a device's value or status changes.

The three log display (Events log, tenScripting log, and the HS log) entries now all contain a numerical sequence number so that you can better determine the sequence of activities.

 HS Debug Log handling has been rewritten to make it easier to turn HS Debug Logging on/off and to now easily display the log records.

The HS Connection dialog now allows for the entry of a TCP Port number.  This is to facilitate connecting to HS from outside the local network.

Minor bug fixes.


Version 1.1.0

Significant changes have been made to tenScripting in version 1.1.0.  The most significant changes were made to simplify managing a large number of scripts.  Instead of requiring all scripts to reside in a single file (Scripts.vb), you may now place your scripts in multiple *.vb files.  This allows your to categorize your scripts into related groups.

Another major change was made to allow testing of multiple entry points to a single script.  HomeSeer allows you to specify both the Script (name.vb) and the entry point (usually Main) when creating events that run scripts.  tenScripting now allows you to specify any entry point (Public Sub) to start debugging. There is an advantage to using multiple entry points within a single script instead of using multiple scripts in defining your HomeSeer Events.  You can include functions and subroutines once within the script and all entry points can use this single copy of these routines instead of including the same routines in each script.  This makes code maintenance much easier.

In addition, the following enhancements have been made:

The HomeSeer connection parameters (IP Address, Userid, Password) can now be easily changed from the GUI.

All HomeSeer Device status and value changes are displayed in real time.

The HomeSeer Log display is now dynamic -- it no longer must be updated manually.

The Help menu provides links to the HomeSeer Help file and the SDK

Additional sample scripts have been included.

Overall GUI improvements have been made.

Complete tenScripting documentation is now available on the web site.

Hopefully, these changes make tenScripting a much more complete development package.  I am continuing to distribute the complete source code instead of encapsulating much of it within compiled .DLLs, and you are encouraged to make modifications.  I only ask that you share these changes with me so that they can be incorporated into the package for others.