User Tools

Site Tools


supported_modules:hs-wd200

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
supported_modules:hs-wd200 [2018/09/07 13:12]
James Sentman [Set Data]
supported_modules:hs-wd200 [2021/05/30 17:08] (current)
James Sentman added hubitat info
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:​hs-wd100|WD100+]] dimmer it adds 2 more central scene gestures. Note that the gesture codes are different between the 2 switches however. It can send us the 4 click and the 5 click gestures. See the article on the [[supported_modules:​hs-wd100|WD100]] for more info on it’s central scene handling and how to work with that in XTension. ​The available Central Scene gesture codes on the WD200+ dimmers are +The HS-WD200+ is Home Seer’s latest wall dimmer. In addition to all the commands and support of the [[supported_modules:​hs-wd100|WD100+]] dimmer it adds 2 more central scene gestures. Note that the gesture codes are different between the 2 switches however. It can send us the 4 click and the 5 click gestures. See the article on the [[supported_modules:​hs-wd100|WD100]] for more info on it’s central scene handling and how to work with that in XTension. ​
  
-^Gesture^Code^ + 
-|Single Click|128| +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 gesture codes that are received from this switch. They are now the same as they were for the WD100+ dimmers with the addition of the extra multi-click supported. 
-|Double Click|131| + 
-|Triple Click|132| +The available Central Scene gesture codes on the WD200+ dimmers are: 
-|Hold|130| + 
-|Release of Hold|129| +^Gesture^Code^Code Prior to 1.7.4 vera update
-|Quadruple Click|133| +|Single Click|0|128| 
-|Pentuple Click|134|+|Double Click|3|131| 
 +|Triple Click|4|132| 
 +|Hold|2|130| 
 +|Release of Hold|1|129| 
 +|Quadruple Click|5|133| 
 +|Pentuple Click|6|134|
  
  
Line 26: Line 31:
 on centralScene( theButton, theGesture) on centralScene( theButton, theGesture)
  
-  if theButton is equal to 1 then+  if theButton is equal to 1" ​then
     write log “the top paddle was pushed"​     write log “the top paddle was pushed"​
     ​     ​
-    if theGesture is equal to 131 then+    if theGesture is equal to “3" ​then
       -- the switch was double clicked on       -- the switch was double clicked on
       write log “double click ON, turning on room lights"​       write log “double click ON, turning on room lights"​
Line 38: Line 43:
     end if     end if
     ​     ​
-  else if theButton is equal to 2 then+  else if theButton is equal to 2" ​then
     write log “the bottom paddle was pushed"​     write log “the bottom paddle was pushed"​
     ​     ​
-    if theGesture is equal to 131 then+    if theGesture is equal to “3" ​then
       write log “double click OFF. turning off the room lights"​       write log “double click OFF. turning off the room lights"​
       turnoff (thisUnit)       turnoff (thisUnit)
Line 52: Line 57:
 </​code>​ </​code>​
  
-===Controlling the RGB LED’s===+**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: 
 + 
 +<​code>​ 
 +tell xUnit “name of your WD200 dimmer” to sendDeviceCommand( “setStatusLED”,​ “1,​red,​blink”) 
 +</​code>​ 
 + 
 +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:​veraui7#​set_data|setData command]] 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:​veraui7#​set_data|setData command]]
supported_modules/hs-wd200.1536325960.txt.gz · Last modified: 2018/09/07 13:12 by James Sentman