• Fixed Z-Wave lockup (introduced in 2.5.0.51)
• Fixed HSSentry setting missing in setup for PRO version

• Detects proper IP address of main adapter card when virtual servers are installed
• Fixed issue with Z-Wave saved scenes not being saved in the database
• Fixed Z-Wave thermostats not updating

• Z-Wave locks are now automatically polled for the battery level once a day
• Polling support for the Evolve LTM-5
• Changes to the updater so developers can reference more than one package with a single URL
• Some reported security issues with the web server are resolved
• New Z-Wave optimization option to optimize without adding return routes (speeds up initial optimizations), Z-Health now optimizes 3 times before adding return routes.

• Web server automatically picks a new server port if default port is in use by another application

• Z-Wave association is automatically added for Leviton receptacle
• Z-Wave changes to better handle some newer devices that support multiple sensors
• Fix for issue where a Z-Wave door lock may not be controlled and an error was logged
• Minor internal changes to Z-Wave support
• Fix for Z-Wave optimize where an error was generated but the optimize actually succeeded

• Fix for init error when using the Cooper Z-Wave USB interface
• Added support for YALE Z-Wave locks
• Minor changes to support HomeSeer SE hardware
• Add limited support for AEON Labs motion sensor (not yet complete)
• Fixed polling setting not available for 2GIG Z-Wave thermostats
• Added auto association set for Everspring Z-Wave door sensor
• Added support for Fortrezz Z-Wave siren strobe
• Added Celsius support for Z-Wave thermostats
• Fixed startup issue when using 4 or more Z-Wave interfaces (Z-Trollers)

• Fixed bad sensor readings with Homemanageables temp sensor
• Fixed lockup when using more than 2 remote Z-Wave interfaces
• Fixed web server to return the correct IP address if running on a system that is not on a network

• Fix for licensing issues on HomeTroller
• Changed Z-Wave thermostat status page to not display fan state if not supported in hardware
• Changed locks to have their battery polled.
• Set polling from web page to wait for request command to complete, this removes some network congestion when polling.
• Added support for Aeon Labs home energy monitor
• Added more status graphics icons
• Fixed memory leak with hs.GetURLIE
• Fixed Z-Wave thermostats operating mode not reporting correctly
• Fixes to the conversion of bytes from Z-Wave into a value, this fixes some temperature readings from reporting incorrectly when they go below 0.
• Fixes to support the HomeManageables temp sensor properly.
• Fixed playing wave files on HSTouch clients
• Added common port numbers for Ethernet Z-Wave interfaces (to setup screen)
• Fixed some web pages not returning HTTP header
• Fixed error on some systems not being able to convert phone messages to MP3 format
• Change to IVR files to fixe replay of messages
• Changed voice recognition parsing to detect empty voice commands to stop grammar errors
• Fixes for HSEvent for Generic events being called too much.

11/29/2010 HS2 / HSPRO Build 2.5.0.1 changes

• Fixed Z-Wave locks not operating properly on remote Z-Wave interfaces
• Fixed license errors when registering software

11/24/2010 HS2 / HSPRO Build 2.5.0.0 changes

• Changes to Z-Wave support for stability and support of more Z-Wave hardw

2/01/2010 HS2 / HSPRO Build 2.4.0.11 changes

• If Rescan (Full) is used, it now forces the retrieval of the Z-Wave command classes from the node.
• Fixed an error in the calculation of sunset and sunrise times for timezones having offsets that were not whole hours - e.g. Newfoundland's offset from GMT is 3.5 hours.
• 2.4.0.10 - Several changes with the handling of commands sent to multiple Z-Wave devices at once, including scene commands, as it was possible previously for an error reaching a node to cancel the send in the middle of the operation. (Thanks to Bob @ Cooper Wiring for finding that one!)
• Added LED control and LoadSense enable/disable control for ZRR150 in device properties.
• All Deprecated API warnings can be disabled from the "Disable obsolete API procedure warning messages" setting in setup.
• Fixed Z-Wave startup to always leave the Z-Troller at 40K mode
• 2.4.0.8 - Fixed issues with Multicast Z-Wave commands.
• 2.4.0.7 - Fixed an issue with values from Z-Wave sensors containing negative numbers not being handled correctly.

12/23/2009 HS2 / HSPRO Build 2.4.0.6 changes

• Fixed an issue with VR on Hi-Phone and Windows 7
• Fixed a bug with adding a secure device resulting in a database warning.
• Fixed an issue with Z-Wave thermostat triggers not working right.
• Extended the field sizes on many of the event actions in response to user requests, so that they would display more information while editing.

