HomeSeer HS-WD100+ and more (Simple DTH in post 27, advanced feature DTH in post 32)

My GE’s have 100w LED equivalents and they sputter during dimming. Other than that they seem to work fine. I have not used them long enough to notice too much lag or delay. I need to look into whether I can speed up the dimming rate or just make them instant on/off. That would be ideal. Also, I am not used to the interface of the GE’s. If the garage lights are half dim then I have to hold down the up rocker to dim it back up. I am not used to that and would prefer my lights just came on full bright each time. I am thinking to replace that with just an on/off switch but it is already installed so I will live with it for now. I think the homeseer would be nice because I could make double tap full bright. I am still learning all the minor differences between switches. I like my cooper’s a lot.

1 Like

So far I have been pleased with the way the HomeSeer/Dragontech WD100+ has been working with the custom device handler by @Darwin that exposes the additional functions of Double-Tap-Up, Double-Tap-Down, Triple-Tap-Up, Triple-Tap-Down, Press&Hold-Up, Press&Hold-Down. Six additional button control opportunities.

The issue has been how to take advantage of it all. Smart Lighting smartapp is fine but is limited to only four button and it can not do 3-speed ceiling fan control as well. The Button Control+ smartapp fit best for my needs but it also was designed around the Minimote which only has 4 buttons. I ended up modifying Bruce’s code to be able to use all six possible events from the new HS-WD100+
The code is Button Controller Plus and is located here below:


I have minor updates available to the HomeSeer HS-WD100+ dimmer and HS-WS100+ on/off switch device handlers that adds the “numberOfButtons” attribute so that the new CoRE rules engine (thanks @ady624) can automatically identify the correct number of available device buttons. These also correct a minor issue where the DH’s were not properly distinguishing between physical and digital/virtual button presses (this issue would not have affected you unless you specifically had actions determined by physical vs. digital/virtual button presses). The repository locations remain the same as before:


Thank you for adding support for CoRE. Awesome, thank you. Do you support more than just pushed and held? If so, maybe we can find a way to tell CoRE that too… Since they are non-standard, people may use them and find out they don’t work with regular buttons that only know pushed and held…

The double/trip tap and hold functions are currently mapped only to the button pushed capability right now (6 buttons total for both up/down) cases. The button capability mapping was added for compatiility with existing SmartApps, but some thought should probably be put into whether or not there is a better long term architecture for these functions. I also added the “numberOfButtons” attribute to the Nexia One Touch DH, which has 15 buttons (both pushed and held are supported) and that appears to work with CoRE in limited testing. Both the HomeSeer switches and One Touch appear to support a button release capability after being held which I didn’t add, but I suppose it could be handy for dimming or other similar functions.

@ady624, I don’t want to derail this thread, but also wanted to add to the comments of others and say how impressed I’ve been with not only your skills and dedication in the creation CoRE, but also with your push to make it GPL. You’ve done some phenomenal work and continue to push ST app state of the art.


I have a bunch of Dragontech and will give it a try tonight. It would be awesome if they are the same.

1 Like

Tried the Dragontech dimmer and switch and it’s a NO GO on double/tripple/held functions. No event on IDE log at all for those functions except ON/OFF. Guess it’s time to get some HomeSeer.

1 Like

You can tell from the conformance statements. The Homeseer models are using the “central scene” command set The DragonTech are not. :sunglasses:


I love those virtual buttons! It reminds me when I looking at the HomeSeer vs the standard dimmers on my ST and I get to control those button actions directly from the device Thing in the mobile app. :grin:

Just food for thought… consider adding the visual indication of tapping those buttons like @ChadCK does with his device handler code on the fan speed buttons so there is visual feedback indication to the user that he initiated that action?

Thanks for the suggestion @dalec. I was pondering adding tap/hold indication a while back. I’ll see about getting that in. This would also be useful for verifying that your switch is working properly without having to look at logs or setting-up test actions in an app.

1 Like

Yeah, I guess what I was getting at is they have the Same hardware. So it’s just a firmware limitation. Technically the dragontechs could be upgraded via fw patch to have the same capabilities.

1 Like

I went ahead and added a secondary control tile attribute to indicate the last tap/hold press for the HS-WD100+ dimmer device handler. This only involved adding a handful of SLOCs, and aside from maybe me being a little lazy, I was trying to minimize added complexity to the code. On the downside, it does take away some of the dimmer level slider real-estate, but at least for me, I don’t seem to miss it. I wish there were more options for status placement on the multi-attribute tile. Let me know if the reduced slider area causes issues for anyone and/or if you would greatly prefer a different approach:

