3.1.2.7 - 5/19/2025

• Corrected some minor text errors on Global Settings page.
• Corrected a bug where an irrelevant warning message was shown in the log during Control Device Sync when ForceSync is False.
• Corrected a bug where temperature suffix was shown as °C (even if units are °F) on configuration web page during editing.

3.1.2.5 - 7/24/2024

• Beta now release version

3.1.2.3 - 6/24/2024

• Updated the method used to filter devices in building sensor drop down lists so that temperature sensors created by the ZWave Plus plug-in are included.
• On the VStats Config Page, finessed behaviour of drop down lists for sensors and added spinner whilst available device lists are being built.
• On the VStats Config Page, device lists were being rebuilt unnecessarily, such as when VStats were collapsed or expanded, causing long unresponsive pauses on large systems. This has been changed so they are only rebuilt when the page first opened, after starting the plug-in, or when the ‘Rebuild Device Lists’ button is pressed.
• On the VStats Config Page, added a note with instructions on editing the Device Type String for any missing sensors that want to be selected.
• Enclosed status strings in <div></div> tags to improve formatting in HS4 in some situations.
• Ability to swap any VStat back and forth between Heating and Cooling from controls on the parent device of the VStat and therefore, also from Events as a Control Device Action. Refer to new section 7.2 of the guide.

3.1.2.2 - 6/4/2024

• Ability to swap any VStat back and forth between Heating and Cooling from controls on the parent device of the VStat and therefore, also from Events as a Control Device Action. Refer to new section 7.2 of the guide.
• Ability to Collapse and Expand VStat details on VStat configuration page.

3.1.2.1 - 12/29/2022

• Fixed a bug where Mode Names on the Config page were returning to their defaults after a restart.
• Adjusted formatting of Control Values status on VStats page.
• Split Config pages into two pages. Now there is a ‘Global Settings’ page and a ‘Virtual Stats’ page.

3.1.1.2 - 1/18/2022

• VSTAT_Scheduler.exe is also updated for the changes in the data structure of the VStats. If you run the scheduler from somewhere other than the HS root folder, make sure to copy the new version over your previous.
• There is now a configurable delay period during which the OpenWindow Target Temperature reduction won’t trigger. This avoids the heating switching on and off rapidly if a door/window is briefly opened then closed again.
• The user can now select one or more window/door sensors for each VStat to trigger the OpenWindow feature.
• Added new features to OpenWindow detection.

3.1.0.7 - 3/31/2021

• Corrected bug importing EasyTrigger Day Schedules with multiple segments
• Corrected minor bug where Export schedule names were sometimes not in sync with import
• Added a check to prevent overwriting an existing EasyTrigger Day Schedule with a Week Schedule
• Corrected an error importing EasyTrigger schedules where start or end times were related to Sunrise or Sunset. These times are now set based on the Sun times on the day of import. If you want a VStat to stay synced with Sun times then set a recurring event to re-import the schedule each week.
• Added Day Schedules to EasyTrigger schedules imports. These are expanded to a week of identical days.
• Default Low SetPoint range for Fahrenheit corrected to 41-77. This only affects new VStats or if an existing VStat is rebuilt. This was incorrectly set as 51-62 for Fahrenheit VStats.
• Corrected a bug that only allowed schedules on Sunday up to 23:50. VSTAT_Scheduler.exe is also updated for the same bug so if you run it from anywhere other than the HS3/4 root folder you will need to copy the new version to your desired location.

3.1.0.6 - 9/28/2020

• Work round for a bug in HS4 which affected deleting VStats. The DeleteDevice function for the root device returns ‘False’ in HS4 even though the device is actually deleted. The plug-in was interpreting this as an error and aborting the deleting of the VStat. This update ignores the return from the function and proceeds regardless.

3.1.0.5 - 7/20/2020

• NOTE – THIS IS THE MINIMUM VERSION FOR RUNNING IN HS4. If upgrading from HS3 to HS4 then install and enable this version, or higher, before upgrading. Format of data stored in root devices plugExtraData changed due to work round a bug in HS4’s conversion of PED to JSON storage.
• VSTAT_Scheduler.exe is also updated for the changes in the data structure of the VStats. If you run the scheduler from somewhere other than the HS root folder, make sure to copy the new version over your previous.
• Testing.
• VStat initialisation moved out of InitIO.

3.1.0.2 - 4/20/2020

• Minor change to routine that filters available temperature sensors in the drop downs on the config page. Necessary due to a bug in newer versions of the Z-Wave plug-in. Doesn’t affect existing VStats.

3.1.0.1 - 3/2/2020

• Corrected a bug causing an error on entering the Config page in certain circumstances.

3.1.0.0 - 2/24/2020