12/02/2009 HS2 / HSPRO Build 2.4.0.3 changes

• Added missing graphic files from the 2.4.0.2 update installer.
• Fixed an issue where HS internal access to the device enumerator sometimes caused an error to appear in the log.

11/25/2009 HS2 / HSPRO Build 2.4.0.2 changes

• Non-Listening Z-Wave devices that supported beaming were treated as non-listening devices only - detection of devices that utilize beaming has been added so that they can be treated as a listening device.
• The method used to select the status icon for Z-Wave temperature measuring devices had certain values that resulted in the "Unknown" temperature icon being displayed - this has been corrected.

11/09/2009 HS2 / HSPRO Build 2.4.0.1 changes

• Changes to support wildcards (* and ?) on directory phone numbers for matching purposes. e.g. 410-313-* matches all numbers that start with area code 410 exchange 313. 410-555-12?? matches all numbers in the range 410-555-1200 through 410-555-1299.
• A web page - "Log Keywords/Colors-Styles" (/lcsc) was added which allows you to configure keywords, and associated colors or style names for entries in the HTML log view. The page can be accessed from the Tools page as well. In this page, you can enter keywords that can be searched for in log entries, and an associated RBG color or style name to be used for that log entry. The style can be added to any of the style sheets HomeSeer supports.
• New, updated icons for use with the device status page have been created. Also, new settings.ini entries were created to control the size of the status icon. There are 2 new settings that control the size of the status icons. The new icons are 32x32 so they display nicely on touch screens. HSTouch will automatically use these new icons when displaying status. HomeSeer scales them to 24x24 by default. If you want to change this add the following 2 settings to your settings.ini file to the [Display] section. If you do not want any scaling, set the size to 0:
  StatusImageSizeWidth=size
  StatusImageSizeHeight=size
• Added device change logging to the Z-Wave status updates and changed the log type on the older device logging lines. When a device is controlled through the UI, script, or event action, "Device Control" is the log type. When a device is updated as a result of state information arriving, "Device Update" is the log type.
  " Select All" checkboxes in status page and event page now work with FireFox.
• New WriteLogEx is created. WriteLogEx is just like WriteLog but with an optional parameter "COLOR" to specify the color to use for the log entry - colors are string values in #rrggbb format (e.g. "#008000"
• 'Light Optomize Network' feature added to the Manage Z-Wave Controller page - utilizes "Null Operation"
  Remote Z-Wave interfaces that have the installer library are now converted into being primary controllers, which means optimization will use the remote interface.
• The way that Z-Wave devices are created and handled in HomeSeer has been restructured to be driven by the command classes that a device supports. This should allow HomeSeer to support most of the functionality of new devices as they are put on the market without having to wait for a HomeSeer release to support them. Because of this sweeping change, YOUR Z-WAVE DEVICES NEED TO BE FULLY RESCANNED.
• The devices that need some MANUAL INTERVENTION on your part for them to operate properly are the currently supported battery based sensors - the HomeSeer HSM100, the ACT ZIR000 motion detector, the Hawking Technologies motion detector and door/window sensor. For these devices, you will need to delete all of the current devices associated with these sensors, and then use "Import Devices" to have HomeSeer re-create the devices. When you remove the devices, you will lose the ability to find the events that referenced these devices for triggers or actions, so if you use the sensors extensively and cannot modify the events from memory, then please use this helpful tool: Go to the main device for the sensor - this is typically the motion detector device or door/window sensor device - and go to its device properties. Using the drop-down list of node numbers where the node number for the sensor is displayed, change the node number to the entry at the top of the list - the blank entry - and then click "Save" to change the node number for the device to zero. This will effectively remove it from the system as far as HomeSeer is concerned without actually removing the device. After you do an "Import Devices" and get your new set of devices created and have renamed them and set their location, you can click on one of the old devices, choose the device operation at the bottom of the page "View event references for a device." and it will display for you a page with all events that reference that device in one way or another. On this page you can click on the events and modify them to use the new device. When you are done making the changes, you will be returned to the event reference listing page that is empty - you are done. You can now delete the old devices.
• Devices that employ Z-Wave secure communications are now supported. Secure communications is done with Zensys Development Kit levels 4.28 and later, although 5.02 is the generally accepted production version. Library version for ZDK 5.02 is 2.48. However, devices requiring Zensornet technology (Schlage LiNK) are supported only in ZDK 5.02, 4.5 or later (library versions vary). Thus, to work with the Schlage lock, you must confirm that the library version for the HomeSeer Z-Wave controller is 2.48. (Library versions for Patches to ZDK 5.02 include 2.51, 2.64, and 2.78 - yes, we know Zensys cannot count.) The Z-Troller does not currently meet the qualifications to work with the Schlage LiNK products. All non-secure functionality is still supported in this release of HomeSeer. To add the Schlage lock to HomeSeer, enter the program code to the lock, when the Schlage button blinks, press it, then press 0. This is the same as pressing the button on any other Z-Wave device. At this point, in HomeSeer, click on the Add Device button on the Z-Wave manage page. Make sure you are within a couple of feet of the lock. You can add the lock close to HomeSeer. When you then install the lock, make sure you optimize it from the HomeSeer device properties screen.
• For devices that use the USER CODE command class (usually security devices), a new button will appear on the device properties page ("User Codes") - this page allows you to add/remove/edit the user access codes for the device. User codes are set at location numbers. Specific information for the Schlage LiNK products: There are 19 user code locations, so the locations available are numbered 1-19. When a user code is entered at a lock, the alarm device for the lock will display the user code location number corresponding to that user code. In the final release this will be a triggerable piece of data. The Schlage lock codes are 4 digits in length. Schlage does not return the user codes when asked - the locks simply report whether the location is occupied or not and return all zeros for the user code, so for Schlage locks you will see a series of XXXX characters when a user code location is occupied. To change a user code, delete the code at a location and then add the new code back in to the same location.
• Added support for AEON Labs Z-Stick so Z-Seer functions work properly (Z-Stick now available in the HomeSeer Store)

