supported_modules:hs-wd100
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
supported_modules:hs-wd100 [2018/09/07 12:57] – added Vera gesture code info James Sentman | supported_modules:hs-wd100 [2018/09/07 13:10] – [Set Data] James Sentman | ||
---|---|---|---|
Line 13: | Line 13: | ||
This will be called almost immediately when the switch is tapped. Two values are sent to you in the handler, the button number and the gesture number. This lets you tell which paddle on the switch was tapped, up or down, and how it was tapped, single tap, double tap, tap and hold etc... | This will be called almost immediately when the switch is tapped. Two values are sent to you in the handler, the button number and the gesture number. This lets you tell which paddle on the switch was tapped, up or down, and how it was tapped, single tap, double tap, tap and hold etc... | ||
- | For the Home Seer switches the button index is always 1 for the up paddle and 2 for the down paddle. Note that the switch documentation lists a different gesture code than is returned by the Vera. When checking in the centralScene handler use the Vera Gesture Code below. The following gestures are currently supported by the Vera. | + | For the Home Seer switches the button index is always 1 for the up paddle and 2 for the down paddle. The following gestures are currently supported by the Vera: |
- | ^Gesture^Code^Vera Gesture | + | ^Gesture^Code^ |
- | |Single Click|128|1| | + | |Single Click|1| |
- | |Double Click|131|3| | + | |Double Click|3| |
- | |Triple Click|132|4| | + | |Triple Click|4| |
- | |Hold|130|2| | + | |Hold|2| |
- | |Release of Hold|129|1| | + | |Release of Hold|1| |
The [[supported_modules: | The [[supported_modules: | ||
Line 65: | Line 65: | ||
===Set Data=== | ===Set Data=== | ||
- | via the [[dictionary: | + | via the [[dictionary: |
^Parameter^Description^value^Example^Default^ | ^Parameter^Description^value^Example^Default^ | ||
Line 75: | Line 75: | ||
These dimmers let you set the local ramp rate and the remote control ramp rate separately, but as is standard in ZWave you cannot include a ramp rate in individual commands. Each one is made of 2 different parameters. The step resolution which appears to be the number of steps it goes through to get to the preset level, and the speed at which it switches between the steps. For some LED lights it may make sense to set a faster ramp rate since they tend to not come on immediately. Some experimentation with the 2 values may be needed to find the ramp rate that you like best for a specific application. | These dimmers let you set the local ramp rate and the remote control ramp rate separately, but as is standard in ZWave you cannot include a ramp rate in individual commands. Each one is made of 2 different parameters. The step resolution which appears to be the number of steps it goes through to get to the preset level, and the speed at which it switches between the steps. For some LED lights it may make sense to set a faster ramp rate since they tend to not come on immediately. Some experimentation with the 2 values may be needed to find the ramp rate that you like best for a specific application. | ||
- | |||
===Known Issues=== | ===Known Issues=== | ||
As of XTension 9.4.6 the central scene events may be sent more than once. This is a known issue and as soon as I can figure out how to filter repeats of them I will do so. Until then your scripts may run more than once. This isn’t generally a problem as turning on or off a device that is already at the same level doesn’t cause any trouble except extra commands to the systems. If you wish you may be able to check the time delta of the unit and ignore a central scene event if it is less than say 2 seconds since it changed state. Or save off the current date in the central scene handler to a local script variable and compare that script variable with the current date when it’s called. If it’s less than 2 or 3 seconds since it last handled a central scene command then ignore it. | As of XTension 9.4.6 the central scene events may be sent more than once. This is a known issue and as soon as I can figure out how to filter repeats of them I will do so. Until then your scripts may run more than once. This isn’t generally a problem as turning on or off a device that is already at the same level doesn’t cause any trouble except extra commands to the systems. If you wish you may be able to check the time delta of the unit and ignore a central scene event if it is less than say 2 seconds since it changed state. Or save off the current date in the central scene handler to a local script variable and compare that script variable with the current date when it’s called. If it’s less than 2 or 3 seconds since it last handled a central scene command then ignore it. |
supported_modules/hs-wd100.txt · Last modified: 2023/02/13 14:52 by 127.0.0.1