I can update to the on/off switch device handler as well; I’ll probably convert that to use use a multi-attribute tile while I’m at it. It may be best to do that anyway for consistency.

1 Like

S W E E T ! ! ! I’m checking github now. :grinning:

@darwin I think the slider is the same size … just moved over to make room for the multi-attribute. That is just fine with me.

FYI UPDATE: It displays differently for Android & WindowsPhone, With Android the multi-attribute is on continuous scroll with the dimming level. FWIW, it’s still functional but waiting for the scrolling info is not nearly as effective as iOS. I will get a quick video to show. I also added a screen capture for those with Windows Phone; it is the crudest display of info but at least it shows all and visually triggers the color background when touched.

Sorry for poor video but my ipad stinks at taking good video that needs to be rotated. The video shows the scrolling on the Android, visual feedback of taps, speed of updating the multi-attribute field, etc.

1 Like

Thanks @dalec. Interesting. I knew there were some rendering differences between the platforms, but I didn’t realize how significant they were for some of the multi-attribute keys - and that the multi-attribute controls may even get mapped to single attribute tiles on the Windows Phone. Really appreciate the image and video captures!

1 Like

I was hoping for a little bit of direction, I recently purchased 4 of these switches (2 WD + 2 WS), and although one of the WS seems to be experiencing the on/off/on cycle (I will attempt a RMA soon), I seem to be getting what I believe to be a bit of cross-talk with the dimming modes.

I did not define any configuration for buttons 5/6, but my Living Room WD switch uses both the “Button Controller Plus” (for 2/3 tap actions) and the default “Automate Lights & Switches” to turn on and set level.

Each time I Press and Hold, my lights seem to go full max, full min, or snap back to the dimming level. Has anyone had a similar experience, or does this switch option not play well with the other SmartApp?

The apps should work great together. It just sounds to me like you setup competing configurations which you didn’t intend. Let me know exactly what you configured for each of the buttons in Button Controller Plus as well as “Automate Lights & Switches”. Maybe I can help you figure out what you got going on. Maybe you found a bug in the smartapp?

FYI: it is always a good practice to post your question about a custom smartapp in the thread on the smartapp itself. That is the one that the author and other users with questions or issues typically monitors. Someone with your same issue might not be seeing it here. :slight_smile:


Moving my discussion to the other thread.

1 Like

As a result of working with @jshessen I need some feedback. Can someone help verify how this switch works when using the 5th and 6th button features that are triggered by the Press & Hold on the paddle?

The best I can tell the switch can not differentiate between the local dimming control of the switch by a continuous press and the button 5/6 operation of Press&Hold. It appears that when one wants to implement use of local dimming it also triggers the 5/6 button actions (press&hold) as well? I experimented with mine and I didn’t see how to operate the paddle and not have both (local dimming & 5/6 button action) occur simultaneously.

So that means that if I only want to manually change the dim level of my lights that are connected to the switch I will automatically trigger the 5/6 button operation as well. And the same is true in reverse, if I only want to trigger a 5/6 button action with press&hold I have no choice and I will manually be changing the dim level of the switch simultaneously as well.

UPDATE: Heard back from HomeSeer and they confirmed the operational quirk above on the dimmer version. Of course this only applies to the dimmer version not the HS-WS100+

That has been my experience so far. I just didn’t use the 5 & 6 buttons to do anything because I didn’t need them.

1 Like

As discussed in the [RELEASE] Button Controller Plus, HS-WD100+ HS-WS100+ thread, I’ve updated the HS-WD100+ Device Handler to add the option to specify a dimmer fade-up rate for remote commands. The dimmer ramp up behavior is managed by the device handler itself by sending intermediate level commands, since the device does not currently appear to support a native configuration to set the remote dim rate.

It’s off by default, but can be set in preferences via the gear icon by selecting “Enable remote dim fade-up”. In preferences, You can also change the default values for the % size of each level (currently 5%) and the ms duration to spend at each level (currently 20ms).

In general, the dim level ramped up more smoothly than I expected considering it’s being managed by the device handler and not on the switch where it ideally belongs. Occasionally though, as expected with the cloud and mesh network, I could see some jitter and every so often an out of order level command.

I’m curious if enabling this slower ramp-up behavior will help anyone who is seeing issues with some LED bulbs when turning them on by remotely by setting them to a specific level.

1 Like