• A new global temperature scale setting on the General tab of the system settings will determine how temperatures for all Z-Wave devices except thermostats will be reported. The initial setting for this will be taken from the HSM100 scale setting if that exists in your INI file. Regardless of whether a temperature from an HSM100 (always Fahrenheit) or FortrezZ WWA-01 (always Celsius) is provided, HomeSeer will convert the temperature if necessary to display it in the scale you choose. The HSM100 INI setting will no longer be used.
• All of the Z-Wave controller functions that used to pop up a status window have been replaced with realtime status updates in the same browser window. This improves the performance of all of the controller functions and eliminates replication issues due to timing problems.
• Added support for the Z-Wave Meter class
• Added event actions to initiate a poll and reset meter accumulations
• Fixed startup search for local subnet IP address - it was returning the first one it found, which is not always valid - changed it to try to return a valid one.
• Fixed a bug where using the multi-device operations to delete a device and it was the last device in a location or location2, the UI would switch to using location "All" but it did not actually choose "all" so it displayed nothing.
• The database password is removed at shutdown, but it was not being removed when backup copies of the DB were created, or when you do an Open or Save As - now it should be removed in all of those cases.
• The system log files are now named with a YYYY-MM-dd format instead of the format using the short month name because of globalization issues. Log pruning now uses the file's last modified date/time to determine when to delete them rather than pulling them from the name of the file.
• Fix to properly disable UPnP from starting if it was disabled in the configuration.
• Changed X10InterfaceStatus to write a message to the log that the command is no longer valid - it was never re-connected since HS 2.0.0.0.
• Fixed database delete error on event actions.
• Fixed an issue with CrLf characters, generated by unknown causes, creating "unknown post" error messages - this was commonly seen with the GC-100 plug-in IR signal learning page, but can affect all web page posts.
• Changed the startup network connection test to eliminate false negatives that users were seeing.
• Fixed an issue with deleting value/status/graphics pair items from a device in HSPro - deleting works now.
• Fixed the issue with uploading WAV files for "Play WAV File" event action.
• Modified FTP to never log an error to the HomeSeer log, and to always append the error information to what is returned by FTPLastError.
• Fixed Lightolier Compose devices not being able to be controlled by HSTouch
• Fixed thermostat devices that use the thermostat scripting support now show the button controls.
• Address book wildcard entries are always searched after non-wildcard entries in all internal procedures that search the address book.
• Changed the configuration UI to list speaker client port numbers which may not be used.
  Removed nondescript log statements of type "Info" and replaced the type with something more meaningful.
  A change to hs.GetURLIE to prevent a possible memory leak
