Announcement

Collapse
No announcement yet.

Version History

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Version History

    SDJ-VStat Version History

    3.1.0.2 Minor change to the 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 Corrected a bug causing an error on entering the Config page in certain circumstances.

    3.1.0.0
    • 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 Corrected bug preventing multiple internal sensors being added to new VStats beyond number 5.

    3.0.9.8 Corrected bug preventing the 21st VStat being created. VSTAT_Scheduler.exe is also updated.

    3.0.9.7
    • Removed the limit on the number of VStats so you can configure as many as you require.
    • 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.
    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.

    3.0.9.6
    • 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.
    • 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.

    3.0.9.5
    • 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.

    3.0.9.4
    • Minor change to code in InitIO routine returning PI version.

    3.0.9.3
    • Additional Debug logging added.

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

    3.0.9.1
    • 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.

    3.0.9.0
    • 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
    • Added the ability to set the Boost Timer increment between 5 and 720 minutes. Defaults to original 15 minutes.

    3.0.8.8
    • 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.

    3.0.8.7
    • Changed DeviceType, DeviceSubTypes and ControlUse properties for new and rebuilt VStats to better integrate with HSTouch standard project and Alexa.

    3.0.8.6
    • 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
    • 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.

    3.0.8.4
    • Added ability to alter the Target Temperature by entering a value on the device management page, or from events, in addition to the increase/decrease buttons. This will apply to new VStats but to upgrade an existing VStat click on the ‘Rebuild VStat’ button on the SDJ-VStat Config page.

    3.0.8.3
    • Added an action that can be used in events to Import Schedules by name into VStats. Also name of current schedule added to the root device string.
    NOTE – The devices are updated to store the additional parameter of the current schedule name so a new version of VStat_Schedule.exe is also required. If you are running VStat_Schedule.exe from somewhere other than the HS3 root folder you will need to replace it with the latest version which the updater will have placed in the HS3 root folder.

    3.0.8.2
    • Cured a bug where OpenWindows wasn’t honoured in some circumstances including a restart.
    • Removed some redundant code causing duplicate control device syncs.
    • Force HS save after changing root device PlugExtraData. Not essential.

    3.0.8.1
    • Sensors with Device Type [String] containing ‘weather’ added to lists.

    3.0.8.0
    • Major change introduced Cooling VStats.
    • The name of an existing VStat can now be changed on the Config page. Name conflicts detected.
    • Mode names can now be edited on Config page as well as having a different set for Heating and Cooling VStats.
    • Format of Scheduled Graphic png file names changed to avoid risk of conflict with other images.
    • Away graphic added for Cooling stats. On Off graphics added for Cooling controls.
    • SetPoint ranges revised and new ranges added for Cooling VStats.
    • Control Use properties added to devices where appropriate.
    • Voice command turned off by default for all devices.
    • Various minor code fixes.

    3.0.7.1
    • Corrected bug detecting Celsius scale on Linux.

    3.0.7.0
    • Control Device lists are now populated with all devices which have both On and Off control status pairs rather than just devices with ‘switch’ in the device type string.
    • Added global option ForceSync which is True by default. When true commands are sent to Control Devices even if the status hasn’t changed. If you change to False then commands are only sent if HS thinks the status of the device has changed. Safe option is True.

    3.0.6.9
    • Open Window feature added. A new VStat child is created called Windows which can be used to reduce the target temperature. See updated section in guide. Config page updated to allow Open Window temperature reduction and minimum temperature to be set for each VStat.
    • Section on swapping schedules using EasyTrigger added to the end of the guide.
    • Section on HSTouch added to the end of the guide.

    3.0.6.8
    • Background changes to way lists of devices are built for the config page.

    3.0.6.7
    • Corrected bug for regions using a comma as the decimal place symbol. This should now work correctly in all regions. If you are updating from an earlier version and your region is set to use the comma you will need to go into the SDJ-VStat/Config page and re-enter the values for the Global settings as they will probably have changed to 0 or very large numbers.

    3.0.6.6
    • Config page revised to speed up opening on large systems. Dropboxes only appear for selection of sensor/control devices when clicked on, or for a new VStat.

    3.0.6.5
    • Bug corrected in selection lists where more than one device had exactly the same loc1 loc2 and name. Ref # added to sensor and control device names.

    3.0.6.4
    • Operating State added to Config page so that individual VStats can now be set to use or not use schedules. Guide updated to show the Manual operating State.

    3.0.6.3
    • Max number of VStats increased from 10 to 20.

    3.0.6.2
    • Fairly major update to add compatibility with Fahrenheit as well as Celsius temperature scales. VStat configuration, default values, etc are now based on HS3 global setting of Temperature Scale.

    3.0.6.1
    • Minor bug cured which occurred if SetPoints were adjusted whilst in boost mode.
    Last edited by SteveMSJ; January 4th, 2020, 08:00 AM.
Working...
X