• Added the ability to designate VStats as Slave and sync optional features to Master VStats. The selected features of a Slave VStat will follow changes to its Master. See the new section 7.1 of the guide.
• Added full status value ranges beyond the control range for SetPoint devices so values beyond the range of control values will be displayed. This was mainly because using the Temperature Offset of Slave VStats it is possible for the value of a Slave Setpoint to be set beyond the normal range limits. This just ensures the value is displayed. Applies to new VStats but can be applied to existing VStats by using the ‘Rebuild’ button on the config page.
• Also added temperature status graphics to SetPoint devices. Again only applies to new or rebuilt VStats.
• Corrected a small bug where submitting a new current temperature to a dummy VStat with no internal temperature sensor assigned didn’t trigger a check if heat required.
• VSTAT_Scheduler program has been updated so that the full week of schedules is now shown on the right hand side of the window when creating and editing schedules.
• VSTAT_Scheduler.exe is also updated for the changes in the data structure of the VStats for Master and Slave operation. If you run the scheduler from somewhere other than the HS3 root folder, make sure to copy the new version over your previous

3.0.9.9 - 1/20/2020

• Corrected bug preventing multiple internal sensors being added to new VStats beyond number 5.

3.0.9.8 - 1/8/2020

• Corrected bug preventing the 21st VStat being created. VSTAT_Scheduler.exe is also updated.
• VSTAT_Scheduler.exe is also updated. If you run the scheduler from somewhere other than the HS3 root folder, make sure to copy the new version over your previous.
• Corrected a bug where the end points of schedules imported and exported to EasyTrigger were 15 minutes out (1 segment). Note that if you are importing schedules that you have previously created by exporting you might need to adjust the end points by 15 minutes.
• Removed the limit on the number of VStats so you can configure as many as you require.
• Made a change so that if a VStat has no Internal Sensors defined then it will show a Text Box Control on the Current Temperature child to allow the current temperature to be set manually. When at least one Internal Sensor is added the Control is removed so the current temperature is status only. If the sensors are subsequently removed the Control will be re-added.
• Added the ability for VStats to control devices that aren’t just On/Off switches. For each VStat the default On/Off values sent to the controlled device can be overridden to custom values. There is a global setting which limits the lists of Control Devices to On/Off devices as previous behaviour. Unchecking this makes all HS devices, which have at least 2 control values, available for selection. Each VStat then has the option to configure the control values sent to the device. The defaults are to Limit to On/Off devices so updating shouldn’t change the behaviour of existing VStats. The above change alters the format of the data stored in the Root device of each VStat which means that the VSTAT_Scheduler.exe is also updated. If you run the scheduler from somewhere other than the HS3 root folder make sure to copy the new version over your previous.
• Added option to ignore a temperature sensor, where there are multiple input sensors, if the last change time hasn’t updated for more than a certain interval. The Highest, Average or Lowest temperature will be based on the remaining active sensors. If there is only one sensor it won’t be ignored. The option and time interval is a global setting on the Config page. The default for this is Off so updating should not change the behaviour of existing VStats.
• Minor change to code in InitIO routine returning PI version.

3.0.9.3 - 4/26/2019

• Additional Debug logging added.

3.0.9.2 - 2/5/2019

• Corrected bug introduced in 3.0.9.1. converting global settings with decimals between locales.

3.0.9.1 - 2/4/2019

• In the unlikely event that a user changed their system locale number formatting from comma to decimal separator after the plug-in had been enabled, decimal global settings such as the temperature swings were being read from the SDJ-VStat.ini file without the decimal point. The plug-in now checks the number format when loading the ini file at startup and converts it if the locale has changed.
• Corrected a small issue with status graphics for some negative numbers in Current Temp and Target Temp. The ranges configured didn’t cover all negative numbers so some would show without a graphic. If you notice the issue on existing VStats use the Rebuild VStat button on the Config page to rebuild the devices which will correct the status graphics.

3.0.8.9 - 1/4/2019

• Added the ability to set the Boost Timer increment between 5 and 720 minutes. Defaults to original 15 minutes.
• Added the ability to select multiple internal sensors and to use the lowest, average or highest value of the selected sensors for the current temperature of a VStat See updated section of guide on Creating VStats for information on how to configure a VStat to use multiple temperature sensors. NOTE – The data structure of the VStats is upgraded in this version to incorporate the extra features. The VSTAT_Scheduler.exe program is therefore also updated. If you run this from a location other than the HS3 root folder you will need to copy the new version to your desired location.
• Changed DeviceType, DeviceSubTypes and ControlUse properties for new and rebuilt VStats to better integrate with HSTouch standard project and Alexa.

3.0.8.6 - 12/10/2018

• Sensors with Device Type [String] containing ‘temp’ added to lists.
• For new or rebuilt VStats Target Temperature child DeviceType now set to SetPoint.

3.0.8.5 - 10/17/2018

• Corrected a bug where mode changes to Auto for multiple VStats within one ‘Then’ action of an event were only being honoured for one VStat.