• The HomeSeer help page was consolidated as the on-line resources are now all located on the support page at HomeSeer.com
• Changed so that HomeSeer opens up the browser at startup (if configured to do so) using the HomeSeer machine IP address instead of Localhost or equivalent IP address.
• Removed generation of caller name and number to be sent to other phones when CID detected (PRO Version only) via Way2Call as it did not work reliably.
• Added ini setting to hsphone.ini: "enable_cid_name_generation" to send caller name to phones (Set to True or False) (PRO version only)
• Added ini setting to hsphone.ini: "enable_message_waiting_led" to light message led on phone (Set to True or False) (PRO version only)
• Fixed an issue with the device replacement function where duplicate devices were left after the replacement
• Added/Fixed in PRO version, closing application from system tray icon closes the HSSentry application.
• On HSPRO, if an exeception is thrown, the web server is stopped so HSSentry can restart the system.
• On HSPRO the HSSentry can get the HomeSeer IP address from the settings.ini file using the setting: SentryIP=[ipaddress]
• Programmer's API Changes
• Updater can now handle MSI installer packages.
• Added [IS64BIT] and [ISNOT64BIT] to the list of commands available in updater packages so that developers can execute a different set of commands on 64 bit operating systems.
• Fixed Z-Wave remote switches not appearing in the list of devices to be added to a SAVED scene.
• Fixed issue with HS not recognizing change in HSM100 sensor if 2 sensors reported at the same time.
• Fixed lockup issue with SmartStick USB Z-Wave interface
• Changed Z-Wave polling to be suspended during all forms of replication (protocol and application)
• USB Smartstick now processes data faster
• Fixed remote switches not appearing in the list of devices to be added to a SAVED scene.
• Fix so that when a manual scene is programmed into a controller, the name of the saved scene is wiped out so the saved scene can be deleted.
• ON for a dimmer in a Z-Wave scene is now level 99 instead of 255. 255 now causes a warning to be displayed that the device may not support it. Only Cooper products support 255 to turn on a device to its preset level, but not as part of a scene.
• Totally removed Z-Wave thermostat script support. Use the Z-Wave Thermostats Plug-in for status and control.
• Changed the layout of Saved Scene page so that it looks better, added ability to rename scenes, and reworded a button at the bottom.
• When doing a re-scan on a scene controller, HomeSeer will no longer load manual scene with scene data from the controller if there is a saved scene already configured.
• Saved Scenes on controller buttons now use their own scene IDs. (Update: The Scene ID of the saved scene is displayed initially, please choose a different scene ID and this UI issue will be corrected in the next release.)
• Scenes can be tested in both saved scenes area and controller button configuration.
  Optimization now skips controllers - controllers should be updated using replication. Optimization does nothing on controllers.
• A delay is added whenever a controller is programmed with a scene to give it time to absorb (store) the scene information.
• Replication Successful (false positive) message fixed on application data replication.
• Application data replication is not attempted with generic (e.g. handheld) controllers.
• Fixed the scene controller button device UI issue where it displayed the saved scene's scene ID as the current scene ID instead of selecting a new, unused scene number.
• Changed the detection of listening devices so that motion detectors converted to be always powered will appear as a listening node.
• Fixes for Leviton wall controllers with less than 4 buttons where 4 button devices were still being created.
  The number of events sent to a Cooper controller was not throttled down to 32 or less - this was only apparent in versions after 2.3.0.0 - this is fixed.
• Fixed an issue with Event Days not right in Cooper Replication - Saturday and Sunday were not being handled.
• Fixed an issue where "Poll Devices" (device status page button) was attempting to poll Z-Wave nodes with invalid Node ID numbers.
• Z-Health now sends "Null Operation" commands in addition to the optimization. Sending NOPs improves routing because it helps populate "Most Frequently Used" and "Preferred Route-Through" node tables in controllers.
• The order of some processing changed in Z-Wave replication so that it will get to the Cooper data exchange faster.
• Fixed the number of Z-Wave nodes transferred in a Cooper Aspire scene to 32 or less.
• Non-scene devices in a Z-Wave scene are activated after the scene capable devices.
  More device types can be added to a scene since Cooper controllers and HomeSeer can operate non-scene devices in a scene.
