supported_modules:hs-wd200
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
supported_modules:hs-wd200 [2018/07/09 13:53] – added the actual central scene codes that this has beyond the wd100 James Sentman | supported_modules:hs-wd200 [2021/05/30 17:08] – added hubitat info James Sentman | ||
---|---|---|---|
Line 4: | Line 4: | ||
- | The HS-WD200+ is Home Seer’s latest wall dimmer. In addition to all the commands and support of the [[supported_modules: | + | The HS-WD200+ is Home Seer’s latest wall dimmer. In addition to all the commands and support of the [[supported_modules: |
- | ^Gesture^Code^ | ||
- | |Quadruple Click|133| | ||
- | |Pentuple Click|134| | ||
- | visit the hs-wd100+ article | + | NOTE: as of Vera firmware version 1.7.4452 Vera Edge / 1.7.4453 Vera Plus / 1.7.4454 Vera Secure they have changed |
+ | The available Central Scene gesture codes on the WD200+ dimmers are: | ||
+ | |||
+ | ^Gesture^Code^Code Prior to 1.7.4 vera update^ | ||
+ | |Single Click|0|128| | ||
+ | |Double Click|3|131| | ||
+ | |Triple Click|4|132| | ||
+ | |Hold|2|130| | ||
+ | |Release of Hold|1|129| | ||
+ | |Quadruple Click|5|133| | ||
+ | |Pentuple Click|6|134| | ||
+ | |||
+ | |||
+ | The button code of the UP paddle is always 1 and the down paddle 2 so the combination of those two data points will let you trap any gesture from either paddle and perform different actions based on them. | ||
+ | |||
+ | The single click always controls the local load, but the other multi-clicks do not control the local load but only send the centra scene event. If you wish to do a sort of “all off” with a double click down you will have to script the changing of the load as well. | ||
+ | |||
+ | |||
+ | Something like this example might be used to control all the rooms lighting with a double click while still being able to control the dimmer locally without affecting the whole room if you wish. | ||
+ | |||
+ | < | ||
+ | on centralScene( theButton, theGesture) | ||
+ | |||
+ | if theButton is equal to “1" then | ||
+ | write log “the top paddle was pushed" | ||
+ | | ||
+ | if theGesture is equal to “3" then | ||
+ | -- the switch was double clicked on | ||
+ | write log “double click ON, turning on room lights" | ||
+ | -- since the switch doesn’t control it’s local load when doing a double click the first thing we should do is control it | ||
+ | turnon (thisUnit) | ||
+ | brighten “other room light” to 75 | ||
+ | turnon “yet another light in the room" | ||
+ | end if | ||
+ | | ||
+ | else if theButton is equal to “2" then | ||
+ | write log “the bottom paddle was pushed" | ||
+ | | ||
+ | if theGesture is equal to “3" then | ||
+ | write log “double click OFF. turning off the room lights" | ||
+ | turnoff (thisUnit) | ||
+ | turnoff other room light" | ||
+ | turnoff “yet another light in the room" | ||
+ | end if | ||
+ | | ||
+ | | ||
+ | end if | ||
+ | </ | ||
+ | |||
+ | **Hubitat Notes:** | ||
+ | Note that with the current built in driver on the hubitat only tap and double tap are available. I am looking into the possibility of using a user created driver or creating one myself that will properly support that for us. At the moment you are limited to that. | ||
+ | |||
+ | ===Controlling the RGB LED’s with a Hubitat=== | ||
+ | The hubitat and the vera have incompatible ways of sending such commands to the device so you must use a different method for the hubitat than the Vera did. | ||
+ | |||
+ | First make sure that the device in the Hubitat is setup to be using the built in Home Seer WD200+ Dimmer driver. Then make sure that the switch in the control page under preferences for that device labeled “Enable Status LEDs” is turned on and save the configuration if necessary. | ||
+ | |||
+ | |||
+ | The scripting command we use to send these commands is sendDeviceCommand which is sent directly to the unit like this: | ||
+ | |||
+ | < | ||
+ | tell xUnit “name of your WD200 dimmer” to sendDeviceCommand( “setStatusLED”, | ||
+ | </ | ||
+ | |||
+ | you will pass 2 parameters to the command as in the above example. The first is always the string “setStatusLED” and capitalization matters. The second is a comma separated list of 3 values. **it is important that you not place any spaces in this list** The first parameter is the LED number which should be 1-7. The second can be either a number or the name of the color. The valid values are: 0 or off, 1 or red, 2 or green, 3 or blue, 4 or magenta, 5 or yellow, 6 or cyan, 7 or white. The third is whether or not the led should blink. It must be either 0 or 1, or, on or off. Remember not to put any spaces in this list or the command will not be sent. | ||
+ | |||
+ | I have had a very issues with this. With the built in driver I cannot reliably get the indicator LED to stay off when no status LED’s are on. It may be necessary to use a user version of the device driver for this. I am still looking into that. | ||
+ | |||
+ | |||
+ | ===Controlling the RGB LED’s on the Vera=== | ||
The other new feature of the WD200+ is the ability to change the color of the LED’s that display the level, or to control the color and the flashing of them individually to give a status display. XTension 9.4.6 adds support for changing all those settings via the new [[supported_hardware: | The other new feature of the WD200+ is the ability to change the color of the LED’s that display the level, or to control the color and the flashing of them individually to give a status display. XTension 9.4.6 adds support for changing all those settings via the new [[supported_hardware: | ||
Line 41: | Line 107: | ||
- | The [[https:// | + | The [[https:// |
^parameter^Description^Value^Example^ | ^parameter^Description^Value^Example^ | ||
Line 57: | Line 123: | ||
|27| Status Mode Color of LED 7|:::|:::| | |27| Status Mode Color of LED 7|:::|:::| | ||
|30| Flash Speed. Any of the LED’s can be assigned to flash or not flash. Only 1 flash speed is supported at a time via this parameter.|0=No Blinking, 1=100ms rate (fast blink) valid values from 0-255 but useful values are probably up to 10 or so.|setData( 30, 1, 1) sets a fast alert flash| | |30| Flash Speed. Any of the LED’s can be assigned to flash or not flash. Only 1 flash speed is supported at a time via this parameter.|0=No Blinking, 1=100ms rate (fast blink) valid values from 0-255 but useful values are probably up to 10 or so.|setData( 30, 1, 1) sets a fast alert flash| | ||
- | |31|Bitmask to turn on or off blinking for each LED. You could use the text to number command to build the bits.|valid values are from 0 to 127|setValue( 31, 1, text to number “& | + | |31|Bitmask to turn on or off blinking for each LED. You could use the text to number command to build the bits.|valid values are from 0 to 127|setData( 31, 1, text to number “& |
+ | ====Turning off all the lights==== | ||
+ | While there doesn’t seem to be a way to make the lights not show at all you can now do that with the status mode. Turnon the status mode instead of the level mode and just set every LED to off. |
supported_modules/hs-wd200.txt · Last modified: 2023/02/13 14:52 by 127.0.0.1