supported_modules:hs-wd100
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
supported_modules:hs-wd100 [2018/07/08 16:10] – added WD200 info for more click support James Sentman | supported_modules:hs-wd100 [2023/02/13 14:52] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 16: | Line 16: | ||
^Gesture^Code^ | ^Gesture^Code^ | ||
- | |Single Click|128| | + | |Single Click|1| |
- | |Double Click|131| | + | |Double Click|3| |
- | |Triple Click|132| | + | |Triple Click|4| |
- | |Hold|130| | + | |Hold|2| |
- | |Release of Hold|129| | + | |Release of Hold|1| |
- | + | ||
- | 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+! | + | |
+ | The [[supported_modules: | ||
Line 71: | Line 64: | ||
</ | </ | ||
+ | ===Set Data=== | ||
+ | via the [[dictionary: | ||
+ | |||
+ | ^Parameter^Description^value^Example^Default^ | ||
+ | |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, 1) to invert the direction if the switch is upside down|0| | ||
+ | |7|Sets the remote control ramp rate step resolution. | 1-99, 1 being the default and highest resolution|tell xUnit “name” to setData( 7, 1, 1)|1| | ||
+ | |8|Remote control Ramp step Speed|1-255 maps between 1 and 10 ms between steps| setData( 8, 1, 1) set to 1ms for a quick fade|3| | ||
+ | |9|Local control ramp rate step, the dim rate when controlled locally|1-99, | ||
+ | |10|Local control ramp rate step speed|1-255 note this value is 2 bytes long! 1=10 milliseconds| setData( 10, 2, 1) set to 1 for a faster local control|3| | ||
- | ===Known Issues=== | + | 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 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: | ||
- | 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.1531066209.txt.gz · Last modified: 2023/02/13 14:51 (external edit)