General Description
The main purpose of this plug-in is to monitor the health of battery devices in HS3 and to enable triggering of alerts from one central Virtual Device so that events do not need to be reconfigured as battery devices are added or removed from your system.
The plug-in can also monitor and report on the health of general devices in the system looking for inactivity and invalid states of devices.
The plug-in can also monitor, filter and report on the HS log including triggering events and scripts based on word, phrases or RegEx matches on log entries.
The three sections operate separately but under the umbrella of the single plug-in. You do not have to use all three sections of the plug-in.
The plug-in was written for HS3 but also works fine in HS4.
When the plug-in is first run it creates a virtual device named ‘Health Root’ which is used to display and report on the status of all monitored battery devices as well as trigger events on configurable alerts. The plug-in can monitor the following conditions:
Awake – Is the device Waking Up / Active / Responding
Battery Level
Battery Discharge Rate
Battery Life – Age since batteries last replaced
The alerts and trigger levels are fully configurable as global parameters and can be overridden locally for individual devices.
In its simplest form, without any configuration, the plug-in will monitor Z-Wave non-listening battery devices that regularly wake-up. Monitoring virtual child devices are created each time a new device wakes up. Depending on the wake-up time period set for each device it will take some time after the plug-in is first started for all devices to be detected, so be patient. On repeated wake-ups the sleep period is detected and battery levels are monitored. If the device fails to wake-up this will be reported in the status of the ‘health Root’ device so that events can be configured to warn of issues. Similarly the status will show battery alerts such as low level.
A simple event triggered by the status of the ‘Health Root’ device can alert you of issues with any monitored battery devices. The guide has example events for sending reports by Pushover message and email.
In addition to the above automatic detection of non-listening devices there are a number of different methods of monitoring battery devices. These can be used to monitor other types of battery devices and are not limited to Z-Wave.
General Health Monitoring is optional and is Off by default. This is a more complex feature intended for experienced users so please refer to the guide and ask questions in this forum about its use.
Log Monitoring and Event/Script triggering is optional and is Off by default. Please refer to the guide for details of its use.
Steve
The main purpose of this plug-in is to monitor the health of battery devices in HS3 and to enable triggering of alerts from one central Virtual Device so that events do not need to be reconfigured as battery devices are added or removed from your system.
The plug-in can also monitor and report on the health of general devices in the system looking for inactivity and invalid states of devices.
The plug-in can also monitor, filter and report on the HS log including triggering events and scripts based on word, phrases or RegEx matches on log entries.
The three sections operate separately but under the umbrella of the single plug-in. You do not have to use all three sections of the plug-in.
The plug-in was written for HS3 but also works fine in HS4.
When the plug-in is first run it creates a virtual device named ‘Health Root’ which is used to display and report on the status of all monitored battery devices as well as trigger events on configurable alerts. The plug-in can monitor the following conditions:
Awake – Is the device Waking Up / Active / Responding
Battery Level
Battery Discharge Rate
Battery Life – Age since batteries last replaced
The alerts and trigger levels are fully configurable as global parameters and can be overridden locally for individual devices.
In its simplest form, without any configuration, the plug-in will monitor Z-Wave non-listening battery devices that regularly wake-up. Monitoring virtual child devices are created each time a new device wakes up. Depending on the wake-up time period set for each device it will take some time after the plug-in is first started for all devices to be detected, so be patient. On repeated wake-ups the sleep period is detected and battery levels are monitored. If the device fails to wake-up this will be reported in the status of the ‘health Root’ device so that events can be configured to warn of issues. Similarly the status will show battery alerts such as low level.
A simple event triggered by the status of the ‘Health Root’ device can alert you of issues with any monitored battery devices. The guide has example events for sending reports by Pushover message and email.
In addition to the above automatic detection of non-listening devices there are a number of different methods of monitoring battery devices. These can be used to monitor other types of battery devices and are not limited to Z-Wave.
General Health Monitoring is optional and is Off by default. This is a more complex feature intended for experienced users so please refer to the guide and ask questions in this forum about its use.
Log Monitoring and Event/Script triggering is optional and is Off by default. Please refer to the guide for details of its use.
Steve
Comment