Release Notes - Events2HVAC Event Automation - Version 1.4.3

Upgrade Information

If you are upgrading from v1.3.x or earlier versions, please review the system requirement changes section below.

• The latest version of .NET framework 4.5.2 or 4.6.x may require a server restart after installation.
• Makes sure you are not using SQL 2005 (v9.0.x) for the Events2HVAC database before you try to upgrade. The update scripts might fail with this version.
• Make sure you make database backups as with any upgrade. If there is a problem during upgrade and you need to revert back to the previous version, you must have a database backup of the previous version.
• If you want to take advantage of the Professional edition features (multiple event providers), you will need to upgrade your license to Professional.
• Your existing license will work as a "standard" edition license.
• Make sure you "Rediscover" your device interfaces if you are using any of the new actions in this release. Device Interface Manager - Rediscover Devices

Please review this link before updating software:

• Upgrading an existing installation of Events2HVAC

Improvements & Fixes

• New Feature: Filter R25 events by event type to prevent events from scheduling HVAC
• Schedule Importer: Improvements in performance and speed for importing large files
• Schedule Importer: Include latest fields for event and rooms
• Fix: In R25, don't allow a corrupt schedule entry fail the entire set of schedules
• Fix: Unhandled exception in R25 options after clicking reload space queries
• Fix: NetX TCP timeout parameter in settings stays at 5000 msec even thought the setting is changed. (*See NetX Upgrade Info below)
• Fix: Large event name lengths can cause MSMQ message to fail to queue the command due to exceeding max length of msg label property.
• Fix: misc sizing issues when Windows screen text size is at 125% magnification
• UI component updates
• Documentation updates

*NetX Upgrade Info

If using the NetX Device interface, the TCP timeout parameter in the NetX Options will be applied when E2H sends commands to NetX. Previously, the internal timeout was fixed at 5000 milliseconds even though the default setting was 1000 milliseconds. As a result you might get some timeout errors after the upgrade. You can change this setting back to 5000 milliseconds to restore this back to what it was actually using.