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 13:10] – [Set Data] James Sentman | ||
---|---|---|---|
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 [[supported_modules: | ||
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 64: | ||
</ | </ | ||
+ | ===Set Data=== | ||
+ | via the [[dictionary: | ||
- | ===Known Issues=== | + | ^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| | ||
- | These dimmers | + | These dimmers |
+ | |||
+ | ===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