Thank you for your work here, Kevin! I am a huge fan of this switch and previously controlled its LEDs with webcore. That broke at some point along with my triple click feature, so I moved to your device handlers. Can you please let me know?..
-If you have any tips for WD200+ that is not always reporting on state correctly? I can control it perfectly, but it retains on state when I turn it off at switch.
-I’ve added the child device handlers to control LEDs. I created the Normal mode child device, tests good. I can also see the Status Mode Blink Frequency. But I do not see the LED child devices. I have respective Color Child app published, but no dice.
Remove // from the log.trace line at the bottom of the code, open live logging, physically turn it on or off, wait about 5 seconds, physically do the opposite, wait 5 seconds, and then post the live logging data.
That will show whether or not the handler is getting any messages from the device when it’s controlled physically.
Now that automations supports custom capabilities I think the LED related functionality is exposed through the parent device so the child device workarounds shouldn’t be necessary, but I haven’t tested that myself so I could be wrong…
@krlaframboise Thank you for the DTHs! I have been having super annoying issues with all my Homeseer devices crashing (they freeze up and only a power cycle will restore them). I switched to your DTHs to see if the issue would go away but it is the same. Supposedly it is due to excessive traffic causing the device to stop responding. Anyhow, I have a couple unrelated issues I wanted to run by you:
I have an automation where my kitchen counter lights turn on and off based on motion and a few other things. When I switched to your DTH the lights started not turning on and I found that the ST app sees the dimmer as ON when in reality it is OFF. If I press OFF, then the automation turns them on properly. After weeks of this issue, I switched to the ST generic zwave DTH and it works perfectly again. So, to recap, the light is off, but the ST app thinks it is on, therefore the webcore automation does not work.
I have a webcore automation that triggers the leds to turn on based on something happening in the house. With the previous DTH, I could turn blinking on only at night to catch my attention. With your implementation of this feature I would have to change the color from say “red” to “blinking red” at night unless I misunderstood the code. I wonder whether I can use “blinking red” with blink frequency 0 and just change that to 500 at night. Even if this works though, it would still bug the OCDness in me.
I am aware the current piston just sets the blink frequency to 500 at night but the colors used are the non blinking ones so in effect nothing changes. Before I start reworking the code to switch to the blinking colors at night, I was hoping there was some nicer solution.
This handler was tested by HomeSeer and myself and we didn’t run into any issues with the reliability of the on/off reporting so that might have something to do with changing handlers instead of re-joining the device.
You should be able to leave the individual leds on blinking red and toggle the master blink frequency between 0 and 500.
This was written when custom capabilities were buggy and only partially supported which is why it has all the child work arounds and the implementation isn’t as clean as I would have liked.
That being said, I noticed that your pistons are looping through all the LEDs, but that shouldn’t be necessary using my handler.
I actually excluded, reset and included the dimmer with your DTH being the only one installed. As mentioned prior, if I swap the DTH with the generic ST one, it works properly (ST app shows proper off status so the piston is able to turn it back on when needed).
As for the led notification piston, it loops all my notification devices and for each device it loops for each led, however my intention was for it to only send commands to the devices when the updated table shows that a value has changed. Did I do this incorrectly and I am sending a zwave command for each led on each device?
@JDRoberts I think you have these super powers… Would it be possible for you to move the last few posts to the WD200 related thread? I mistakenly posted in the WS200 thread and am now derailing the thread.
Keep in mind you’re on the wrong topic and the issue that user reported was that it worked fine when controlled in ST, but the status didn’t change when physically controlled which sounds like the opposite of what you’re seeing.