• Fixed it so that requests to poll a Z-Wave node cannot stack up - only one request per node ID can exist.
• Added support for a European temperature sensor marketed by LS Controls.
• Fixed an issue where indicator LEDs were attempting to be set by HomeSeer on Leviton controllers, none of which support the indicator classes.
• The Z-Wave thermostat plug-in has been integrated into HomeSeer. It still appears as a plug-in on the Interfaces tab, but it is automatically enabled if HomeSeer detects a Z-Wave thermostat in the system. You can leave the Z-Wave thermostat plug-in DLL in your root HomeSeer folder - it will not do any harm - or you may remove it.
• The "Door Lock Alarm" device created when a Schlage lock is added to the system can now be used as a value change trigger item to know when certain lock related events happen, most noteably the use of one of the user codes.
• Fixed an issue that caused some ACT Z-Wave nodes to have devices created for command classes that the node can control, but are not a feature of the node itself.
• Devices that report temperature and luminance (e.g. HSM100) now have new graphics associated with their status values.
• Several of the Merten "System M" devices are now working with HomeSeer on a "best effort" basis. These devices are battery powered and do not stay awake, so you have to continuously tap the buttons while they are being added to the network or when you want to change associations. (These are Europe-only Z-Wave devices)
• The LS Control ES 861 series Temperature, Humidity, and rotary control are now supported. (These are Europe-only Z-Wave devices)
• When an association is added with HomeSeer, and when HomeSeer optimizes a node, a "return route" is added to insure that a path is established between the two nodes. For example, if you associate an HSM100 at node 57 with HomeSeer at node 1, then a return route is established from 57 to 1 so that the signals can reach HomeSeer when they are issued by the source node. However, previous versions of HomeSeer did not always wait for the return route command to complete as it was not monitoring the correct return status. This has resulted in perhaps 50% or more of the return routes to NOT be established properly. In certain networks, a lack of return routes can cause routing failures - thus communication failures. While this basic error has been fixed, it is now possible for an association or optimization to succeed, but then for the "add return route" to fail if Z-Wave could not find a route. Additionally, adding more return routes than what Z-Wave allows results in a failure of the route to be added, so existing routes must be removed and routes must be re-added for the current set of nodes that a device is associated with - this means that associations and optimizations will take longer to complete because of the additional command overhead.
• The Z-Wave Who Am I (/zwho) page has been modified to be more readable, and it now lists the Z-Wave Basic, Generic, and Specific node type information.
• Z-Wave debug logging now produces two log files rather than one.
• When a device corresponding to a Cooper Wiring Z-Wave scene controller button was clicked OFF in the HomeSeer UI, the corresponding LED did not always turn off on the controller - this has been fixed.
• Changed Delete/Add Return Routes (Z-Wave) so that they are not carried out if the source node is a controller (ignores add/delete route).
• Changed the temperature and luminance status display to only show the value to the tenths if it is a fractional value.
• Fixed Cooper Z-Wave devices - previous betas were not saving the node name and node locations to the devices properly.
• Added the ability to do a full Rescan (Sync) on all Z-Wave devices from the Z-Wave Manage Controller page. This function, as well as Light Optimization, may be cancelled by the user part way through the process.
  Added buttons on most of the Z-Wave Controller Page functions to turn on/off auto-scrolling of the page. When you click Auto Scroll On, the page will move down every 2 seconds to keep the latest output lines showing on the page. Jump back to the top and click Auto Scroll Off to disable this if you want to scroll up/down to review the history on the page. At the end of the procedure, the page will jump to the bottom so that you can review the final results.
• Added support for instant status for the newer Intermatic switch products. (Product Type 0x4841) Because this product does not support instant status, the way we made it work makes it more like "almost instant" status - the status update takes about 1 to 2 seconds to update in HomeSeer.
• Z-Wave thermostats set to auto mode now allow setting of both setpoints.
• HSM100 multisensor updates light and temp when motion is detected, new option in HSM100 config that controls this.
• When adding a new node, only the new node is scanned, not all nodes.
• Added secure command classes to the ZWave Who Am I page, and changed format of the device names/links on that page slightly.
• When a Z-Wave thermostat is controlled, it is then polled so it's status is updated.

12/23/2008 HS2 / HSPRO Build 2.3.0.19 changes

Fixed event names not transferring properly on Cooper controller replication.
Fixed an issue with Cooper controller replication resulting in duplicate events in HomeSeer being created.
Saved Z-Wave scenes will now default to a ramp rate of "device default" when they are newly created.

12/18/2008 HS2 / HSPRO Build 2.3.0.16 changes
WHAT WAS FIXED IN THIS RELEASE

