Comments on: HomeSeer HS-WD200+ & HS-WS200+ Dimmer, Switch Review and SmartThings Device Handlers

By: Rich Baseil

Rich Baseil — Sun, 06 Dec 2020 04:31:55 +0000

Hi! Thanks so much for the 13-Aug-2020 version of the SmartThings device handler for the HS-WD200+. I am able to connect the switch to my v2 SmartThings hub and control it using the new SmartThings App, but any settings I change for the switch in the SmartThings app seem to be ignored by the device handler. For example, if I select a different default LED color, or indicate the LED should be on if the load is off, a change in the settings shows in the SmartThings app but has no effect on the switch. The same problem happens with the original device handler v1.0 as well as 1.0.dd.1. Any advice?

By: Brian Bruck

Brian Bruck — Wed, 30 Sep 2020 17:38:03 +0000

In reply to Darwin’s Den.

Thanks so much for letting me try out your new DTH!

It works perfectly with the automations in the New App! Is there anything you’d like me to specifically test/try? I’d be happy to help.

I have two WD100+ dimmers that have having the same button controller issue as well. Do you have a beta version for that model?

By: Darwin's Den

Darwin's Den — Mon, 28 Sep 2020 18:45:19 +0000

In reply to Brian Bruck.

I’m not sure why buttons 9-12 aren’t working with the button controller app, but if it’s the dimmer (WD200+) that you are having issues with, I do have a newer beta version of the WD200+ device handler that should support the Automation capability in the new app. It may allow you to work-around the issues you are having, but I’ll caution that this new version has not received much testing yet. The new handler can be downloaded at a different location than the current production version (for now) at https://raw.githubusercontent.com/DarwinsDen/SmartThingsPublic/master/devicetypes/darwinsden/wd200-dimmer.src/wd200-dimmer.groovy.

This new handler was specifically updated to work with the button mapping approach used by the new Automation capability. Once you update to this new device handler, the device needs to be refreshed in the app for the new mappings to take effect – by either pulling down on the device once it’s selected in the new mobile app (ie. to get spinner for a few seconds) or by hitting config in the old app. The new handler provides a preference/setting option that is required to be used if you wish to toggle between the new button mapping approach used by the new Automation capability and the legacy button approach used by the current smart lighting, button controller, WebCore, etc smart apps (at least until these legacy smart apps are updated to use the new approach). The default setting is to use the new Automation button mapping approach.

By: Brian Bruck

Brian Bruck — Sun, 27 Sep 2020 17:37:19 +0000

Hi Everyone! First of all, thanks to Darwin’s Den for writing this DTH. It has worked well for the almost two years I have been using it.

I forced myself to switch over to the new SmartThings App (and updated this DTH and Button Controller App) and most everything seems to be working now, except the button controller on both the classic and new app only let me get to button # 8.

After 8 it goes back to the beginning on the classic app, and in the new app, the only option is the “save” after reaching Button 8. So I can’t attach any scenes to buttons 9-12.

Any idea why that is happening? TIA. -Brian

By: Darwin's Den

Darwin's Den — Thu, 13 Aug 2020 16:38:41 +0000

In reply to Mike Rossman. Thank you! I haven't had a chance yet to look at compatibility with the new SmartThings app for these devices. I appreciate your efforts in not only debugging these, but also taking the time to provide your findings. I'm hoping to to be able to get to the updates shortly.

By: Mike Rossman

Mike Rossman — Thu, 13 Aug 2020 04:48:24 +0000

Samsung is forcing users to their new app and it looks like it’s breaking the device handler for the HS-WS200+. I suspect the same for HS-WD200+. After messing around a bit it looks like the “special” triangle characters in the tile label is confusing the app. I played around a bit and replaced the triangle characters with ASCII characters and restored functionality. Hopefully find the helpful, and it leads to a more formal bug fix.

By: Darwin's Den

Darwin's Den — Thu, 27 Sep 2018 17:39:30 +0000

In reply to Brad.

Hi Mark. Thanks! Appreciate it.

You likely have the answer by now, but the HS-WA100+ is required any time you want to use a HomeSeer dimmer or switch in a 3+ way configuration. Unlike some of the newer Z-Wave dimmers out there such as the Inovelli’s, the HomeSeer’s are not designed to work with standard switches as the aux switch. Hope that answers your question!

By: Brad

Brad — Thu, 30 Aug 2018 17:09:31 +0000

Hi.

Thanks for all of your work.

Is the HomeSeer HS-WA100+ wired 3-way companion switch necessary if you want to use one of the Z-wave dimmers on a 3-way switch or is it only required if you want to have the control capability the companion switch offers?

By: Darwin's Den

Darwin's Den — Thu, 09 Aug 2018 21:33:45 +0000

Hi Mark. That definitely sounds like odd behavior. Just to make sure I understand what’s happening – if you manually turn on the switch by holding down the up toggle, the light will reach full brightness when the dimmer reads 50% (and there is no additional change in brightness as the dim level increases to 100%). But if you then decrease the brightness from 100% to, say 90%, the light will dim slightly. Is that correct?

I can’t think of anything offhand with the device or device handler that would explain that, but I’ll look a little closer. Are you able to try a different bulb? Possible an incandescent bulb for testing? Also, does it have the same behavior when changing the brightness from the slider on the mobile device?

Let me know if my understanding is correct regarding the behavior of the issue, and I’ll keep pondering!

By: Mark Boarman

Mark Boarman — Tue, 07 Aug 2018 13:06:11 +0000

Thanks for your brilliant work with the WS200+ DH! I have a small issue that when pressing the paddle the ramp up rate appears to hit full brightness and around 50% of the led climb. Further more in limited testing it doesn’t seem to matter what I set the local parameter 12 (local ramp rate) if remains the same. However, it does function correctly when ramping down on shut-off. Any suggestions why it’s only working one-way and not both on and off?

By: Darwin's Den

Darwin's Den — Wed, 01 Aug 2018 18:05:30 +0000

In reply to Kyle. Great! Always good to hear when things work! No updates yet for the WS200+ switch. I still need to merge in the mobile UI tile display updates to make the switch display interface better match the dimmer, but as far as I know, there are no outstanding functional concerns. Let me know though of any issues, or if you have any other great enhancement suggestions.

By: Kyle

Kyle — Wed, 01 Aug 2018 04:12:15 +0000

Thanks! Works perfectly! Is there an update for the switch (non dimmer) device handler?

By: Darwin's Den

Darwin's Den — Sat, 28 Jul 2018 17:20:18 +0000

In reply to Kyle. Kyle, I've added the capability to programmatically specify the LED blink rate. The new command "setBlinkDurationMilliseconds" allows you to specify the blink on/off duration to be anything from 100ms to 25000 ms (25 sec). The firmware allows you to specify a single value that controls both the on and off duration. The default was 500ms on/500ms off. Let me know how this works for you.

By: Darwin's Den

Darwin's Den — Wed, 16 May 2018 15:02:02 +0000

In reply to Kyle. Hi Kyle. Yes, I'll put LED flash rate on the list for future enhancements.

By: Kyle

Kyle — Wed, 16 May 2018 00:23:09 +0000

Any way to add the ability to change the LED flash rate like with HomeSeer’s software?