Homeseer WD200+ Zwave Plus Wall Dimmer

Configuration Z-Wave
1

Just received this in a newsletter:

b180efa563420587_Medium
Homeseer WD200+ Zwave Plus Wall Dimmer

This opens a lot of possibilities :slight_smile:

2

It will probably take a while for this to be supported in OpenZwave - as far as I know it doesn’t even support Central Scene officially yet.

3

With the WD100+, I control 5 devices using double and triple tap as on/off switch. So adding up to 5-tap and some RBG led, I can totally imagine using this one as a global control switch/dimmer.

4

I purchased one and a three way companion. I should still be able to use it as a standard dimmer until more support is added right?

5

I have one of these. Homeassistant doesn’t recognize the device, but it will treat it as a normal dimmer. You can’t do any configuration on it though.

I did write up a device xml file for openzwave and was able to change the configuration parameters including individual LED colors, so there doesn’t seem to be any reason it won’t be fully supported in the future.

2 Likes
6

Good deal! I hope OZW adds support soon!

7

Quick question, did you set a refresh option on the dimmer to get the UI to work right? I was able to get scene activation working with double taps, etc.

8

Yes, I had to use the refresh option to keep the UI consistent. I also got scenes working, but I had to tail the z wave log while tapping the switch to get the scene_data numbers, I have no idea how those numbers were determined.

9

Can either of you provide a bit more detail as how to get the WD200+ working in HA for the moment? I seems to work somewhat ok out of the box, but as it sounds like you mention, the UI is pretty delayed. Where do I set the refresh, and does that clean up the UI issues completely?

10

This is from my configuration.yaml file. The devices with “refresh_value: true” are homeseer switches. The UI cleans up within a couple of seconds.

   zwave:
      usb_path: /dev/zwave
      polling_interval: 60000
      device_config:
        switch.pantry_light_switch_switch:
          polling_intensity: 1
        switch.porch_light_switch_switch:
          polling_intensity: 1
        light.kitchen_sink_light_switch_level:
          refresh_value: true
        light.laundry_room_light_switch_level:
          refresh_value: true
1 Like
11

Made that settings change… but the result I’m getting is still pretty much the same. The status is always wrong until you click a second time.
Eg.
Light = Off, UI = off, User turns UI ON, Light = On, UI = On…then off. Then you click on again… and light stays on and UI finally says on. The reverse is true for Off.

Also, and I think this might have something to do with the laggy status, is that the lights ramp time is pretty slow… so I think the status gets updated before they are complete off, and so it thinks the updated status is on still? Any way to kill that ramp time and make things immediate?

Also, @aenea as this you? https://github.com/OpenZWave/open-zwave/pull/1439 Is there any way to pull those changes into my HA? Does it allow for complete WD200 support?

D

12

I don’t know how you’d pull it in, but you could edit the files directly. I’m running the docker version of HA and the file path inside the container is: /usr/local/lib/python3.6/site-packages/python_openzwave/ozw_config/config/

If you get the files updated, you’ll have to remove the switch from your z-wave network and re-add it. Once it’s re-added you don’t really need the files anymore so you won’t lost functionality if an upgrade wipes out the files.

I copied the parameters from here:

so it should cover all the documented options and the switch did respond properly to all the options I tested.

13

Oh really? So after manually updating those files the switch works flawlessly?
Do the extended features work too, like programmatically changing the LED colors?

14

@e_jp,

Could you please point me in a direction with instructions on how to get double/triple taps working on the homeseer switches in Home Assistant.

Thanks

16

Hey pdobrien3,

Sorry for the delay, got a busy week.

So, you first have to add some lines in the zwave config. See https://www.home-assistant.io/docs/z-wave/device-specific/#homeseer-switches
Then you can add this in your automation:

- id: a0009a
  alias: Double tap down
  trigger:
  - platform: event
    event_type: zwave.scene_activated
    event_data:
      entity_id: zwave.homeseer_hswd100_wall_dimmer
      scene_id: 2
      scene_data: 3
  action:
    service_template: >
      {% if states.light.lampe_christine.state == 'on' %}
        light.turn_off
      {% else %}
        light.turn_on
      {% endif %}
    data:
      entity_id: light.lampe_christine

Basically, when double tap down, if light is on then turn it off else turn it on.

I hope this will help you.

2 Likes
17

@iDVB did you find any update on these switches? I would like to change the colors too. Not sure if it is possible yet? Hope these are supported fully in future. I have 3 of these and would like to use them to their potential.

18

Any news on the colored status lights?

1 Like
19

I was able to switch the color on mine within zwave settings by grabbing a copy of the latest OpenZWave configs and pointing my install at the directory using the config_path setting.

1 Like
20

@Tuckie Can you elaborate a bit more on the specifics of what you did with the config, and how you integrated it in to HA, and why it helped?

1 Like
21

sure @JimM:

I downloaded a copy of openzave, and pointed my install to the config directory from the project.

zwave:
  usb_path: /dev/zwave
  config_path: /zwave-config/open-zwave/config

This lets my copy of home assistant use all of the latest xml definitions from the openzwave project.
In my case, it let me set all of the settings on the zwave page for my WD200+.

1 Like