Errors generated by plug-in web page links were causing portions of the "Plug-Ins" link page to not be generated - this has been addressed.
Modified FormatAction to display (Missing Device) when a device is not present for the "Remove Delayed Actions" action - will add more missing device placeholders for other actions in the future.
Fixed an issue with the log file pruning not able to handle month abbreviations in the log file names that are more than 3 characters.
Fixed voice recognition error for command strings of the format (|) missing a command
Fixed email handing when MIME parts are not complete
Fixed formatting of the log entry when setting a wake-up interval on a Z-Wave device to 24 hours or more.
Fixed a bug with Z-Wave Optomization where it would check for the best remote interface (HS Pro, multiple interfaces) even though it was not told to (not set to (Auto))
Fixed hs.SetDeviceString to trigger callbacks after device string is actually changed.
Changed logging of device commands to only log commands, for devices that do not exist, for commands issued to addresses in the X-10 range.
Fixed an issue where the control panel, X-10 command, does not process multiple addresses like it says it will - only does the first one - now fixed.
HSM100 sub-devices are changed again - if NO LOG is set, then they do not log but they still get queried for their values, but if they are HIDDEN then they will not be queried for their values.

11/13/2008 HS2 / HSPRO Build 2.3.0.0 changes
WHAT IS NEW IN THIS RELEASE

Added pop-up confirmation dialog for Z-Wave reset controller command
Changes to support 'Manual with Conditions' trigger type. The only difference between Manual with Conditions and Manual, is that conditions can be applied to the Manual with Conditions type and they will appear when viewing the event in the event list.

Changed the method used to store/restore the device state file.
hs.LastVoiceMailInfo, with the MessageInfo argument, now fully encodes the XMLdata in UTF-8
Voicemail messages now play on more non-IE browsers
Removed the indicator as to whether an IR signal was present at a given location - it was not accurate for most IR interfaces.

Script Function AppStarting(Optional ByVal wait As Boolean = False) As Boolean now has a "wait" parameter which causes it to wait until AppStarting is TRUE
Geographical locations are now stored in the file "locations.csv"
Added numerous small performance enhancements
Added support for UPNP discovery of HomeSeer - allows UPnP enabled PCs to find and access the HomeSeer web interface more easily.
Changed the Special Day condition to allow for a Fifth day occurrence in the month to handle months with 5 weeks in them.

Windows scripting engine is automatically registered with Windows if it was not already
MyHomeSeer Connect service now supports email notifications of IP address changes - enter the email address to use in the MyHomeSeer Connect configuration.

Added ReplaceVariables for script use (used to be just for plug-in callbacks and internal use)
Removed zstat.thm script from devtypes.cfg file - ZW thermostats supported by plug-in only.
New feature to enable voice dialing by microphone - the configuration of Phone Line 1 is where it can be enabled. You must still pick up the phone to hold a conversation!

Added DebugMode of Debug_VR (1024).

When the speaker client connects via the local LAN without needing a password because the web server is configured to bypass password checking on the local network, HomeSeer will still log a warning message if the user credentials would not allow a remote network login (e.g. password is wrong, user ID lacks adequate capabilities, etc.)
|
Three new HSPhone script commands were added to facilitate the use of the PCI modem speaker phone:
Public Function LINEAnswerSpeakerPhone(ByVal line As Integer) As Integer
Public Function LINEEnableSpeakerPhone(ByVal line As Integer) As Integer
Public Function LINEDisableSpeakerPhone(ByVal line As Integer) As Integer
To assist in keeping the database free of corruption, especially in environments with frequent power loss, HomeSeer will now: A) Automatically restore the latest backup copy of the database from the Backup folder when it detects a corrupted and unrepairable database, and B) will not write (save) the entire database if HomeSeer is shut down within 5 minutes of startup.
Created a queue and a separate thread to process script callbacks for status changes (RegisterStatusChangeCB) so that HomeSeer is not delayed waiting for scripts to launch.
Added an optional parameter, UTF8 (as Boolean) to GetURL to indicate whether UTF8 decoding should be used for the retrieved web page.
Added a new function to retrieve web pages (GetURLEx) which combines some of the features of GetURL and GetURLImage, and if the output is text or a web page written to a file, then HomeSeer attempts to determine the page encoding so that the page can be decoded properly.

Web Server Changes:

