Skip to main content
Skip table of contents

HS4 Beta Release 4.2.17.4

Installation

NOTE PLEASE READ: This build includes a new feature called Conditional Actions. This allows you to have actions that are executed based on some conditions you specify. Because of this, the saved format of the events has changed. If you decide to go back to a previous version of HS4 you will lose all of your event actions unless you follow the Reverting to a Previous Version instructions below.

Manual Install

  • Windows

    If you need to perform a new install or the update is not available through setup, run the installer:

  • Linux

    For standard Linux tar file, check in setup for an update, or manually update with the TAR file:

Existing HS4 systems or HomeTroller Hubs

  1. Navigate to Setup > General and click the CHECK UPDATE button.
  2. Click the INSTALL BETA button.
  3. An Install Beta pop up appears. Click INSTALL to begin the installation. This may take several minutes to complete.


Reverting to a Previous Version

If you wish to revert to a previous version, you'll need to follow the steps below. Starting with beta 4.2.17.2, a new backup feature was added to back up your configuration whenever you update your HS4 version. The backup may be retrieved from Setup.

When running Beta versions of HS4 it is advised that you always perform a backup from the Tools menu. This is an alternate way to go back to a previous config.

Windows

  1. Uninstall the beta. Do not remove HS4 settings and temporary files.
  2. Install the previous version.
  3. Launch HS4 and navigate to Setup > General and click Edit Config
  4. Select the config file that was created when the beta was installed. The name will contain _before_4.2.x.x.json
  5. Check your events to confirm they're all there and the actions are correct

Linux

  1. Navigate to Setup > General and click REINSTALL UPDATE
  2. Once installation is complete, navigate to Setup > General and click Edit Config
  3. Select the config file that was created when the beta was installed. The name will contain _before_4.2.x.x.json
  4. Check your events to confirm they're all there and the actions are correct

Changes

4.2.17.4

  • On Windows, fixed event log being written to c:\Logs rather than Logs folder in HomeSeer install location.
  • Added a possible fix for the stuck spinner when checking for updates in Setup.

4.2.17.3

KeySummary
HS-1805

Conditional Actions: legacy plugins conditions not working when action group is moved

HS-1806

Conditional Actions: some events incorrectly show as "Not Configured" after a reboot

HS-1766

DoGlobalSearch is called twice when clicking the search button

HS-1809

Conditional actions with recurring trigger cause excessive log entries

4.2.17.1

KeySummary
HS-1803

Backup config folder when upgrading to a newer build

HS-1798

Event Group does not need to be written to events.json

HS-1797

Add scripting access to html tags format is: {{run_script_function script proc params wait singleinstance}} 

HS-1795

Access to the state object using html tags retrieves the wrong page

HS-1794

Add events access to json interface format is: /JSON?request=getallevents

HS-1783

Sweetalert popups not displayed in group actions and group conditions pages

HS-1777

Avoid refreshing the whole page when a JUI action or trigger is updated or saved

HS-1773

Possible duplicates of strTrigActInfo.UID

HS-1766

DoGlobalSearch is called twice when clicking the search button

HS-1765

404 page when hitting enter on a search from the root page

HS-1708

GetPropertyByType(dev, EProperty.FeatureDisplayType) returns PriorityDisplayType instead of EFeatureDisplayType

HS-1683

Conditional Actions Added to event builder

HS-1664

Editing 2 events in different browser tabs causes event corruption

HS-1499

HSTouch Server Warning "Exception on String Change callback: Value was either too large or too small for an Int32"

HS-1372

Copying a device Adds the word "copy" to loc1 and loc2 values



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.