From 8197097e1da51c00844fbe45f100f4347dc87910 Mon Sep 17 00:00:00 2001 From: jackchi Date: Thu, 6 Apr 2017 14:15:08 -0700 Subject: [PATCH] Revert "Added health-check for FortrezZ Siren Strobe Alarm" This reverts commit 7a7a08ea6ea413de32a5fb67ba219fff077e1bbc. --- .../smartthings/zwave-siren.src/.st-ignore | 2 - .../smartthings/zwave-siren.src/README.md | 42 ------------------- .../zwave-siren.src/zwave-siren.groovy | 14 ------- 3 files changed, 58 deletions(-) delete mode 100644 devicetypes/smartthings/zwave-siren.src/.st-ignore delete mode 100644 devicetypes/smartthings/zwave-siren.src/README.md diff --git a/devicetypes/smartthings/zwave-siren.src/.st-ignore b/devicetypes/smartthings/zwave-siren.src/.st-ignore deleted file mode 100644 index f78b46e..0000000 --- a/devicetypes/smartthings/zwave-siren.src/.st-ignore +++ /dev/null @@ -1,2 +0,0 @@ -.st-ignore -README.md diff --git a/devicetypes/smartthings/zwave-siren.src/README.md b/devicetypes/smartthings/zwave-siren.src/README.md deleted file mode 100644 index ed17b1e..0000000 --- a/devicetypes/smartthings/zwave-siren.src/README.md +++ /dev/null @@ -1,42 +0,0 @@ -# Z-wave Siren - -Cloud Execution - -Works with: - -* [FortrezZ Siren Strobe Alarm](https://www.smartthings.com/works-with-smartthings/other/fortrezz-water-valve) - -## Table of contents - -* [Capabilities](#capabilities) -* [Health](#device-health) -* [Troubleshooting](#troubleshooting) - -## Capabilities - -* **Actuator** - represents that a Device has commands -* **Alarm** - allows for interacting with devices that serve as alarms -* **Battery** - defines device uses a battery -* **Health Check** - indicates ability to get device health notifications -* **Polling** - represents that poll() can be implemented for the device -* **Refresh** - _refresh()_ command for status updates -* **Sensor** - detects sensor events -* **Switch** - can detect state (possible values: on/off) - -## Device Health - -FortrezZ Siren Strobe Alarm is polled by the hub. -As of hubCore version 0.14.38 the hub sends up reports every 15 minutes regardless of whether the state changed. -Device-Watch allows 2 check-in misses from device plus some lag time. So Check-in interval = (2*15 + 2)mins = 32 mins. -Not to mention after going OFFLINE when the device is plugged back in, it might take a considerable amount of time for -the device to appear as ONLINE again. This is because if this listening device does not respond to two poll requests in a row, -it is not polled for 5 minutes by the hub. This can delay up the process of being marked ONLINE by quite some time. - -* __32min__ checkInterval - -## Troubleshooting - -If the device doesn't pair when trying from the SmartThings mobile app, it is possible that the device is out of range. -Pairing needs to be tried again by placing the device closer to the hub. -Instructions related to pairing, resetting and removing the device from SmartThings can be found in the following link: -* [FortrezZ Siren Strobe Alarm Troubleshooting Tips](https://support.smartthings.com/hc/en-us/articles/202294760-FortrezZ-Siren-Strobe-Alarm) \ No newline at end of file diff --git a/devicetypes/smartthings/zwave-siren.src/zwave-siren.groovy b/devicetypes/smartthings/zwave-siren.src/zwave-siren.groovy index d368610..9ee8071 100644 --- a/devicetypes/smartthings/zwave-siren.src/zwave-siren.groovy +++ b/devicetypes/smartthings/zwave-siren.src/zwave-siren.groovy @@ -20,7 +20,6 @@ metadata { capability "Actuator" capability "Alarm" capability "Battery" - capability "Health Check" capability "Polling" capability "Refresh" capability "Sensor" @@ -28,7 +27,6 @@ metadata { fingerprint inClusters: "0x20,0x25,0x86,0x80,0x85,0x72,0x71" - fingerprint mfr:"0084", prod:"0313", model:"010B", deviceJoinName: "FortrezZ Siren Strobe Alarm" } simulator { @@ -60,11 +58,6 @@ metadata { } } -def updated(){ -// Device-Watch simply pings if no device events received for 32min(checkInterval) - sendEvent(name: "checkInterval", value: 2 * 15 * 60 + 2 * 60, displayed: false, data: [protocol: "zwave", hubHardwareId: device.hub.hardwareID]) -} - def createEvents(physicalgraph.zwave.commands.batteryv1.BatteryReport cmd) { def map = [ name: "battery", unit: "%" ] if (cmd.batteryLevel == 0xFF) { @@ -126,13 +119,6 @@ def both() { on() } -/** - * PING is used by Device-Watch in attempt to reach the Device - * */ -def ping() { - refresh() -} - def refresh() { log.debug "sending battery refresh command" zwave.batteryV1.batteryGet().format()