Changed Home to Start, Changes to make the Start page its own Link.
Changes to allow non-Latin characters in device and event names
Changed webserver to use UTF-8 URL encoding instead of windows-1252 to allow more compatibility with non-Latin characters
Changes to the web server so that (for example) a plug-in page of \Status is not misinterpreted to be the \Stat page since now we are checking for HomeSeer pages before plug-in pages.
Added a new Search page at /srch
Added a new Code List page at /code so you can see which letter codes and unit numbers have been used.
Added Z-Wave Node "Who Am I" page at /zwho
Moved Z-Wave Associations to their own page at /mnza
Created Z-Wave Saved Scene Management page at /mnzs
Added a new utility "Replace Devices" page at /repl
Menu Link Changes:
A new menu link item exists - "Tools" - which contains links to several of the tool web pages (Help, About, Search, Control Panel, etc.) and it is ENABLED BY DEFAULT the first time you run this version. With the Tools button enabled, all of the utility buttons on the Tools page are removed from the link buttons. If you disable the Tools button, you can go back to your currently set link customizations.
A new menu link item exists - "Plugins" - which contains the plug-in provided link buttons all on one page. This button is ENABLED BY DEFAULT the first time you run this version, but may be disabled to have your plug-in link buttons appear separately.
New IP Blocking feature - attempts to access the web server that fail a number of times within a time period between attempts are blocked from further access to the system for a period of time.
Settings may be added to the IPBlock section of HomeSeer's settings.ini file to change the default parameters:
Parameter: FailCount Default: 3 Description: The number of failed login attempts within the set time period before IP Blocking is enabled.
Parameter: FailInterval Default: 10 Description: The interval between failed login attempts to be counted toward IP Blocking - value is in seconds. A setting of 10 seconds with a failure count of 3 means that 3 failures 10 seconds or less apart will trigger IP Blocking.
Parameter: BlockTime Default: 30 Description: If an IP address is blocked, this is the period of time it will be blocked from access to the system - value is in minutes.
Changed Response.BinaryWrite to use the web server encoding (UTF-8), and created Response.BinaryWriteDefault to use default encoding.
Modified ASP processing to remove parameters after the ASP filename so that the system would not report that the file could not be found - parameters passed in the URL of an ASP are not processed anyway.
Modified Response.BinaryWrite (ASP pages) to not "convert to text" the data to be written as this can cause text encoding issues.

Z-Wave Changes:

If there is an error with a remote Z-Wave interface at startup, the system will continue to re-try the connection.
Z-Wave device configuration settings can now be set on multiple devices at once - e.g. Set the default ramp rate for all of your Cooper Dimmer Masters to the same rate at once.
New "ZHealth" Z-Wave Network Health Service added - enable it at the bottom of the Z-Wave Controller Management Page (/mnzw) ZHealth works within the hours you specify to continuously optimize your network, one node at a time, allowing you to sleep while your network adjusts to any changes made. At the end of the ZHealth time period you specify, statistics are shown on what ZHealth accomplished during the time period.
New Z-Health configuration feature only appears if the HomeSeer Z-Wave controller is the primary controller.
Z-Wave polling is disabled by default for devices that support instant status.
Added the display of the Z-Wave Node Number in parenthesis after the address in the device status page - e.g. Q23 (45)
Created /zwho (See Web Server Changes)
Created /mnza (See Web Server Changes)
Created /mnzs (See Web Server Changes)
Removed the "Scene Events" feature (sorry for the inconvenience) - added "Saved Scenes", which will allow you to create Z-Wave scenes and give them names, which then allow you to use them to program several scene controller buttons if so desired.
Cooper Aspire events downloaded from controllers are now created as an Aspire "Saved Scene" so that you can use it/apply it in other areas.
New Z-Wave Event Actions!
Activate/Deactivate a Scene (Saved scene, Aspire saved scene, or a scene from a scene controller button)
Enable/Disable Cooper's Panic (Alarm) Mode
Send All Lights On/All Lights Off commands
Set Protection Mode on Devices (e.g. Child safety or local control lockout)
Set/Reset a Cooper device's indicators (e.g. Turn dimmer or scene controller lights on/off)
Added Generic Z-Wave parameter configuration option to the device properties/config screen - devices NOT known to HomeSeer can now have configuration parameters set for them if you know the parameter and value to set.
Added a "Resync" button on the device properties page, so you can have HomeSeer query just that device for its capabilities and reset how the device is set up in HomeSeer to match the capabilities.
A new configuration checkbox option on the Z-Wave pages (/mnzw, /mnza, /mnzs) allows you to indicate that HomeSeer is not left running at all times or is not a part of the system (used for installation only) - this prevents HomeSeer from adding itself to scenes and device associations for instant status purposes, which can hamper the Z-Wave if a node tries to communicate with a node that is not present.
Added a new script command: ZWaveAction(DeviceRef as Object, ActionType as Integer, Optional Parm1 as Object, Optional Parm2 as Object) as String - See the documentation for details.
The optimization of Z-Wave nodes has been significantly enhanced to improve the reliability of the optimization. Note: To completely clear out old (potentially bad) routes from a node, it is necessary to complete 4 successful optimizations.
(HS Pro) Interfaces configuration now allows you to name remote ZW interfaces, UI is new - no longer lists node IDs. Device properties now allows you to select which interface to use for the node to communicate ZWave with.
Added remote interface number to ZWHO page (HS Pro Only)
Z-Wave Support Added For:
Wayne Dalton WDUSB-10 Z-Wave Interface
Danfoss Radiator Controller
Merten Battery Wall Switch
ACT ZTW230
ACT ZCU201 Z-Wave interface
Hawking Technologies' Door/Window Sensor
Hawking Technologies' Motion Detector
Cooper Battery Operated Accessory Switch (Supports On/Off/Dim status on the HomeSeer device representing the switch)
When a source device is selected on the Associations page, the Z-Wave node ID for that device is displayed below it.
The list of fixed locations used by Cooper Aspire handheld remotes is now shown if you have the option set to exchange application data with the handheld remote. You can select one of these locations or create your own as has always been the case.
If you have multiple (remote) Z-Wave interfaces, the Z-Wave Associations page now lists those remote interfaces using their friendly name.
Removed "On/Off Only" scene number option from the manual scene configuration page as it is not needed for HomeSeer to register on/off transitions of scene/zone controller buttons.
Changes to support application data replication with Cooper controllers with firmware after version 1.1.2
Added a node neighbor status indicator on the Z-Wave Who Am I page.

