supported_modules:hs-wd100
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
supported_modules:hs-wd100 [2018/07/08 15:42] – created James Sentman | supported_modules:hs-wd100 [2018/09/07 00:41] – James Sentman | ||
---|---|---|---|
Line 21: | Line 21: | ||
|Hold|130| | |Hold|130| | ||
|Release of Hold|129| | |Release of Hold|129| | ||
+ | |||
+ | The HS-WD200+ dimmer also adds the following extra gestures | ||
+ | |||
+ | ^Gesture^Code^ | ||
+ | |Quadruple Click|133| | ||
+ | |Pentuple Click|134| | ||
+ | |||
+ | Yes, thats right you can do up to a 5 click macro for each button with the HS-WD200+! | ||
+ | |||
+ | |||
When single tapping the default switch behavior is to control the local load as well as send the central scene information. | When single tapping the default switch behavior is to control the local load as well as send the central scene information. | ||
Line 61: | Line 71: | ||
</ | </ | ||
+ | ===Set Data=== | ||
+ | via the [[dictionary: | ||
- | ===Known Issues=== | + | ^Parameter^Description^value^Example^ |
+ | |4|Sets paddle’s load orientation| 0 = top of paddle turns load on or 1 if you need to invert it so that the bottom of the paddle turns the load on.| tell xUnit “name of unit” to setData( 4, 1, 0) to set it to normal orientation | | ||
+ | |7|Sets the dimmer remote ramp rate step resolution| 1-99, 1 being the default and highest resolution|tell xUnit “name” to setData( 7, 1, 1)| | ||
+ | |8|Remote Ramp Step Speed|1-255 maps between 1 and 10 ms between steps| setData( 8, 1, 200)| | ||
+ | |9|Local ram rate step, the dim rate when controlled locally|1-99, | ||
+ | |10|Local Ramp Rate Step Speed|1-255 note this value is 2 bytes long! 1=10 milliseconds| setData( 10, 2, 1)| | ||
- | These dimmers require a neutral connection so work well for LED or CF lighting. However they do seem to cause some of my LED lighting to flicker somewhat at high dim levels. I’m not sure why this is but they are by no means the only Z-Wave dimmer that has this problem. It doesn’t bother some people, it drives me crazy. The lights can randomly flicker every so often. The solution is to dim them until the flickering stops. The light will remember that new value as the On level so will return to this level when you manually click on the switch. Go into XTension and manually dim them to the same level via the UI, this will set the preset level. Make sure the dimmable type of the unit is set to “Simulated” and now issuing turnon commands in XTension will result in the switch always going to that level as well. Alternatively you could set the max level of the light to that level under the [[xtension_manual: | + | |
+ | |||
+ | ===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