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-Health Version History

    Version : 3.0.8.5
    • If running under HS4 general device report file names now don’t have spaces as these caused problems in the HS4 web interface.
    Version : 3.0.8.4
    • General Devices - Enabled ability to include devices that aren’t owned by a plug-in, i.e. virtual devices. These now appear as ‘No Interface’. They can of course be hidden and not scanned.
    Version : 3.0.8.3
    • General Devices configuration page is now OFF by default with a checkbox to enable.

    Version : 3.0.8.2 (Beta)
    • Corrected small bug in reported Last Change Time for devices in Invalid State.

    Version : 3.0.8.1 (Beta)
    • PollingDepth added for interfaces in General Health section. Default is 1 but if set higher then for a physical device represented by a group of devices the pi will poll that number of devices until a successful result

    Version : 3.0.8.0 (Beta)
    • Corrected bug where Check at Time wasn’t being accepted if in 12 hour clock format.

    Version : 3.0.7.9 (Beta)
    • Corrected bug where failed devices weren’t being added to list of devices for possible exclusion.

    Version : 3.0.7.8 (Beta)
    • Corrected minor bug where child devices were being recreated for hidden interfaces.

    Version : 3.0.7.7 )Beta)
    • Further major updates to the General Health Checking Features which are still in beta. The General Health Checking is optional and separate to the Battery Health Checking and should not interfere with the way the plug-in has operated up until now.
    • General Health Checking can now create a group of devices for monitoring and alerting. There is a General Health Root device plus a child device for each interface which is selected, e.g. Z-Wave, Insteon, etc.
    • Configuration pages separated so that there are now 3 pages, “Plug-in Configuration’ that is common to Battery and General (currently just LogLevel) plus the original page now renamed ‘Battery Devices’ and the new page ‘General Devices’.
    • General Health reports now produced in html format for better viewing.
    • For General Health checking, in addition to scanning for inactivity and polling, the plug-in can scan for devices in ‘Invalid State’. This can certainly occur with Z-Wave devices and may apply to devices of other interfaces, although I have not seen any on my system.
    • The guide has been updated to cover the General Health Checking features.

    Version : 3.0.7.6 (Beta)
    • Trial addition of General Health Checking Features – Refer to the thread in the SDJ-Health forum for details of this Beta version. The guide has not been updated yet but there is a basic guide to the new features posted on the forum.
    • Minor adjustment so that Battery Activity and Polling checks trigger immediately after restarts.

    Version : 3.0.7.5
    • Adjusted display of average discharge rate information.
    • Average discharge rate information is a global option but now only displays if the Display Battery Discharge Rate is selected which can be configured for individual devices.
    • Some re-wording of the Config page.

    Version : 3.0.7.4
    • Added option to display Average Battery Discharge Rate information in addition to the Battery Discharge Rate. This is refreshed each day for all devices and individually each time a new battery reading is received. See the updated section in the guide

    Version : 3.0.7.3(A)
    • Modified some text under Heartbeat Monitoring in the guide.

    Version : 3.0.7.3
    • Added the option to choose not to display the various types of monitoring in the device string of the monitoring children and the reports in the root device string. For each type of monitoring, i.e. wake-ups/level/discharge rate/life, if you choose not to Alert you can also choose not to Display the value. These options can be set globally on the Config page and overridden locally for individual devices on the SDJ-Health tab, if required.
    Version : 3.0.7.2
    • Corrected some spelling inconsistencies.
    Version : 3.0.7.1
    • Corrected a minor bug whereby if a device being monitored was deleted then when the monitoring child was removed the SDJ-Health root would still show the state of the deleted monitoring child until another device triggered a higher status alert.
    • Minor change so that the reference of the last device to raise an alert is saved over restarts of the plugin.
    • Minor change where displayed sleep period minutes is properly rounded where seconds is 30 or greater.
    • Change to improve the way monitoring of devices is automatically changed when a wakeup message or a poll is detected for a device previously monitored by a different method. This rarely occurs in practice.
    Version : 3.0.7.0
    • Minor change to the hidden status value of the Root device so it matches the status. This shouldn’t affect any reporting or event triggering.

    Version : 3.0.6.9
    • Corrected a bug in device grouping which was inadvertently introduced in an earlier update.
    • Removed RepairDeviceGrouping option as the ZWave bug has now been corrected by HS so this feature is no longer necessary.

    Version : 3.0.6.8
    • Corrected a minor bug in FindBatteryChild.
    • The history display in a device string now shows dates only, without times, for a more concise display. The full history display from the SDJ-Health tab of each monitored device shows the full date and times.
    Version : 3.0.6.7
    • Corrected a bug where text input boxes were showing truncated when viewing with the Safari browser.
    Version : 3.0.6.6
    • ForceBackToRoute option renamed to RepairRootDeviceGrouping. This option is there to help correct an issue in HS where the device grouping for some devices, particularly battery devices, is lost when the ZWave pi starts up. Previously the issue was that the root device’s relationship status would be erroneously changed to StandAlone but the list of child associations was still in the root. The issue appears to have got worse in that the list of child relationships is also erased. With the RepairRootDeviceGrouping option selected the plugin will repair the grouping by searching for child devices that are related to the parent , restoring the relationship and setting the parent relationship status back to Parent_Root. The change in name of the option reflects the more aggressive repair. Only devices that are monitored by the plug-in are repaired. Note that if you previously had this option selected it will default back to unselected so to use it you will need to reselect it after upgrading. If you have never seen loss of grouping in your HS system then leave this option unselected.
    • Some minor changes in logging where warnings that are unimportant have been relegated to debug logging.
    Version : 3.0.6.5
    • Cured bug that caused an error when building the list of battery devices due to Insteon devices having two childs with ‘battery’ in the Device Type (string). Now correctly ignores the Low Battery Warning device. Insteon battery devices can now be monitored using the Activity Monitoring method.
    • Cured bug where newly created monitoring devices had their battery last replaced date set to many years ago. Default is for it to be initially set to the last change time of the battery child.

    Version : 3.0.6.4
    • Corrected a minor bug that sometimes caused battery last changed date to be miss-positioned in history list.

    Version : 3.0.6.3
    • Work around added to retain monitoring of a device by polling even if its Supports_Status property gets changed from True to False by HS. This has been known to happen although it may have been a unique case.

    Version : 3.0.6.2
    • History buttons now only displayed for devices with database logging turned on.

    Version : 3.0.6.1
    • Added BatteryFactor that can be applied to devices that report a battery range that is greater or less than 100 to convert to 0-100%.
    • If batteries are replaced in a device set to check by polling and level is updated by HS3, the monitoring device will now change to ok without waiting for next polling interval.

    Version : 3.0.6.0
    • Now able to handle battery values above 100.

    Version : 3.0.5.9
    • Precautionary-Now force HS to save device after writing PED to root monitoring device.

    Version : 3.0.5.8
    • Added some polling messages to Log Level 1.
    • Added some additional error checking.
    • Removed some redundant code

    Version : 3.0.5.7
    • Corrected a bug that affected some installations using comma as decimal delimeter. Failed to read PEData for child devices.

    Version : 3.0.5.6
    • Updated device images to sdj-health.png.

    Version : 3.0.5.5
    • Changed the Device Type of SDJ-Health monitoring devices to support the Plug-in API property to improve selection on the Device Management page. Existing devices are updated on first run of this update.

    Version : 3.0.5.4
    • Added the last battery change date in battery history lists.

    Version : 3.0.5.3
    • Corrected some minor bugs which affected Local Settings overrides.

    Version : 3.0.5.2
    • Corrected a bug in writing discharge rates to the SQLite if your system uses ‘,’ for the decimal separator.

    Version : 3.0.4.9
    • Default polling interval changed to 360 minutes for new installations only. If you are upgrading and use the polling method for any devices then I would suggest you consider whether the polling interval that is set is shorter than necessary. Default was 60 minutes. You can change this globally from ‘Plug-ins>SDJ-Health>Config’.
    • Device configuration SDJHealth tab – Re-coded as there was a small possibility of confusion if you clicked on ‘Set All to Global’ and then moved away without Saving or Cancelling.
    • Device configuration SDJHealth tab - Additional Information added. Reference IDs and Monitoring Method. Full battery history list in scrollable region if you have Log to Database selected. Button for trimming (deleting) stored history data for the individual device.
    • Config Page - Additional parameter added to restrict the maximum number of stored battery readings for each device when logging. This prevents the database growing indefinitely. Click ‘Trim Now’ to trim the full database immediately, however each devices stored data is trimmed if necessary each time a new value is added.
    • Clicking the ‘History’ button on a device now cycles back and forth between the normal details and the battery history, if logging is selected.

    Version 3.0.4.8.
    • Installation and updating now uses updater_override.txt method.
    • SDJ-Health Guide added to //Docs folder.
    • Optional logging of battery levels to SQLite database added.
    • History button added to child devices to display logged battery levels.
    • ReTrigger button added to Health Root
    • Minor bug fixes

    Last version before guide was 3.0.4.3.
    Last edited by SteveMSJ; April 21st, 2019, 08:44 AM.

  • #2
    Sorry I had neglected to keep this version history up to date. I have however been updating it at the end of the guide document.

    Updated to 3.0.6.2 which has been submitted to HS so should be released shortly.

    Steve

    Comment


    • #3
      Version 3.0.7.5 adds an optional feature to display average discharge rates, see the updated guide.

      Click image for larger version  Name:	Average Discharge.JPG Views:	0 Size:	21.9 KB ID:	1351732

      Battery Discharge Rates

      Each time a new battery level is reported the plug-in calculates the discharge rate over the period from the previous battery level. It is calculated as the percentage change in level divided by the period of time since the last reported battery level. If the level increases the discharge rate is reported as 0% per day. If 2 different battery levels are received close together the calculated rate can be very high. For example if the device reports 90% and then 1 hour later 80% that is a change of 10% over 1 hour which will be reported as 240% per day. Some devices are fairly erratic in reporting battery levels which can result in wildly fluctuating discharge rates. For this reason alerting on discharge rates is rarely useful which is why it is turned off by default. As with other parameters the global settings for Alert and Display can be overridden for individual devices if required.

      In addition to the battery discharge rate discussed above, which only changes when a new battery level is reported, additional information on the average discharge rate can be displayed in the status string of each monitoring child. To display the additional information select the global option Show Average Discharge Rate. The additional information consists of the range and the average rate of discharge from when the batteries were last replaced to today. It is updated each day and when a new battery level is received.

      This works best if Log To Database is selected and the date the batteries were last changed is set correctly, either automatically when the battery level jumps by more than the specified amount, or manually. If there are battery levels recorded in the database then the highest reading since the last replacement date is used as the starting level, otherwise the batteries are assumed to have started at a level of 100%.

      Steve

      Comment


      • #4
        Plug-in has been updated to 3.0.8.3. and submitted to the updater. It might be a few days before HS add it to the general updater but it can still be installed from the beta section in the meantime.

        This is the first non-beta version with the Health Checking of General Devices added. This is OFF by default so if you want to experiment, turn the new features on from the SDJ-Health>Config page. The new features are separate from Battery Device checking so should not interfere with anything you already have set up.

        Comment

        Working...
        X