Developer/SDK Changes:

Changes to support new EV_TYPE_GENERIC CallBack, and to queue/thread the actual processing of the callback requests.
Implemented a 3-strike system for removing callbacks for unresponsive plug-ins.
Added ConditionUIHTML functionality.
Changed the config-change callback (devices or events) to include a 4th parameter, which is the type of change - Add, Change, Delete, or Unknown.

WHAT WAS FIXED IN THIS RELEASE

Fixed several issues related to non-English (non-US culture) systems, involving licensing and the database.
Commands from web pages are now logged if logging is enabled for the controlled device
Fixed "Bad devices" error message to display on Z-Wave manage associations page.
Removed tool tips for up/down buttons on caller ID box
Made minor wording changes on e-mail setup page.
Fixed licensing on systems using a decimal symbol other than a dot.
Eliminated false error message on shutdown "Error Processing email..."
Fixes to licensing (enhanced licensing)
Changes to ensure that an event still runs if the prior trigger time is in the future
GetURL and GetURLIE, with the StripTags argument, now properly decode all standard HTML character entities
Fixed a bug with the "Value Change" Trigger when using sub-types of "For At Least" and "Exactly" - when one of those types triggered, all events of the same trigger type would run.
Fixed hs.ExecX10 with wait did not control devices owned by plugins
Fixed device value/status/graphics pair editing page (HS Pro) - it now works with HTML in the status.
Fixed com port script handling stripping commas from received data
Fixed issue with enabling plug-ins with special characters in the name (e.g. CM11A/CM12U)
COM Port script function errors should be resolved.
Initialization error with some X10 interfaces should be resolved.
A long standing issue where the removal of a device caused an entire multi-device event action to be removed has been fixed.
IP address terminology in some log messages was corrected.
Fixed an event display issue where events manually triggered and manual with conditions were being treated the same.
Future scheduled events by voice via the phone should now work properly (e.g. will not trigger immediately).
The COM port prompt box was showing up on the Interfaces tab of setup sometimes when it should not have been - this has been fixed.

Web Server Fixes:

Fixed display of apostrophes in location names, device names, and event names
Fixed a bug in the device status page so that if a device had no name, it would at least display a "______" for purposes of getting to the link to modify the device properties.
Fixed the "view events referencing a device" display. Leave the (Device Reference) event page and return to it, and the list was empty - now it displays the events as it should.

Z-Wave Fixes:

Fixed Z-Wave associations not being displayed when using remote interfaces
The "Optimize All" function will skip over battery operated devices and other nodes that are not always listening for Z-Wave commands.
When a non-controllable Z-Wave node is operated via the HomeSeer interface (e.g. secondary controllers), HomeSeer no longer sends commands to the node resulting in a command failure message being logged.
Fixed an issue where synchronizing remote Z-Wave interfaces ended with a blank status popup screen.

Developer/SDK Fixes:

Fixed an issue with ConfigDevicePost that prevented it from being called when deleting a device.